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: bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [Bridge] VLANs and bridge
Date: Sat, 22 Aug 2009 10:12:10 -0700	[thread overview]
Message-ID: <4A9026EA.9020404@superduper.net> (raw)
In-Reply-To: <OF9BD07CB5.A2197AEA-ONC125761A.005AE004-C125761A.005B662E@transmode.se>

Looking through B.1.3 it looks like the patch would need some 
enhancement. It provides a good basis - handling tagging/untagging and 
filtering, but would need a way to specify the untagged vlan separately 
for in and out.

Simon


Joakim Tjernlund wrote:
> Joakim Tjernlund/Transmode wrote on 22/08/2009 17:36:54:
>   
>> Simon Barber <simon@superduper.net> wrote on 22/08/2009 16:34:11:
>>     
>>> 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
>>>
>>>       
>> Thanks Simon
>>
>> Do you mean the "bridge vlan integration" patch?
>> It is not clear to me if this would support the case
>> described in B.1.3(802.1Q-2005), does it?
>>
>> Seems like there is little interest to post this to 2.6 and
>> I am not sure how welcome this would be either, perhaps
>> the bridge maintainer could comment?
>>
>>   Jocke
>>     
>
> Thinking a bit more about this I could envision some changes to the
> vlan code too. I image one could create one vlan interface which will listen
> to several VLANs. One VLAN is the primary VLAN and is used in the tx path
> by default. The bridge would be able to filter on individual VLANs received
> from such interface and be able to chose outgoing VLAN too.
>
>  Jocke
>
>   


  reply	other threads:[~2009-08-22 16:52 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
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 [this message]
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=4A9026EA.9020404@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).