From: Tim Nelson <tnelson@rockbochs.com>
To: netfilter@vger.kernel.org
Subject: Re: Bridging / VLANs / ebtables
Date: Sun, 21 Dec 2014 21:37:46 -0600 (CST) [thread overview]
Message-ID: <9818903.380408.1419219466312.JavaMail.root@rockbochs.com> (raw)
In-Reply-To: <30877804.350548.1418834429764.JavaMail.root@rockbochs.com>
----- Original Message -----
> ----- Original Message -----
> > On Tue, Dec 16, 2014 at 03:46:59PM -0600, Tim Nelson wrote:
> > > ----- Original Message -----
> > > > iiuc, you have the following types of packets on eth0:
> > > >
> > > > x.x.x.x/24
> > > > y.y.y.y/24
> > > > z.z.z.z/24
> > > > vlan2:a.a.a.a/24
> > > > vlan3:b.b.b.b/24
> > > >
> > > > So, you need x.x.x.x/24, y.y.y.y/24, and z.z.z.z/24 to get
> > > > routed
> > > > into vlan3. Does traffic need to go the other way? Is there
> > > > broadcast or multicast traffic to worry about?
> > > >
> > >
> > > Greetings Jason-
> > >
> > > Specifically, I have:
> > >
> > > eth0: x.x.x.x/24
> > > eth0.2: y.y.y.y/29
> > > eth0.3: z.z.z.z/24
> > >
> > > After bridging eth0 and eth0.3, devices on eth0.3 will utilize
> > > the
> > > same address space as that present on eth0 native (x.x.x.x/24).
> > > Of
> > > course, traffic to/from eth0.2 would continue to be functional.
> > > Traffic *does* need to operate in both directions, and yes there
> > > will
> > > be broadcast traffic originating from eth0.3, as a DHCP request,
> > > which
> > > would be answered by a DHCP server on the eth0 native connected
> > > network.
> >
> > I'm sure I'm missing something, but a quick test in a VM worked:
> >
> > [root@triton] # brctl show
> > bridge name bridge id STP enabled interfaces
> > br0 8000.00163e1c9a87 no eth126
> > eth126.3
> >
> > eth126.3 did not have an ip address. eth126 did, but you have to
> > set
> > both interfaces promiscuous and 0.0.0.0. Then, assign an IP in the
> > range z.z.z.z/24 to br0.
> >
>
> I've done the same:
>
> root@h4222:~# brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.b827ebbd9e51 no eth0
> eth0.3
>
> I've set both eth0 and eth0.3 to promiscuous mode (ifconfig ethX[.y]
> promisc), and neither eth0 or eth0.3 have an IP, but br0 does. I'm
> not able to communicate with the IP assigned to the bridge from
> either interface.
>
> Thank you very much for the helpful suggestions, it is greatly
> appreciated.
>
*BUMP*
Any thoughts on this? I know it's "odd", but all suggestions welcome and appreciated. Thanks!
--Tim
next prev parent reply other threads:[~2014-12-22 3:37 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
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 [this message]
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=9818903.380408.1419219466312.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