netdev - Re: [Bridge] Can linux kernel bridge forward 802.1q tagged vlan packets?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130823062234.c34a6da6.skraw@ithnet.com>
Date:	Fri, 23 Aug 2013 06:22:34 +0200
From:	Stephan von Krawczynski <skraw@...net.com>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	Marek Kierdelewicz <marek@...sta.pl>,
	bridge@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: [Bridge] Can linux kernel bridge forward 802.1q tagged vlan
 packets?

On Thu, 22 Aug 2013 15:19:41 -0700
Stephen Hemminger <stephen@...workplumber.org> wrote:

> On Thu, 22 Aug 2013 23:49:41 +0200
> Marek Kierdelewicz <marek@...sta.pl> wrote:
> 
> > Hi,
> > 
> > >My general idea is to bridge tagged vlan packets from a physical
> > >interface (intel) to a virtual interface (virtio in qemu) and not
> > >losing the tags, so the qemu guest can use vconfig and friends to get
> > >some vlan interfaces. Is this possible and are there any additional
> > >steps necessary besides the usual bridge configuration?
> > 
> > I'm using this setup with KVM virtualization (Qemu's successor). It
> > didn't work with default nic type for guest (realtek I think) as 802.1q
> > tags were not preserved properly in one of the directions. I don't
> > remember specifics. Anyway using e1000 driver instead of default fixed
> > it. Works like a charm.
> 
> KVM e1000 Vnic doesn't do VLAN offloading at least in my experience.
> Virtio works fine.

Ok guys, here is one of the major questions in this issue:

How did you manage to convince the _host_ interface driver (in my setup "igb"
from intel) to get the vlan tagged packets from the LAN port. igb has a vlan
filter function built in and reads _no_ tagged packets at all if the driver
does not tell it to. And in case of "up-ing" the interface for attachment to a
bridge it does not configure this vlan filter.
How is this expected to work?

-- 
Regards,
Stephan

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html