From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Oester Subject: Re: TCP window tracking has bad side effects Date: Wed, 1 Dec 2004 16:54:54 -0800 Message-ID: <20041202005454.GA14803@linuxace.com> References: <20041201110253.GA9536@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@lists.netfilter.org, Ludwig Nussel Return-path: To: Jozsef Kadlecsik Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org 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