Date: Thu, 11 Jul 2002 15:39:32 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Alex Dyas <alexdyas@hotmail.com> Cc: net@freebsd.org Subject: Re: BSD / Firewall / 0 window size problem Message-ID: <20020711153621.O33106-100000@patrocles.silby.com> In-Reply-To: <F255DapE6dEeQkhtzmC0000d00a@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Jul 2002, Alex Dyas wrote: > The only clue I've managed to find as to what is going on is in a tcpdump of > the session (attached). The trigger for the lock up seems to be a messages > from the Otherbox machine setting the window size to 0 : > > 10:41:38.614141 otherbox.foo.com.telnet > bsdbox.foo.com.2230: . ack 154 win > 0 > 10:41:38.614200 bsdbox.foo.com.2230 > otherbox.foo.com.telnet: . ack 337 win > 33304 <nop,nop,timestamp 9026230 147804149> (DF) [tos 0x10] > > I've tried all the following scenarios, none of which exhibit the same > problem, which is why I think the problem is with FreeBSD : > > bsdbox.foo.com -> otherbox.foo.com > solarisbox.foo.com -> internal GNAT firewall -> otherbox.foo.com > windowsbox.foo.com -> internal GNAT firewall -> otherbox.foo.com > linuxbox.foo.com -> internal GNAT firewall -> otherbox.foo.com Could you post a tcpdump of one of the successful connections so that we can see how 0 windows are handled there? Also, have you tcpdump'd at both ends to ensure that we're not actually seeing odd sideeffects of packet loss or something? (Some reported problems in the past have been due to misbehaving duplex autodetect and bad cables.) Offhand, I can't see what the FreeBSD box is doing wrong, but I'd like something else to compare to. Thanks, Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020711153621.O33106-100000>