From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Duplicate IP scenario. Doable with iptables?
Date: Tue, 23 Nov 2004 14:50:52 -0500 [thread overview]
Message-ID: <20041123195052.GA2847@bender.817west.com> (raw)
In-Reply-To: <s1a330bd.064@mail2.hatsize.com>
On Tue, Nov 23, 2004 at 12:44:07PM -0700, Kevin Hilscher wrote:
> I have a somewhat odd scenario that requires the same pools of 192.168
> IPs to be bound to eth1 and eth2 on the same machine.
odd? no--it seems pretty much everyone has the same two problems these
days:
1) multiple, overlapping network address ranges
2) an inability to search through mailing list archives
> I need to NAT
> another pool of 10.x.x.x IPs bound to eth0 to these two pools of 192.168
> IPs. The setup is as follows:
>
> eth0:10.115.0.1/16 -> eth1:192.168.0.1/24
> eth0:10.115.0.2/16 -> eth1:192.168.0.2/24
> eth0:10.115.0.3/16 -> eth1:192.168.0.3/24
> eth0:10.115.0.4/16 -> eth1:192.168.0.4/24
> eth0:10.115.0.5/16 -> eth1:192.168.0.5/24
> eth0:10.115.0.6/16 -> eth1:192.168.0.6/24
>
> eth0:10.116.0.1/16 -> eth2:192.168.0.1/24
> eth0:10.116.0.2/16 -> eth2:192.168.0.2/24
> eth0:10.116.0.3/16 -> eth2:192.168.0.3/24
> eth0:10.116.0.4/16 -> eth2:192.168.0.4/24
> eth0:10.116.0.5/16 -> eth2:192.168.0.5/24
> eth0:10.116.0.6/16 -> eth2:192.168.0.6/24
>
> Suse 8.1 has no problem letting me bind the same IPs to eth1 and eth2,
> since eth1 and eth2 are not on the same physical network. However, I am
> having problems writing my NAT rules for this scenario.
>
> Is this scenario doable under iptables?
refer to:
http://marc.theaimsgroup.com/?l=netfilter&m=110027573811157&w=2
though Carry never reported back whether it worked or not--so YMMV, but
it sure saves some typing... :-D
-j
--
"I hope I didn't brain my damage."
--The Simpsons
next prev parent reply other threads:[~2004-11-23 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 19:44 Duplicate IP scenario. Doable with iptables? Kevin Hilscher
2004-11-23 19:50 ` Jason Opperisano [this message]
2004-11-27 4:04 ` John A. Sullivan III
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 19:28 Kevin Hilscher
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=20041123195052.GA2847@bender.817west.com \
--to=opie@817west.com \
--cc=netfilter@lists.netfilter.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