Greater than 1371 Bytes Output Hangs Session 1806

On Tue, 04 Jul 2006, in the Usenet newsgroup comp.os.linux.misc, in article

Comment: RH7.2 has been end-of-lifed by Red Hat at the end of 2003, and the very limited support at download.fedoralegacy.org ended five months later. That really should be replaced.

On the Linux box, run '-usr-sbin-tcpdump -i eth0 -env'. You won't be able to see what is in the packets, but what you are looking for is the TCP headers and any ICMP errors. PLEASE DO NOT POST THE DUMP - it will be relatively large, and will contain IP addresses that you probably don't want to publish.

Likewise at home, run a packet sniffer such as ethereal - again, you are looking at the TCP headers and any ICMP stuff.

Agreed.

Doing good - I'd actually suggest setting the MTU (but not MRU if they are separately configurable) AT BOTH ENDS AT THE SAME TIME. An example might be to drop the MTUs to 1350, and look for changes in behavior.

The O-P could also try using traceroute, although it is using UDP by default (ICMP echo is available as an alternative - probably even more useless). The original LBL version of traceroute supplied with Red Hat would use the syntax

usr-sbin-traceroute -i eth0 destina.tion.host.address 1350

and then try again with larger packet lengths UP TO AND INCLUDING in excess of the MTU (which should cause the packets to fragment). If someone is admining the Red Hat box (possibly not given the use of an obsolete release), you might have 'tcptraceroute' (a tcp version of traceroute) or 'hping2' which would use TCP instead of UDP or ICMP for the trace.

I don't know that this would be the case on a stock Red Hat set of scripts. Thesbin-ifconfig command can set MTU, but as far as I recall, Red Hat only allowed for MTU to be specified as a variable on ppp based links. The '-sbin-ifup' script Red Hat used to supply doesn't know about the 'mtu' option to ifconfig.

Old guy