From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27 Date: Mon, 12 Jan 2009 06:27:43 +0100 Message-ID: <496AD4CF.4070807@trash.net> References: <20090109031408.GB11336@gondor.apana.org.au> <20090109115515.GA12486@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: John Dykstra , =?ISO-8859-15?Q?Ilpo_J=E4rv?= =?ISO-8859-15?Q?inen?= , Netdev , bugme-daemon@bugzilla.kernel.org, Andrew Morton , Speedster , Stephen Hemminger , "David S. Miller" To: Herbert Xu Return-path: Received: from stinky.trash.net ([213.144.137.162]:55809 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbZALF2A (ORCPT ); Mon, 12 Jan 2009 00:28:00 -0500 In-Reply-To: <20090109115515.GA12486@gondor.apana.org.au> Sender: netdev-owner@vger.kernel.org List-ID: Herbert Xu wrote: > It turns out that even though we have sysctl's that's supposed > to control pppoe/vlan processing, they don't actually work. Which reminds me - I think we should change them to default to off, they regulary break things for unsuspecting users. I'm not sure though what the best way to warn people for a while would be, feature-removal-schedule doesn't seem approriate. > This patch should make them work. > > bridge: Fix handling of non-IP packets in FORWARD/POST_ROUTING > > Currently the bridge FORWARD/POST_ROUTING chains treats all > non-IPv4 packets as IPv6. This packet fixes that by returning > NF_ACCEPT on non-IP packets instead, just as is done in PRE_ROUTING. Applied, thanks.