From: "David S. Miller" <davem@redhat.com>
To: bert hubert <ahu@ds9a.nl>
Cc: jamie@shareable.org, shemminger@osdl.org, netdev@oss.sgi.com,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
ALESSANDRO.SUARDI@ORACLE.COM
Subject: Re: window tracking firewall involved, was: Re: preliminary conclusions regarding window size issues
Date: Thu, 8 Jul 2004 08:37:08 -0700 [thread overview]
Message-ID: <20040708083708.5f63bc71.davem@redhat.com> (raw)
In-Reply-To: <20040708063700.GA23496@outpost.ds9a.nl>
On Thu, 8 Jul 2004 08:37:00 +0200
bert hubert <ahu@ds9a.nl> wrote:
> On Thu, Jul 08, 2004 at 08:03:26AM +0200, bert hubert wrote:
>
> [ theory that a window tracking firewall drops packets for which it thinks
> the intended recipient has no room, as they are larger than the window size
> it sees, where it neglects to scale that window size ]
>
> > We could verify this assumption by checking if lowering the MTU to say 700
> > allows wscale=3 to work.
>
> This has now been confirmed with the packages.gentoo.org firewall!
It's the netfilter patches added to the gentoo WOLK kernel running
on packages.gentoo.org
Specifically, it's the tcp-window-tracking patch from netfilter's
patch-o-matic. There's some bug in there wrt. it's window scaling
support.
I bet if the tcp-window-scaling diff is removed from the kernel running
there, the problem will totally go away.
I note that it is using a very old version of the tcp-window-tracking
patch, the current version is 2.2 and probably fixes this bug. The
gentoo linux-2.4.20-wolk-4.14 kernel is using version 1.7
next prev parent reply other threads:[~2004-07-08 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 23:27 preliminary conclusions regarding window size issues bert hubert
2004-07-08 1:44 ` Jamie Lokier
2004-07-08 6:03 ` bert hubert
2004-07-08 6:37 ` window tracking firewall involved, was: " bert hubert
2004-07-08 15:37 ` David S. Miller [this message]
2004-07-08 16:34 ` Martin Josefsson
2004-07-08 21:57 ` Redeeman
2004-07-09 20:24 ` bert hubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040708083708.5f63bc71.davem@redhat.com \
--to=davem@redhat.com \
--cc=ALESSANDRO.SUARDI@ORACLE.COM \
--cc=ahu@ds9a.nl \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.