From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: iptables / ebtables IP address intercept
Date: Fri, 06 Aug 2010 16:07:44 -0500 [thread overview]
Message-ID: <4C5C79A0.8060607@riverviewtech.net> (raw)
In-Reply-To: <FC97946E765591E436489FAE@nimrod.local>
On 08/04/10 03:08, Alex Bligh wrote:
> R1 might or might not be connected to BBI, or R1/C1 might be in 1918
> space
Ok.
> OK - that looks promising. I'd only investigated iptables & ebtables.
*nod*
> Note BBI hangs of BR1 not R1 - I think that makes things easier.
Seeing as how BR1 is a bridge and router, it doesn't make that much
difference.
> I presume there is a route step here, but C1' is designed to be on
> the correct interface.
Yes.
The reply traffic will be routed at layer 3, and then at layer 2 will be
altered from the one layer 3 (that was routed) to the proper layer 3
(that isn't routed).
> Sure - thanks.
I've done some more thinking and I strongly believe that what needs to
be done can be, I just don't have a way to test this at the moment. (I
will see if I have some time this weekend to throw together a VM.)
> That's actually quite simple, as because BBI is not behind R1, all
> the non-intercepted traffic is simply bridged.
*nod*
Grant. . . .
prev parent reply other threads:[~2010-08-06 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 14:24 iptables / ebtables IP address intercept Alex Bligh
2010-08-03 16:54 ` Grant Taylor
2010-08-03 18:06 ` Alex Bligh
2010-08-03 20:23 ` Grant Taylor
2010-08-04 8:08 ` Alex Bligh
2010-08-06 21:07 ` Grant Taylor [this message]
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=4C5C79A0.8060607@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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