From: "Michael Walle" <michael@walle.cc>
To: linux-kernel@vger.kernel.org
Subject: dropped packets with bonding and 8021q
Date: Wed, 19 Aug 2009 12:29:42 +0200 (CEST) [thread overview]
Message-ID: <9e8b01b1556687e0b78ca63dfb5ca8dc.squirrel@ssl.serverraum.org> (raw)
Hi,
i have some strange bonding and vlan configuration. The bonding interface
is in active-standby mode and i want to send and receive raw ethernet
frames on _both_ enslaved interfaces. Additionally the frames are tagged
with a vlan id. So one config could be:
# modprobe bonding mode=1
# modprobe 8021q
# ifenslave bond0 eth1
# ifenslave bond0 eth2
# vconfig add eth1 10
# vconfig add eth2 20
# vconfig add bond0 1000
# [activate bonding active slave etc..]
I use raw/dgram sockets (AF_PACKET) with eth1.10 and eth2.20 (or dump the
frames with tcpdump).
As long as i don't use the bonding module everything works as expected.
But if the physical interfaces are enslaved, frames received on the
standby device will be dropped.
The network driver is e1000. So the hardware acceleration for tagged VLAN
frames gets used and the frame gets through __vlan_hwaccel_rx() in the
receiving path. And there it seems to get dropped by
skb_bond_should_drop().
On the "normal" receive path there was a patch by Joe Eykholt that allows
to receive frames on the physical interface even if it is enslaved and not
active (git commit 0d7a3681232f545).
Shouldn't __vlan_hwaccel_rx() (in net/8021q/vlan_core.c) be patched in the
same way to allow reception on inactive enslaved interfaces?
Thanks,
Michael
PS. could you please cc me, as i'm not subscribed to the ml.
next reply other threads:[~2009-08-19 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 10:29 Michael Walle [this message]
2009-08-27 22:22 ` Jesse Brandeburg
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=9e8b01b1556687e0b78ca63dfb5ca8dc.squirrel@ssl.serverraum.org \
--to=michael@walle.cc \
--cc=linux-kernel@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
Powered by JetHome