You have the symptoms of an MTU problem: some TCP connections freeze, more or less reproducibly for a given command or URL but with no easily discernible overall pattern. A telltale symptom is that interactive ssh sessions work well but file transfers almost always fail. Furthermore pppoe is the number one bringer of MTU problem for home users. So I prescribe an MTU check.
What is it?
The maximum transmission unit is the maximum size of a packet over a network link. The MTU varies from transport medium to transport medium, e.g. wired Ethernet and wifi (802.11) have different MTUs, and ATM links (which make up most of the long-distance infrastructure) each have their own MTU.
PPPOE is an encapsulated protocol, which means that every packet consists of a few bytes of header followed by the underlying packet — so it lowers the maximum packet size by the size of the header.
IP allows routers to fragment packets if they detect that they're too big for the next hop, but this doesn't always work. In theory the proper MTU should be discovered automatically, but this also doesn't always work either. In particular googling suggests that Network Manager doesn't always properly act on MTU information obtained from MTU discovery, but I don't know what versions are affected or what the problematic use cases are.
How to measure it.
If you have
tracepath from the Linux iputils, run
tracepath 126.96.36.199 to see the MTU over the path to Google's DNS server.
If your version of
traceroute has a
--mtu option, run
traceroute -n --mtu 188.8.131.52.
See Discover MTU between me and destination IP for more options.
Lacking automated tools, you can measure manually. Try sending ping packets of a given size to an outside hosts that responds to them, e.g.
ping -c 1 -s 42 184.108.40.206 (on Linux; on other systems, look up the documentation of your
ping command). Your packets should get through for small enough values of 42 (if 42 doesn't work, something is blocking pings.). For larger values, the packet won't get through. 1464 is a typical maximum value if the limiting piece of infrastructure is your local Ethernet network. If you're lucky, when you send a too large packet, you'll see a message like
Frag needed and DF set (mtu = 1492). If you're not lucky, just keep experimenting with the value until you find what the maximum is, then add 28 (
-s specifies the payload size, and there are 28 bytes of headers in addition to that).
See also How to Optimize your Internet Connection using MTU and RWIN on the Ubuntu forums.
How to set it (replace 1454 by the MTU you have determined, and
eth0 by the name of your network interface)
- As a once-off (Linux):
ifconfig eth0 mtu 1454
- Permanently (Debian and derivatives such as Ubuntu, if not using Network Manager):
/etc/network/interfaces. Just after the entry for your network interface (after the
iface eth0 … directive), add a line with
pre-up ifconfig $IFACE mtu 1454. Alternatively, if your IP address is static, you can add the
mtu 1454 parameter to the
iface eth0 inet static directive.
Permanently (Debian and derivatives such as Ubuntu, with or without Network Manager):
Create a script called
/etc/network/if-pre-up.d/mtu with the following contents and make it world-executable (
ifconfig $IFACE mtu 1454