ipmtunetworkingping
I tested it on Windows 7 and Ubuntu 11.10 with MTU size 1500B.
1500 – 28 = 1472
So maximum packet that I could ping without fragmentation is 1472B, and this is correct, because when I try set higher value, it shows that fragmentation is needed. But maximum value when ping is successful, is 1448 on both systems. When I try values between 1449 – 1472 bytes I get time out. Why is that?
For Windows 7, Windows Vista and Windows XP, the MTU for various interfaces is available from Windows itself using netsh.
To show current MTU on Windows 7 or Windows Vista, from a command prompt:
C:\Users\Ian>netsh interface ipv6 show subinterfaces
MTU MediaSenseState Bytes In Bytes Out Interface
---------- --------------- --------- --------- -------------
1280 1 24321220 6455865 Local Area Connection
4294967295 1 0 1060111 Loopback Pseudo-Interface 1
1280 5 0 0 isatap.newland.com
1280 5 0 0 6TO4 Adapter
And for IPv4 interfaces:
C:\Users\Ian>netsh interface ipv4 show subinterfaces
MTU MediaSenseState Bytes In Bytes Out Interface
---------- --------------- --------- --------- -------------
1500 1 146289608 29200474 Local Area Connection
4294967295 1 0 54933 Loopback Pseudo-Interface 1
Note: In this example my Local Area Connection IPv6 interface has such a low MTU (1280) because i'm using a tunnel service to get IPv6 connectivity.
You can also change your MTU (Windows 7, Windows Vista). From an elevated command prompt:
>netsh interface ipv4 set subinterface "Local Area Connection" mtu=1492 store=persistent
Ok.
Tested with Windows 7 Service Pack 1
The netsh syntax for Windows XP is slightly different:
C:\Users\Ian>netsh interface ip show interface
Index: 1
User-friendly Name: Loopback
Type: Loopback
MTU: 32767
Physical Address:
Index: 2
User-friendly Name: Local Area Connection
Type: Etherenet
MTU: 1500
Physical Address: 00-03-FF-D9-28-B7
Note: Windows XP requires that the Routing and Remote Access service be started before you can see details about an interface (including MTU):
C:\Users\Ian>net start remoteaccesss
Windows XP does not provide a way to change the MTU setting from within netsh. For that you can:
Tested with Windows XP Service Pack 3
Short discussion on what MTU is, where the 28 bytes is coming from.
Your network card (Ethernet) has a maximum packet size of 1,500 bytes:
+---------+
| 1500 |
| byte |
| payload |
| |
| |
| |
+---------+
The IP portion of TCP/IP requires a 20 byte header (12 bytes of flags, 4 bytes for source IP address, 4 bytes for destination IP address). This leaves less space available in the packet:
+------------------------+
| 12 bytes control flags | \
| 4 byte from address | |- IP header: 20 bytes
| 4 byte to address | /
|------------------------|
| 1480 byte payload |
| |
| |
| |
+------------------------+
Now an ICMP (ping) packet has an 8-byte header (1 byte type, 1 byte code, 2 byte checksum, 4 byte additional data):
+------------------------+
| 12 bytes control flags | \
| 4 byte from address | |
| 4 byte to address | |- IP and ICMP header: 28 bytes
|------------------------| |
| 8 byte ICMP header | /
|------------------------|
| 1472 byte payload |
| |
| |
| |
+------------------------+
That's where the "missing" 28 bytes is - it's the size of the headers required to send a ping packet.
When you send a ping packet, you can specify how much extra payload data you'd like to include. In this case, if you include all 1472 bytes:
>ping -l 1472 obsidian
Then the resulting ethernet packet will be full to the gills. Every last byte of the 1500 byte packet will be filled:
+------------------------+
| 12 bytes control flags | \
| 4 byte from address | |
| 4 byte to address | |- IP and ICMP header: 28 bytes
|------------------------| |
| 8 byte ICMP header | /
|------------------------|
|........................|
|........................|
|. 1472 bytes of junk....|
|........................|
|........................|
|........................|
|........................|
+------------------------+
If you try to send one more byte
>ping -l 1473 obsidian
the network will have to fragment that 1501 byte packet into multiple packets:
Packet 1 of 2
+------------------------+
| 20 bytes control flags | \
| 4 byte from address | |
| 4 byte to address | |- IP and ICMP header: 28 bytes
|------------------------| |
| 8 byte ICMP header | /
|------------------------|
|........................|
|........................|
|..1472 bytes of payload.|
|........................|
|........................|
|........................|
|........................|
+------------------------+
Packet 2 of 2
+------------------------+
| 20 bytes control flags | \
| 4 byte from address | |
| 4 byte to address | |- IP and ICMP header: 28 bytes
|------------------------| |
| 8 byte ICMP header | /
|------------------------|
|. |
| 1 byte of payload |
| |
| |
| |
| |
| |
+------------------------+
This fragmentation will happen behind the scenes, ideally without you knowing.
But you can be mean, and tell the network that the packet is not allowed to be fragmented:
>ping -l 1473 -f obsidian
The -f flag means do not fragment. Now when you try to send a packet that doesn't fit on the network you get the error:
>ping -l 1473 -f obsidian
Packet needs to be fragmented but DF set.
The packet needs to be fragmented, but the Do not Fragment flag was set.
If anywhere along the line a packet needed to be fragmented, the network actually sends an ICMP packet telling you that a fragmentation happened. Your machine gets this ICMP packet, is told what the largest size was, and is supposed to stop sending packets too big. Unfortunately most firewalls block these "Path MTU discovery" ICMP packets, so your machine never realizes the packets are being fragmented (or worse: dropped because they couldn't be fragmented).
That's what causes web-server to not work. You can get the initial small (<1280 byte) responses, but larger packets can't get through. And the web-server's firewalls are misconfigured, blocking ICMP packets. So the web-server doesn't realize you never got the packet.
Fragmentation of packets is not allowed in IPv6, everyone is required to (correctly) allow ICMP mtu discovery packets.
Your ping trial does not necessarily mean anything.
The normal MTU for Ethernet (and for the internet) is 1500. Because ping does not count the (28 byte) header size as part of the packet size, it normally will complain Packet needs to be fragmented but DF set if you try to use a packet size over 1472 (+ 28 = 1500). The DF stands for "Don't Fragment" and packets larger than the MTU have to be fragmented to be transmitted.
Also, to prevent malicious scanners from detecting servers, it is typical to turn off responses to pings, so Request timed out is not necessarily indicative of a problem.
That said, I can ping css-tricks.com and jquery.com and get responses, so you may really have a problem there. To help narrow things down, compare the IP address you are seeing for these sites (ping will report the IP address it is pinging in parentheses after the domain name) to the IP address you see on other computers that work. Also try tracert or traceroute (depending on your OS) to see what route your packets are taking. It is possible there is a routing error between you and the site in question which would show the packets going off into a black hole. I note that both sites you mentioned are hosted by Media Temple so you might try asking them for help.
Best Answer
There are several possibilities:
You can test the latter by pinging with the "don't fragment" option set (on ubuntu: add a
-M dooption), but that is not failsafe since some routers don't properly return an error if they drop a too large packet.