From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Redirecting ports in a bridge
Date: Wed, 23 Apr 2008 12:16:30 -0500 [thread overview]
Message-ID: <480F6EEE.9010201@riverviewtech.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0804231722570.13697@fbirervta.pbzchgretzou.qr>
On 04/23/08 10:24, Jan Engelhardt wrote:
> Often layer-2 transparency is not needed, but what do I know. If you
> just log layer-3 (IP addrs) and up without caring about MAC
> addresses, make a standard routing setup, i.e. 192.168.1.0/22 on
> eth0, 192.168.2.0/22 on eth1, and enable forwarding; kinda like that.
> And let hosts use 192.168.1.1/192.168.2.1 as a default gw (as they
> already should do).
If it was not for the fact that the OP wanted layer 3 transparency, I
would agree with you. However the desire to insert this between a
router and one or more systems with out changing the IP addressing
necessitates the use of layer 2 technology, i.e. bridging.
Grant. . . .
next prev parent reply other threads:[~2008-04-23 17:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 9:27 Redirecting ports in a bridge Javier Prieto Martínez
2008-04-18 10:35 ` Jan Engelhardt
2008-04-18 10:55 ` Javier Prieto Martínez
2008-04-18 11:29 ` Jan Engelhardt
2008-04-18 11:41 ` Javier Prieto Martínez
2008-04-18 12:26 ` Marc Cozzi
2008-04-18 12:34 ` Javier Prieto Martínez
2008-04-23 15:25 ` Jan Engelhardt
2008-04-18 14:38 ` Grant Taylor
2008-04-21 6:55 ` Javier Prieto Martínez
2008-04-22 1:30 ` Grant Taylor
2008-04-22 6:15 ` Javier Prieto Martínez
2008-04-22 14:29 ` Grant Taylor
2008-04-22 15:10 ` Javier Prieto Martínez
2008-04-22 19:24 ` Grant Taylor
2008-04-23 15:24 ` Jan Engelhardt
2008-04-23 17:16 ` Grant Taylor [this message]
2008-04-23 18:48 ` Jan Engelhardt
2008-04-23 18:57 ` Grant Taylor
2008-04-24 6:15 ` Javier Prieto Martínez
2008-04-18 14:34 ` Grant Taylor
2008-04-18 14:44 ` Grant Taylor
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=480F6EEE.9010201@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