yea, i always had cable before.
here's an example of information i found on how i arrived at my MTU settings;
https://learningnetwork.cisco.com/thread/25798
the first guy is pretty much right, the guy answering him is trying to calculate crap on his own and is way off, but has the right idea. the problem is that there are additional parameters to set for various kinds of encapsulation that alter payload size as well as some forms of encapsulation can expand their padding, again shrinking the payload size.
so, what i accept to be absolutely certain when calculating MTU is that if there aren't baby jumbo frames implemented by the ISP allowing greater than 1500 MTUs, but not nearly as high as jumbo frame mtus, then you can have an MTU greater than 1488. you could potentially have an MTU of 48bytes x 32 for 1536 MTU, IF there is ABSOLUTELY NO encapsulation in use. Which is never the case, even without PPPoE. To find MTU, i set the router's WAN MTU to 1500 and configured it at the interface of the machine i was testing from.
in this case, windows with the command
Code:
netsh interface ipv4 set subinterface "Local Area Connection" MTU=1456 store=persistent
you can verify with
Code:
netsh interface ipv4 show subinterfaces
so, since MTU can't be greater than 1500, all dsl travels over atm which divides packets into payloads of 48bytes, (+5 bytes making 53byte atm 'cells', but this is not important.) leaving me a starting point of 1488. then, find your favorite speedtest that has been most successful testing your maximum downstream bandwidth and keep dropping your MTU between speedtests a few bytes at a time. when your downstream bandwidth launches back up despite a lower MTU, you'll know you are at your maximum efficient MTU with DSL. After, set the WAN MTU on the router to what you got.
back to the topic;
i disabled jumbo frames under LAN > Switch Control, set this computer's MTU to 1500, but with
Code:
netsh interface ipv4 set subinterface "Local Area Connection" mtu=1500 store=active
i then disabled and re-enabled the the interface and used
Code:
netsh interface ipv4 show subinterfaces
again and this time my computer took the 1456 MTU automatically.
so, it looks like as long as you have jumbo frames disabled, the LAN ports take on the MTU set at the WAN side
1456 MTU is what i arrived at for my connection in my testing. you can try it, but i'd definitely advise testing others to make sure.