Date: Sun, 22 Apr 2007 16:33:16 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Rui Paulo <rpaulo@fnop.net> Cc: freebsd-current@freebsd.org, Andre Oppermann <andre@freebsd.org> Subject: Re: rfc1323 problems (was: network problems?) Message-ID: <20070422143316.GP41664@obiwan.tataz.chchile.org> In-Reply-To: <86k5w67shd.wl%rpaulo@fnop.net> References: <46272B99.9090100@bulinfo.net> <20070419223759.GA4051@turion.vk2pj.dyndns.org> <462868FF.2050008@bulinfo.net> <4628A6A0.40102@freebsd.org> <86k5w67shd.wl%rpaulo@fnop.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi list, On Fri, Apr 20, 2007 at 08:31:26PM +0100, Rui Paulo wrote: > At Fri, 20 Apr 2007 13:40:16 +0200, > Andre Oppermann wrote: > > 7-current uses larger receive windows with a higher scaling factor. > > If your firewall doesn't correctly track that you get the problem > > you are describing. In pf based firewalls it is a common thing to > > misplace the keep-state rule. > > I have another problem. I'm trying to talk to a host (MontaVista Linux > based router/AP) that is on the same network segment. If rfc1323 is > on, I can't browse the router's webpage: after a few bytes transfered, > I only seep TCP keep alive packets. But a telnet connection works well. > > If I disable rfc1323, everything works as expected. > > Maybe this is related to PAWS, but I don't the router at hand. > > If you need a tcpdump, I can only give it to you during the upcoming > week. Same problem here with a Linux-based Linksys router. I'm running -CURRENT as of 2007.04.11.20.00.00, disabling rfc1323 solves the problem. Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070422143316.GP41664>