| PLEX86 | ||
|
Greater than 1371 Bytes Output Hangs Session 1805I'm a very long way from being a networking expert, but the numbers of bytes are close enough to the normal maximum packet length over ethernet and DSL that my hunch would be it's a packet segmentation issue. Normally, ethernet is set up for 1500 byte maximum packet size. With overhead for IP stack stuff, DSL (and maybe other broadband types), and ssh, it might be that a file of 1371 bytes fits in a single packet while a file of 1372 bytes gets split up somewhere between the endpoints of the network routing path. 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... Failure to put the packets back together to let things work properly might be caused by a problem with stateful firewall state tracking or a bug somewhere else in the network stacks. I would think one way to test this hunch would be to decrease the MTU of the leg of the network path (probably your DSL or other broadband link) and see if that causes 1371-byte files to hang. That's about where even my half-knowledge stops, though. Oh, MTU is set in one of the networking scripts. I know there have been discussions on setting MTU, so a search should find them. -- Robert Riches (Yes, that is one of my email addresses.)
|
||||
Greater than 1371 Bytes Output Hangs Session 1806 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||