On 23.09.2005 [13:43:26 -0400], Bill Davidsen wrote:
Nishanth Aravamudan wrote:
On 22.09.2005 [15:19:05 -0400], Bill Davidsen wrote:route <destination_IP> gw <default_router_IP> mss 1200
Nishanth Aravamudan wrote:<snip my long mail>
Hello all,
Yes, I see that still being an option. Let me go learn how to use routecode in such a solid state. I have had only one complaint so far: itYou can (or could in 2.4) sometimes play with the size for an individual IP by using the "mss" option of the old "route" command. That shouldn't glitch anything, it just should use little packets.
seems that the the "Broadcom Corporation NetXtreme BCM5751 Gigabit
Ethernet PCI Express" adapter, with the tg3 driver, downs and ups the
iface on MTU changes. Unfortunately, with some VPN software I use, it is
sometimes necessary to drop the MTU to 1300 or so to get consistent
connections. When I do this, though, ssh through the tunnel tends to not
function. I have a workaround, where I bounce over a different laptop,
but that's a bit of a pain (and that network adapter seems to be able to
transiently change the MTU). Not a big deal, in any case.
and see if that works better.
Thanks, that works for setting the mss, but when setting it to 1200, i
can't even ping the remote host. I can ping it if remove the mss change.
I can even ssh to it. It just so happens that when I try to ls a large
directory, the connection tends to hang. Any other ideas? Or tracing I
can do to figure it out?