From: Michael Tremer <michael.tremer@ipfire.org>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Bridging untagged and tagged VLANs
Date: Tue, 21 Jul 2009 23:52:37 +0200 [thread overview]
Message-ID: <4A6638A5.208@ipfire.org> (raw)
Hello everybody,
I got a weird problem but don't know if it is expected to work.
brctl addbr br0
vconfig add eth0 30
brctl addif br0 eth0.30
Until here, everythink works well... I can access the VLAN with id 30.
But when I run the following:
brctl addif br0 eth0
Then, I can't access the VLAN any more but the untagged LAN.
But instead of adding eth0:
vconfig add eth0 40
brctl addif br0 eth0.40
It works.
It would be nice if you can me give a short advice...
Is it not possible to bridge an untagged LAN with a tagged VLAN or
is this a bug?
Sincerely,
Michael
Kernel 2.6.29, brctl 1.4
next reply other threads:[~2009-07-21 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 21:52 Michael Tremer [this message]
2009-07-21 22:59 ` [Bridge] Bridging untagged and tagged VLANs richardvoigt
2009-07-22 8:51 ` Benny Amorsen
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=4A6638A5.208@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=bridge@lists.linux-foundation.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