>>>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. > >Thanks for your help here. Whilst it differs from what other people >have suggested, what you've said seems to make good sense. Some >examples would really help me out. For instance, is it just DNAT I'm >doing in 1 and 4 or do I also need to use SNAT? I take it that 3. is >optional and only required if I require extra filtering/firewalling. > >How does this look? > >iptables -t nat -A PREROUTING -d 192.168.152.2 -o eth1 DNAT --to 193.168.152.2 > >ip route add 193.168.152.0/24 dev eth1 > >iptables -t nat -A PREROUTING -d 172.26.158.2 -o eth0 DNAT --to 193.168.152.2 > >ip route add 192.168.152.0/24 dev eth2 > >iptables -t nat -A PREROUTING -d 172.26.158.130 -o eth0 DNAT --to 192.168.152.2 > >ip route add default dev eth0 via 192.168.152.1 > Ah. I didnt read your first query carefully enough. Are you really wanting to map each 192 subnet into a unique bit of 172 address space so that you dont have to make any config changes to machines in 172 in order for them to access 192-space? I dont know if this is possible. It implies that eth0 would have to respond to the whole bunch of 172 ip addresses which you had reserved for your 192 nets, and would also have to know that those packets were not intended for *it*, but had to be forwarded on somewhere else. How would this be achieved? It sounds like some sort of NAT'ing bridge, which is beyond my experience. Maybe static entries in eth0's arp tables... What I was suggesting is something that would map one of your 192 subnets into a different bit of 192 space (so that the two 192 nets were distinguishable), but that machines in 172 would still reference the 192 machines by their 192 addresses (a different set in the case of eth2, say). This would require config'ing a static route in every machine in 172 which wanted to talk to the 192 boxes. Before carrying on, is this acceptable? Cheers, Terry.
