From: Jan Niehusmann <jan@gondor.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: TX VLAN acceleration on bridges broken in 2.6.37?
Date: Tue, 22 Feb 2011 00:29:02 +0100 [thread overview]
Message-ID: <20110221232902.GA3440@x61s.reliablesolutions.de> (raw)
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.
Jan
next reply other threads:[~2011-02-21 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 23:29 Jan Niehusmann [this message]
2011-02-23 1:32 ` Jesse Gross
2011-02-25 22:53 ` Jesse Gross
2011-02-26 0:19 ` Jan Niehusmann
2011-02-26 1:16 ` Jesse Gross
2011-02-26 1:22 ` Jeff Kirsher
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=20110221232902.GA3440@x61s.reliablesolutions.de \
--to=jan@gondor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®