Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Tim Nelson <tnelson@rockbochs.com>
To: netfilter@vger.kernel.org
Subject: Re: Bridging / VLANs / ebtables
Date: Tue, 16 Dec 2014 15:46:59 -0600 (CST)	[thread overview]
Message-ID: <31506370.345790.1418766419268.JavaMail.root@rockbochs.com> (raw)
In-Reply-To: <20141216213425.GU967@titan.lakedaemon.net>

----- 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.

Thanks!

--Tim

  reply	other threads:[~2014-12-16 21:46 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 [this message]
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=31506370.345790.1418766419268.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