From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridging untagged and tagged VLANs
Date: Wed, 22 Jul 2009 23:14:11 +0200 [thread overview]
Message-ID: <4A678123.1020006@free.fr> (raw)
In-Reply-To: <4A677ACA.3060100@ipfire.org>
Michael Tremer wrote:
> Oops, just sent the email when your one scrabbled to my inbox.
>
> https://lists.linux-foundation.org/pipermail/bridge/2009-July/006626.html
>
> I applied that ebtables rule to the chain but no packages got to the
> vlan interface (eth0.30) anymore.
>
> Michael
For as far as I remember, this hack works really well when eth0 and
eth0.30 are not in the same bridge (br0/br1). Anyway, I cannot think of
a good reason for it not to work in a single bridge.
Try and dig around with ebtable, using the logging feature. Im' pretty
sure it works, but does not have a bridge available here to test.
I googled around to try and find the original web page where a learned
this hack, but without any success. You can try, searching for
ebtables+BROUTING+DROP+802_1Q+vlan-id and so on...
Nicolas.
next prev parent reply other threads:[~2009-07-22 21:14 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
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 [this message]
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=4A678123.1020006@free.fr \
--to=nicolas.2p.debian@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox