Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: ka9q configuration Message-ID: Date: 17 Apr 91 03:30:38 GMT References: <9104160849.aa09417@dribble.c-mols.siu.EDU> Sender: usenet@grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 18 In-Reply-To: dan@dribble.c-mols.siu.edu's message of 16 Apr 91 13:49:38 GMT In article <9104160849.aa09417@dribble.c-mols.siu.EDU> dan@dribble.c-mols.siu.edu (Dan Ellison) writes: ip ttl 16 This ttl is too low. For example, it's twenty hops between MIT and my PC. I use 255. Since the value is only there to prevent zombie packets, you're not hurt much by too-high values, but you're hurt greatly by too-low values. tcp mss 216 tcp window 1500 That's an awfully small mss value. I'd use tcp mss 1024 and window 4096, unless I was using a 3c501, in which case I'd use a window of 1024 also. -- --russ I'm proud to be a humble Quaker. 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.