MTU: Difference between revisions
Appearance
Content deleted Content added
mNo edit summary |
mNo edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
To simply test if you have 1500 MTU: |
To simply test if you have 1500 MTU: |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
For example: |
For example: |
||
| Line 13: | Line 12: | ||
[[File:Firebrick-1500MTU-ping.png|200px|thumb|a 1500 ping on FireBrick]] |
[[File:Firebrick-1500MTU-ping.png|200px|thumb|a 1500 ping on FireBrick]] |
||
| ⚫ | |||
| ⚫ | |||
ping -c1 -M do -s 1472 81.187.81.187 |
ping -c1 -M do -s 1472 81.187.81.187 |
||
On OSX (Apple): |
'''On OSX (Apple):''' |
||
ping -c1 -D -s 1472 81.187.81.187 |
ping -c1 -D -s 1472 81.187.81.187 |
||
On Windows: |
'''On Windows:''' |
||
ping -n 1 -f -l 1472 81.187.81.187 |
ping -n 1 -f -l 1472 81.187.81.187 |
||
| Line 43: | Line 41: | ||
'''0 packets transmitted, 0 received''', +1 errors |
'''0 packets transmitted, 0 received''', +1 errors |
||
[[File:Mtu-osx-ani.gif|800px|frameless]] |
|||
==Explanation of the ping options== |
==Explanation of the ping options== |
||
| Line 109: | Line 108: | ||
1 packets transmitted, 1 received, 0% [[Packet Loss|packet loss]], time 0ms |
1 packets transmitted, 1 received, 0% [[Packet Loss|packet loss]], time 0ms |
||
rtt min/avg/max/mdev = 55.448/55.448/55.448/0.000 ms |
rtt min/avg/max/mdev = 55.448/55.448/55.448/0.000 ms |
||
=MTU Overview= |
=MTU Overview= |
||
| Line 178: | Line 174: | ||
As there is no real way to tell if baby jumbo frames are supported on an [[Ethernet]], RFC4638 defines an extra option for PPPoE to negotiate this at the [[Ethernet]] level. Of course two ends could simply agree to handle slightly larger [[Ethernet]] frames by configuration as well. Sadly this is not always the same level of operation or the same equipment that does the MRU negotiation at the PPP level, and if that knows PPPoE is involved it will not negotiate more than 1,492 MRU as per RFC2516. So typically some configuration is needed. |
As there is no real way to tell if baby jumbo frames are supported on an [[Ethernet]], RFC4638 defines an extra option for PPPoE to negotiate this at the [[Ethernet]] level. Of course two ends could simply agree to handle slightly larger [[Ethernet]] frames by configuration as well. Sadly this is not always the same level of operation or the same equipment that does the MRU negotiation at the PPP level, and if that knows PPPoE is involved it will not negotiate more than 1,492 MRU as per RFC2516. So typically some configuration is needed. |
||
The upshot of all this? It is possible to get BT FTTC (Fibre to the Cabinet) circuits (which use PPPoE) working on full 1,500 byte PPP by using modified pppd on the customer end, a suitable network card that will handle 1,508 byte frames at 10/100Mbit/s. We have done this! (Thanks to TonyHoyle and Simon, customers on irc, for tweaking pppd and testing this for us). The new FireBrick does, of course, support PPPoE with baby jumbo frames to handle 1,500 byte MTU and even bonds multiple lines. Using the right modem (and the DLINK 320B in bridge mode do this) you can negotiate and use 1508 bytes over ADSL as well. |
The upshot of all this? It is possible to get BT FTTC (Fibre to the Cabinet) and BT FTTP (Fibre to the Premises) circuits (which use PPPoE) working on full 1,500 byte PPP by using modified pppd on the customer end, a suitable network card that will handle 1,508 byte frames at 10/100Mbit/s. We have done this! (Thanks to TonyHoyle and Simon, customers on irc, for tweaking pppd and testing this for us). The new FireBrick does, of course, support PPPoE with baby jumbo frames to handle 1,500 byte MTU and even bonds multiple lines. Using the right modem (and the DLINK 320B in bridge mode do this) you can negotiate and use 1508 bytes over ADSL as well. In addition, BTs FTTP ONT units support baby jumbo frames and can support a 1,500 byte MTU. |
||