netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: mbizon@freebox.fr
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: Re: VLAN rx acceleration bypasses bridge
Date: Sat, 24 Oct 2009 11:11:52 -0700	[thread overview]
Message-ID: <20091024111152.6299a203@nehalam> (raw)
In-Reply-To: <1255564685.21615.131.camel@sakura.staff.proxad.net>

On Thu, 15 Oct 2009 01:58:05 +0200
Maxime Bizon <mbizon@freebox.fr> wrote:

> 
> Hi Patrick, Stephen & all,
> 
> 
> If I do:
> 
> # vconfig add eth0 100
> # brctl addbr br0
> # brctl addif br0 eth0
> 
> Then eth0.100 gets no more packet and br0.100 should be used instead to
> get tagged packets.
> 
> But, if vlan rx acceleration is enabled on eth0, then vlan 100 packets
> no longer go through bridge, and eth0.100 is to be used instead.
> 
> This is fixable, but I'm not sure which behavior is preferred ?
> 
> 
> In case we prefer the first one, how could someone bridge untagged
> packets from eth0 with some tagged packets from eth1, and some tagged
> packets from eth0 with untagged packets from eth1 ?
> 
> Something like this, which currently works when vlan rx accel is on:
> 
> # vconfig add eth0 100
> # vconfig add eth1 100
> # brctl addbr br0
> # brctl addif br0 eth0
> # brctl addif br0 eth1.100
> # brctl addbr br1
> # brctl addif br1 eth0.100
> # brctl addif br1 eth1
> 
> 
> Regards,
> 

The way I see it, if you define a vlan then you need to bridge that
vlan. Mixing plain and vlanned interfaces is a mess that is hard to untangle
and probably not worth fixing.

      reply	other threads:[~2009-10-24 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 23:58 VLAN rx acceleration bypasses bridge Maxime Bizon
2009-10-24 18:11 ` Stephen Hemminger [this message]

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=20091024111152.6299a203@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=kaber@trash.net \
    --cc=mbizon@freebox.fr \
    --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).