From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: Problem with igb and vlans in 2.6.38-rc4
Date: Thu, 10 Feb 2011 09:57:01 -0800 [thread overview]
Message-ID: <4D5426ED.7000801@candelatech.com> (raw)
We have a user-space app that uses packet-sockets to grab and send
Ethernet frames (basically a user-space bridge).
This has stopped working for VLANs unless we set the physical
port MTU to be vlan-MTU + 4 (ie, 1504 for standard MTU size vlan frames).
I think this started post 2.6.34 kernel..but not exactly sure at this
time.
The test setup is essentially:
client -- vlan 5 -- [ eth4 {software-bridge} eth3 ] -- vlan 5 -- server
The software bridge machine has no VLANs enabled..it is supposed to just
read Ethernet frames from one port and xmit out the other.
The bridge machine sees rx-length errors, and if only one port is
set to 1504, the other shows xmit errors (since it doesn't like sending
a frame 4 bytes larger than MTU probably).
This used to work, and I'm hoping this change wasn't done on purpose.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2011-02-10 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 17:57 Ben Greear [this message]
2011-02-10 20:51 ` Problem with igb and vlans in 2.6.38-rc4 Ben Greear
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=4D5426ED.7000801@candelatech.com \
--to=greearb@candelatech.com \
--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;
as well as URLs for NNTP newsgroup(s).