3c501 users please read this
opnrhen at acsu.buffalo.edu
Thu Feb 7 11:08:13 AEST 1991
In article <NELSON.91Feb5145001 at sun.clarkson.edu> nelson at clutx.clarkson.edu (aka NELSON at CLUTX.BITNET) writes:
>Sorry to post this so widely, but since the question has come up
>recently twice on the net, and twice locally to Clarkson, people
>should be aware of this problem.
>The 3c501 cannot receive back-to-back packets (two packets addressed
>to the same host with no intervening packet). BSD Unix (well, SunOS
>and NeXTos at least) will attempt to fill your TCP window by sending
>back-to-back packets. Therefore, your TCP Window must not be larger
>than your TCP MSS.
> o Under KA9Q, use "tcp window 1024" and "tcp mss 1024".
> o Under SCO Xenix, use the UNDOCUMENTED ifconfig option -onepacket.
> o Under NCSA Telnet, use "maxseg=1024" and "rwin=1024".
> o Under FTP Software's PC/TCP, use "ipconfig window 1024".
I've run into situations where it may be necessary to reduce
the tcp and mss window sizes down as low as 512 to prevent excessive
retransmits. Many TCP implimentations will use 512 mss packets if they
think that the packet is leaving the local network. (This is recommended
based on 576 MTU in gateway requirements in the absense of MTU discovery.)
With local subnetting and high performance routers two short back to back
back packets can be generated within the available the the receive window,
causing the same poor performance.
University at Buffalo
opnrhen at ubvms.cc.buffalo.edu
More information about the Comp.unix.xenix.misc