From: "T. Horsnell (tsh)" <tsh@mrc-lmb.cam.ac.uk>
To: Fisher Alex <Alex.Fisher@uk.thalesgroup.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Is this possible?
Date: Fri, 23 Apr 2004 09:49:54 +0100 (BST) [thread overview]
Message-ID: <E1BGwNe-001zei-Lg@alf1.lmb.internal> (raw)
In-Reply-To: <4087ACE0.1020006@uk.thalesgroup.com> from Fisher Alex at "Apr 22, 2004 12:30:40 pm"
>Hi.
>
>I'll do my best to explain what I'm trying to acheive with a linux box
>and 3 NICS.
>
>I have two sets of systems. Each system has about 30 IP addresses
>spread across various bits of hardware. The two systems are identical
>(ie have the same 30 IP addresses). The addresses are all part of the
>class C subnet 192.168.0.*
>
>The IP addresses for each system are now set in stone and can't be
>changed. Furthermore, similar addresses are already in use on our network.
>
>I've been given a set of IP addresses I CAN use (172.26.158.*)
>
>A diagram might help here ...
>
> ----------- -----------------
> - System1 ---------|eth1 |
> ----------- | |
> | Linux Router |
> | eth0|------------Rest of the network
> | |
> ----------- | |
> - System2 ---------|eth2 |
> ----------- ------------------
>
>I also have an address I can use for eth0 which will make the router
>visible from machines on the rest of the network. This can be set as
>the default gateway for connections to the 172.26.158.* subnet.
>
>I would like PCs on the normal network to be able to connect with either
>system by addressing them with addresses off the 172.26.158 subnet.
>I'll assign 30 of these IPs to each system.
>
>For example. 172.26.158.10 might be mapped onto 192.168.0.2 on eth1
>whilst 172.26.158.50 might be mapped onto 192.168.0.2 on eth2
>
I've always regarded netfilter as a symmetric thing, so is it possible to
1. apply a set of S/DNAT rules specifically to
eth1 to map system1's 192 addresses to something else,
2. add a route to enable these new addresses to reach eth0
3. add appropriate rules to the FORWARD chain for those NAT'd addresses
if required
4. add a suitable set of S/DNAT rules specifically for eth0
to S/DNAT those new addresses to a unique subset of 172 addresses
5. Do the same stuff for eth2 but 1. would not be necessary
Cheers,
Terry.
next prev parent reply other threads:[~2004-04-23 8:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 11:30 Is this possible? Fisher Alex
2004-04-22 11:45 ` Kiran Kumar
2004-04-22 12:12 ` Antony Stone
2004-04-22 12:24 ` David Cannings
2004-04-22 12:44 ` Antony Stone
2004-04-23 8:49 ` T. Horsnell (tsh) [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-11 16:06 Michael Thompson
2005-02-13 12:18 ` Jose Maria Lopez Hernandez
2005-02-14 16:54 ` Andrew Schulman
2005-02-15 4:25 ` Alex Samad
2005-02-15 6:20 ` Michael Thompson
2004-04-27 9:57 T. Horsnell (tsh)
2004-04-26 10:03 Fisher Alex
2004-04-22 13:08 Fisher Alex
2004-04-22 12:36 Fisher Alex
2004-04-22 13:03 ` Antony Stone
2004-04-10 20:27 is this possible ? Syed Faisal Gillani
2004-04-10 20:54 ` Frederic de Villamil
2004-04-10 20:14 Admin
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=E1BGwNe-001zei-Lg@alf1.lmb.internal \
--to=tsh@mrc-lmb.cam.ac.uk \
--cc=Alex.Fisher@uk.thalesgroup.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