From: Tim Nelson <tnelson@rockbochs.com>
To: netfilter@vger.kernel.org
Subject: Re: Bridging / VLANs / ebtables
Date: Mon, 22 Dec 2014 09:24:14 -0600 (CST) [thread overview]
Message-ID: <14852223.382712.1419261854310.JavaMail.root@rockbochs.com> (raw)
In-Reply-To: <CAPJdpdD+Ziiy_keV=Re92-v53PtMA8N7XK6rKXYHvzj3QJcOQg@mail.gmail.com>
----- Original Message -----
> I get the scenario but not the why. Is it a subset of specific things
> you need to do a layer 2 bridge for or do you need it for something
> else.
>
> For example I have a firewall where I need to forward broadcast
> (255.255.255.255,xxx.xxx.xxx.255) messages between different segments
> in the network. Most people would think of bridging for this but I
> did
> something completely different involving setting both interfaces to a
> /32, adding a static route for each subnet, adding a static arp table
> entry on each interface for the broadcast IP addresses mapped to the
> broadcast mac addresses then simple iptables rules.
>
Greetings Paul-
I believe you mentioned this previously. While the mechanism is 'different', does the end result still operate the same, allowing a device on one interface to have an IP from the other interface, and still operate as though a bridge was in place?
Thank you,
--Tim
next parent reply other threads:[~2014-12-22 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPJdpdD+Ziiy_keV=Re92-v53PtMA8N7XK6rKXYHvzj3QJcOQg@mail.gmail.com>
2014-12-22 15:24 ` Tim Nelson [this message]
2014-12-22 21:15 ` Bridging / VLANs / ebtables Paul Robert Marino
[not found] <549119ce.ca25e00a.053d.1a62@mx.google.com>
2014-12-17 17:30 ` Tim Nelson
[not found] <4829673.301498.1418414563731.JavaMail.root@rockbochs.com>
2014-12-12 20:03 ` 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
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
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=14852223.382712.1419261854310.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