From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [netfilter-core] Re: [PATCH] ip_conntrack_proto_tcp Date: Fri, 11 Nov 2005 14:58:01 +0100 Message-ID: <4374A369.6020308@trash.net> References: <1131637730.14044.12.camel@quant> <437495E7.5050500@eurodev.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: coreteam@netfilter.org, Vlad Drukker , netfilter-devel@lists.netfilter.org Return-path: To: Pablo Neira In-Reply-To: <437495E7.5050500@eurodev.net> 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 Pablo Neira wrote: > Vlad Drukker wrote: > >>Attached patch for ip_conntrack to account TCP sessions started with SYN >>+PUSH flags. Looks weird, but some HW vendors do TCP their own way. >> >>Let's earn some points from RFC 1025. > > I see this patch like a sort of workaround to make broken devices with > the TCP connection tracking, right? In that case, I don't think that > it's a good idea polluting our code with workarounds for every existing > broken device. The HW vendors must fix their devices. Unfortunately this is unlikely to happen, and if Linux itself accepts SYN|PSH, I don't see a reason why ip_conntrack shouldn't as well.