From: Simon Barber <simon@superduper.net>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridging untagged and tagged VLANs
Date: Tue, 21 Jul 2009 20:49:29 -0700 [thread overview]
Message-ID: <4A668C49.7080209@superduper.net> (raw)
In-Reply-To: <4A6638A5.208@ipfire.org>
To do this seamlessly you need a VLAN aware bridge - the kernel has
separate support for VLAN and bridging, but not integrated. I posted a
patch a while back to fix this - see here:
http://www.mail-archive.com/bridge@lists.osdl.org/msg01440.html
It was for a 2.4 kernel, but shouldn't take too much work to port to 2.6.
Simon
Michael Tremer wrote:
> 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
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>
next prev parent reply other threads:[~2009-07-22 3:49 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
2009-07-22 8:55 ` Benny Amorsen
2009-07-22 3:49 ` Simon Barber [this message]
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=4A668C49.7080209@superduper.net \
--to=simon@superduper.net \
--cc=bridge@lists.linux-foundation.org \
--cc=michael.tremer@ipfire.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.