Hi,
regarding CPU load: Check this with
while pushing traffic through the device.
Regarding MTU:
A often used way to determine actual MTU of a path is pinging the remote side with a ping of a given sized and the DF (=dont fragment) bit set. Keep in mind, that you have to add 36 bytes to the used ping size to get the MTU (20 bytes for the IP header and 8 bytes for ICMP). Starting from a ping length of 1500 you decrease the value of the -l parameter step by step (for example by 50 every step).
As long as the packets must be fragmented, you wont get a successful response. As soon as your chosen -l parameter value (+28 bytes) is less than the actual MTU, you'll get a successful response.
On windows you can yous ping. The parameter -f is "don't fragment" and -l the size of the ping's payload.
From my machine it looks like this:
Step 1)
-> no successful reponse in my case: decrease value of -l 50
Step 2)
-> successful response, increase value of -l by 25
Step 3)
-> no successful reponse: decrease value of -l by 12
Step 4)
-> successful response: increase value of -l by 1
Step 5)
-> successful response: increase value of -l by 1
Step 6)
-> successful response: increase value of -l by 1
Step 7)
-> no successful response.
Last working value was 1464. Adding 28 bytes from IP header and ICMP leads to 1492, which is the MTU of my PPPoE session.
You should configure your PPPoE clients MTU according to the value you determined by using the shown "ping technique".
Ape