netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: VLANs and bridge
Date: Sat, 22 Aug 2009 07:34:11 -0700	[thread overview]
Message-ID: <4A9001E3.6060506@superduper.net> (raw)
In-Reply-To: <OFC5BA9A4A.DCCE8D0D-ONC125761A.004A7620-C125761A.004BEA17@transmode.se>

Hi Joakim,

Look back a month or so in the archives - you'll find an email from me 
referencing a patch to make the bridge VLAN aware. It's a little old, 
and needs updating for 2.6 (it was written for 2.4) - but should not be 
much work to get it done. There is a matching patch for the brctl utility.

Simon


Joakim Tjernlund wrote:
> This is probably no news to experienced bridge and VLAN users but I just learned the
> hard way that Shared VLAN learning(SVL) isn't supported
> by the linux bridge making it impossible to support configurations described in B.1.3
> Basically the bride needs to be made VLAN aware and the VLAN code needs to be adopted
> to allow this.
>
> I figured I should mention it in case it is just an oversight. It does not look like a simple
> job though.
>
>  Jocke
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>   

  reply	other threads:[~2009-08-22 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22 13:49 VLANs and bridge Joakim Tjernlund
2009-08-22 14:34 ` Simon Barber [this message]
2009-08-22 15:36   ` [Bridge] " Joakim Tjernlund
     [not found]   ` <OF2C06F138.1BC279AE-ONC125761A.0054117B-C125761A.0055C6F1@LocalDomain>
2009-08-22 16:38     ` Joakim Tjernlund
2009-08-22 17:12       ` Simon Barber
2009-08-24 18:51         ` Joakim Tjernlund
2009-08-25 14:00           ` Patrick McHardy
2009-08-26  6:56             ` Joakim Tjernlund

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=4A9001E3.6060506@superduper.net \
    --to=simon@superduper.net \
    --cc=bridge@lists.linux-foundation.org \
    --cc=joakim.tjernlund@transmode.se \
    --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).