Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755663Ab1BWBce (ORCPT ); Tue, 22 Feb 2011 20:32:34 -0500 Received: from mail-vw0-f46.google.com ([209.85.212.46]:38544 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754454Ab1BWBcd (ORCPT ); Tue, 22 Feb 2011 20:32:33 -0500 MIME-Version: 1.0 In-Reply-To: <20110221232902.GA3440@x61s.reliablesolutions.de> References: <20110221232902.GA3440@x61s.reliablesolutions.de> Date: Tue, 22 Feb 2011 17:32:32 -0800 Message-ID: Subject: Re: TX VLAN acceleration on bridges broken in 2.6.37? From: Jesse Gross To: Jan Niehusmann Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1412 Lines: 30 On Mon, Feb 21, 2011 at 3:29 PM, Jan Niehusmann wrote: > With the following configuration, sending vlan tagged traffic from a > bridged interface doesn't work in 2.6.37. > The same configuration does work with 2.6.36: > > - bridge br0 with physical interface eth0 > - eth0 being an e1000e device (don't know if that's important) > - vlan interface br0.10 > - (on 2.6.37) tx vlan acceleration active on br0 (default) > > Networking on br0.10 doesn't work, and tcpdump on eth0 shows packets > sent on br0.10 as untagged, instead of vlan 10 tagged. > > After turning vlan tx offloading off with 'ethtool -K br0 txvlan off', > everything works as expected, again. > > The workaround is made permanent by reverting "bridge: Add support for > TX vlan offload.", 361ff8a6cf90d62c0071b7e532e37369bfd3ae77, turning > of the feature on bridges completely. I tested this at one point and it worked but it sounds like something broke after that. It's probably fairly simple, so I'd rather just fix the problem instead of reverting the commit. I'm just coming back from vacation and am trying to catch up but I'll try to look at it in the next couple of days. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/