From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: Re: VLAN test cases in 2.6.38.7
Date: Tue, 24 May 2011 12:08:38 -0700 [thread overview]
Message-ID: <4DDC0236.4090800@candelatech.com> (raw)
In-Reply-To: <4DDBFDD6.4060903@candelatech.com>
On 05/24/2011 11:49 AM, Ben Greear wrote:
>
> I wrote a simple bridge that uses packet sockets to read/write
> from network devices. I'll upload this code somewhere when
> I get it a bit more presentable.
>
> Machine info:
>
> Linux lf0300-demo 2.6.38.7+ #14 SMP Mon May 23 10:31:45 PDT 2011 i686
> i686 i386 GNU/Linux
>
> Interface A: eth1
> driver: igb
> version: 3.0.19
> firmware-version: 1.2-1
> bus-info: 0000:01:00.0
>
> Interface B: eth3:
> driver: igb
> version: 3.0.19
> firmware-version: 1.2-1
> bus-info: 0000:01:00.1
>
>
> If no vlans are on eth1 and eth3, then it bridges fine, with vlan
> headers inline. But, if you add a VLAN to eth1, it stops working,
> probably because pkt tag is then un-stripped. I was generating on
> vlan 7, and created vlan 9, btw.
>
> I'll see if I can figure out how to use aux-data next...
Why does the aux-data mask out the CFI bit? Shouldn't
we just pass the 16-bit VLAN tag un-modified to user-space?
Thanks,
Ben
>
> Thanks,
> Ben
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-24 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 18:49 VLAN test cases in 2.6.38.7 Ben Greear
2011-05-24 19:08 ` Ben Greear [this message]
2011-05-24 22:52 ` Ben Greear
2011-05-25 0:34 ` Ben Greear
2011-05-25 2:47 ` David Miller
2011-05-25 3:33 ` Ben Greear
2011-05-25 18:49 ` 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=4DDC0236.4090800@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).