From: Benny Amorsen <benny+usenet@amorsen.dk>
To: bridge@osdl.org
Subject: Re: [Bridge] Bridging untagged and tagged VLANs
Date: Wed, 22 Jul 2009 10:51:14 +0200 [thread overview]
Message-ID: <m3fxcpdrst.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: 2e59e6970907211559t1bf1c776r8684d59e98f96069@mail.gmail.com
"richardvoigt@gmail.com" <richardvoigt@gmail.com> writes:
> I don't think Linux VLAN support provides a way to separate packets
> with _no_ VLAN header onto a virtual interface, but that surely sounds
> useful.
It would be handy if VLAN 0 meant "packets tagged with VLAN 0 + packets
without tags". The VLAN 0 tag is reserved for packets in the native VLAN
which need 802.1p priority.
Then you could bridge eth0.0 and eth0.30 for the desired effect.
/Benny
next prev parent reply other threads:[~2009-07-22 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 21:52 [Bridge] Bridging untagged and tagged VLANs Michael Tremer
2009-07-21 22:59 ` richardvoigt
2009-07-22 8:51 ` Benny Amorsen [this message]
2009-07-22 8:55 ` Benny Amorsen
2009-07-22 3:49 ` Simon Barber
2009-07-22 7:35 ` Michael Tremer
2009-07-22 20:30 ` Nicolas de Pesloüan
2009-07-22 20:47 ` Michael Tremer
2009-07-22 21:14 ` Nicolas de Pesloüan
2009-07-23 7:54 ` Michael Tremer
2009-07-22 20:41 ` Michael Tremer
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=m3fxcpdrst.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=bridge@osdl.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