Xref: utzoo comp.protocols.tcp-ip:14759 comp.protocols.tcp-ip.ibmpc:4841 comp.unix.xenix.sco:1602 comp.unix.xenix.misc:96 comp.unix.sysv386:4598 comp.unix.sysv286:121 Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc,comp.unix.xenix.sco,comp.unix.xenix.misc,comp.unix.sysv386,comp.unix.sysv286 Subject: 3c501 users please read this Message-ID: Date: 5 Feb 91 20:50:01 GMT Sender: @grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 19 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". -- --russ Humble Quaker, and damned proud of it. It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.