From: Phil Oester <kernel@linuxace.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@lists.netfilter.org,
Ludwig Nussel <ludwig.nussel@suse.de>
Subject: Re: TCP window tracking has bad side effects
Date: Wed, 1 Dec 2004 16:54:54 -0800 [thread overview]
Message-ID: <20041202005454.GA14803@linuxace.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0412011308520.27175@blackhole.kfki.hu>
On Wed, Dec 01, 2004 at 01:16:31PM +0100, Jozsef Kadlecsik wrote:
> Yes, you can disable it anytime:
>
> echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
>
> But a full tcpdump from such a session and the log entries on the
> invalid packets would be useful for us to recheck the code.
This sounds remarkably similar to bugzilla #258, where a TCP
session which works in 2.6.8.1 fails in 2.6.9:
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=258
Attached to the report is a binary tcpdump. I've replayed it
and tried a few things but can't figure out what the problem
is.
Disabling window tracking did nothing -- were there any other
interesting changes in 2.6.9 series?
Phil
prev parent reply other threads:[~2004-12-02 0:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 11:02 TCP window tracking has bad side effects Ludwig Nussel
2004-12-01 12:16 ` Jozsef Kadlecsik
2004-12-01 15:39 ` Ludwig Nussel
2004-12-03 8:44 ` Jozsef Kadlecsik
2004-12-06 8:35 ` Jozsef Kadlecsik
2004-12-09 16:26 ` Ludwig Nussel
2004-12-10 10:03 ` Jozsef Kadlecsik
2004-12-10 20:32 ` David S. Miller
2004-12-10 22:14 ` Jozsef Kadlecsik
2004-12-10 17:22 ` Bill Rugolsky Jr.
2004-12-10 19:42 ` Jozsef Kadlecsik
2004-12-10 19:51 ` David S. Miller
2005-01-10 17:13 ` Jan Du Caju
2005-01-10 17:16 ` Phil Oester
2004-12-02 0:54 ` Phil Oester [this message]
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=20041202005454.GA14803@linuxace.com \
--to=kernel@linuxace.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=ludwig.nussel@suse.de \
--cc=netfilter-devel@lists.netfilter.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.