From: Stephen Hemminger <stephen@networkplumber.org>
To: Marek Kierdelewicz <marek@piasta.pl>
Cc: bridge@lists.linux-foundation.org,
Stephan von Krawczynski <skraw@ithnet.com>,
netdev@vger.kernel.org
Subject: Re: [Bridge] Can linux kernel bridge forward 802.1q tagged vlan packets?
Date: Thu, 22 Aug 2013 15:19:41 -0700 [thread overview]
Message-ID: <20130822151941.301cd36a@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20130822234941.4affc863@catus>
On Thu, 22 Aug 2013 23:49:41 +0200
Marek Kierdelewicz <marek@piasta.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.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Marek Kierdelewicz <marek@piasta.pl>
Cc: bridge@lists.linux-foundation.org,
Stephan von Krawczynski <skraw@ithnet.com>,
netdev@vger.kernel.org
Subject: Re: Can linux kernel bridge forward 802.1q tagged vlan packets?
Date: Thu, 22 Aug 2013 15:19:41 -0700 [thread overview]
Message-ID: <20130822151941.301cd36a@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20130822234941.4affc863@catus>
On Thu, 22 Aug 2013 23:49:41 +0200
Marek Kierdelewicz <marek@piasta.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.
next prev parent reply other threads:[~2013-08-22 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:44 [Bridge] Can linux kernel bridge forward 802.1q tagged vlan packets? Stephan von Krawczynski
2013-08-22 20:44 ` Stephan von Krawczynski
2013-08-22 21:49 ` [Bridge] " Marek Kierdelewicz
2013-08-22 21:49 ` Marek Kierdelewicz
2013-08-22 22:19 ` Stephen Hemminger [this message]
2013-08-22 22:19 ` Stephen Hemminger
2013-08-23 4:22 ` [Bridge] " Stephan von Krawczynski
2013-08-23 4:58 ` Jeff Kirsher
2013-08-26 10:21 ` Stephan von Krawczynski
2013-08-26 10:21 ` Stephan von Krawczynski
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=20130822151941.301cd36a@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=marek@piasta.pl \
--cc=netdev@vger.kernel.org \
--cc=skraw@ithnet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.