From: Tim Nelson <tnelson@rockbochs.com>
To: netfilter@vger.kernel.org
Subject: Re: Bridging / VLANs / ebtables
Date: Mon, 15 Dec 2014 19:20:03 -0600 (CST) [thread overview]
Message-ID: <5194407.335095.1418692803168.JavaMail.root@rockbochs.com> (raw)
In-Reply-To: <12631645.301499.1418414592170.JavaMail.root@rockbochs.com>
----- Original Message -----
> Greetings-
>
> I have an interesting situation that requires bridging some VLAN
> enabled interfaces together on a Debian 7.x x86 system. On the host,
> there is a single physical interface passing traffic natively
> (eth0), and two tagged VLANs also passing traffic (eth0.2 and
> eth0.3).
>
> The use case is that I need to bridge eth0 with eth0.2, allowing
> layer two traffic to pass seamlessly between interfaces, and still
> leave eth0.3 in a usable state. The switch this system is connected
> to is outside of my control, which is the reason for the odd network
> setup.
>
> What I'm finding by simply creating a new bridge br0 with members
> eth0 and eth0.2 is no connectivity on eth0.2, and slow/quirky
> connectivity on eth0 (native connectivity to Debian 7.x host). In
> doing research, I've found suggestions of adding the VLAN interfaces
> to the bridge direct, resulting in a br0, br0.2, and br0.3, but the
> results were the same.
>
> It has been suggested to use ebtables to filter the VLANs from the
> eth0 interface on the bridge, yet allow operation to the system
> interface eth0.2/eth0.3. I found a very specific reference on the
> ebtables site for this scenario [1], usage suggested (modified to
> fit my environment):
>
> ebtables -t broute -A BROUTING -i eth0 -p 802_1Q --vlan-id 3 -j DROP
> ebtables -t broute -A BROUTING -i eth0 -p 802_1Q --vlan-id 2 -j DROP
>
> If my understanding of the ebtables usage as a brouter, and the
> kernel's interaction between all components involved, this should
> work. However, as noted, no change in operation is observed.
>
> I'm hoping someone can shed light on what needs to be done for a
> successful bridge of eth0/eth0.2, with an intact eth0.3 (point to
> point link between Debian 7.x host and another device). I posted
> this to the debian-users list but given the wide audience, was not
> successful in getting relevant content.
>
> All tips/tricks/suggestions welcome.
>
> Thank you,
>
> --Tim
>
> [1] http://ebtables.netfilter.org/misc/brnf-faq.html#quiz2
**bump** Any thoughts? Thanks!
--Tim
next prev parent reply other threads:[~2014-12-16 1:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4829673.301498.1418414563731.JavaMail.root@rockbochs.com>
2014-12-12 20:03 ` Bridging / VLANs / ebtables Tim Nelson
2014-12-16 1:20 ` Tim Nelson [this message]
2014-12-16 9:01 ` Akshat Kakkar
2014-12-16 14:56 ` Paul Robert Marino
2014-12-16 21:16 ` Tim Nelson
2014-12-16 21:15 ` Tim Nelson
2014-12-16 21:34 ` Jason Cooper
2014-12-16 21:46 ` Tim Nelson
2014-12-17 2:41 ` Jason Cooper
2014-12-17 16:40 ` Tim Nelson
2014-12-22 3:37 ` Tim Nelson
2014-12-17 2:55 ` Jason Cooper
2014-12-17 4:41 ` Akshat Kakkar
2014-12-17 16:56 ` Tim Nelson
2014-12-17 16:51 ` Tim Nelson
[not found] <549119ce.ca25e00a.053d.1a62@mx.google.com>
2014-12-17 17:30 ` Tim Nelson
[not found] <CAPJdpdD+Ziiy_keV=Re92-v53PtMA8N7XK6rKXYHvzj3QJcOQg@mail.gmail.com>
2014-12-22 15:24 ` Tim Nelson
2014-12-22 21:15 ` Paul Robert Marino
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=5194407.335095.1418692803168.JavaMail.root@rockbochs.com \
--to=tnelson@rockbochs.com \
--cc=netfilter@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