Problem with re-directing from 2 sources to one server

Problem with re-directing from 2 sources to one server

[Richhmond Dyes]

I have a server that I have to reach from 2 different networks, the
Internet and another private network called downtown and I also have to
reach from the server both networks.  If I have one of the set of rules
running, it works fine, but if I put both set of rules on, it doesn't
work.  below are my set of rules.  Can anyone tell me a how this can be
done?

Here is the setup.
mynetwork 172.31.0.0/21
eth0 172.31.4.254 my network interface
eth1 192.168.14.1 interface to downtown which on that network's side
routes to 10.0.0.0/9
eth2 publicIP to the internet
publicnetwork.100 is the virtual address on eth2 called eth2:100
172.31.5.100 is the private ip address of the server I want reached
192.168.14.10 is the virtual ip address on eth1 called eth1:10


$IPT -t nat -A PREROUTING -d publicnetwork.100 -j DNAT --to-destination
172.31.5.100
$IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source
publicnetwork.100

$IPT -t nat -A PREROUTING -d 192.168.14.10  -j DNAT --to-destination
172.31.5.100
$IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source 
192.168.14.10

Then I forward all my 10.0.0.0/9  ip requests to  downtown

$IPT -A FORWARD -m state --state NEW -i eth0 -s 172.31.0.0/21  -o eth1
-d 10.0.0.0/8  -j ACCEPT

Then I forward ip requests from downtown for the server to it.
$IPT -A FORWARD -i eth1 -s 10.0.0.0/8 -d 172.31.5.100 -m state --state
NEW -j ACCEPT

Then I forward ip request from the internet to the server.
$IPT -A FORWARD -i eth2 -s 0/0 -o eth0 -d 172.31.5.100 -m state --state
NEW -m multiport -p tcp  --dport 22,80,1352 -j ACCEPT

Again when I have both set of rules on, it does not work.  any ideas?

Re: Problem with re-directing from 2 sources to one server

[former03 | Baltasar Cevc]

Hi,

On 08.12.2006, at 03:46, Richhmond Dyes wrote:

> I have a server that I have to reach from 2 different networks, the
> Internet and another private network called downtown and I also have to
> reach from the server both networks.  If I have one of the set of rules
> running, it works fine, but if I put both set of rules on, it doesn't
> work.  below are my set of rules.  Can anyone tell me a how this can be
> done?
>
> Here is the setup.
> mynetwork 172.31.0.0/21
> eth0 172.31.4.254 my network interface
> eth1 192.168.14.1 interface to downtown which on that network's side
> routes to 10.0.0.0/9
> eth2 publicIP to the internet
> publicnetwork.100 is the virtual address on eth2 called eth2:100
> 172.31.5.100 is the private ip address of the server I want reached
> 192.168.14.10 is the virtual ip address on eth1 called eth1:10
>
>
> $IPT -t nat -A PREROUTING -d publicnetwork.100 -j DNAT --to-destination
> 172.31.5.100
> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source
> publicnetwork.100
>
> $IPT -t nat -A PREROUTING -d 192.168.14.10  -j DNAT --to-destination
> 172.31.5.100
> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source 
> 192.168.14.10
>
> Then I forward all my 10.0.0.0/9  ip requests to  downtown
>
> $IPT -A FORWARD -m state --state NEW -i eth0 -s 172.31.0.0/21  -o eth1
> -d 10.0.0.0/8  -j ACCEPT
>
> Then I forward ip requests from downtown for the server to it.
> $IPT -A FORWARD -i eth1 -s 10.0.0.0/8 -d 172.31.5.100 -m state --state
> NEW -j ACCEPT
>
> Then I forward ip request from the internet to the server.
> $IPT -A FORWARD -i eth2 -s 0/0 -o eth0 -d 172.31.5.100 -m state --state
> NEW -m multiport -p tcp  --dport 22,80,1352 -j ACCEPT
>
> Again when I have both set of rules on, it does not work.  any ideas?
>
Can you make both of the networks able to communicate with the server
one at a time?
Please specify your networks (network address and bcast) or create a
little ASCII art on how everything's connected.

I assume that the router does not know where the initial request
came from when trying to descide where to send answers. Or in other 
words
I'd say it's probably a routing problem on the way back.

Baltasar


--
Baltasar Cevc

_____ former 03 gmbh
_____ infanteriestrafle 19 haus 6 eg
_____ D-80797 muenchen

_____ http://www.former03.de

Re: Problem with re-directing from 2 sources to one server

[Richmond Dyes]

former03 | Baltasar Cevc wrote:
> Hi,
>
> On 08.12.2006, at 03:46, Richhmond Dyes wrote:
>
>> I have a server that I have to reach from 2 different networks, the
>> Internet and another private network called downtown and I also have to
>> reach from the server both networks.  If I have one of the set of rules
>> running, it works fine, but if I put both set of rules on, it doesn't
>> work.  below are my set of rules.  Can anyone tell me a how this can be
>> done?
>>
>> Here is the setup.
>> mynetwork 172.31.0.0/21
>> eth0 172.31.4.254 my network interface
>> eth1 192.168.14.1 interface to downtown which on that network's side
>> routes to 10.0.0.0/9
>> eth2 publicIP to the internet
>> publicnetwork.100 is the virtual address on eth2 called eth2:100
>> 172.31.5.100 is the private ip address of the server I want reached
>> 192.168.14.10 is the virtual ip address on eth1 called eth1:10
>>
>>
>> $IPT -t nat -A PREROUTING -d publicnetwork.100 -j DNAT --to-destination
>> 172.31.5.100
>> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source
>> publicnetwork.100
>>
>> $IPT -t nat -A PREROUTING -d 192.168.14.10  -j DNAT --to-destination
>> 172.31.5.100
>> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source 
>> 192.168.14.10
>>
>> Then I forward all my 10.0.0.0/9  ip requests to  downtown
>>
>> $IPT -A FORWARD -m state --state NEW -i eth0 -s 172.31.0.0/21  -o eth1
>> -d 10.0.0.0/8  -j ACCEPT
>>
>> Then I forward ip requests from downtown for the server to it.
>> $IPT -A FORWARD -i eth1 -s 10.0.0.0/8 -d 172.31.5.100 -m state --state
>> NEW -j ACCEPT
>>
>> Then I forward ip request from the internet to the server.
>> $IPT -A FORWARD -i eth2 -s 0/0 -o eth0 -d 172.31.5.100 -m state --state
>> NEW -m multiport -p tcp  --dport 22,80,1352 -j ACCEPT
>>
>> Again when I have both set of rules on, it does not work.  any ideas?
>>
> Can you make both of the networks able to communicate with the server
> one at a time?
> Please specify your networks (network address and bcast) or create a
> little ASCII art on how everything's connected.
>
> I assume that the router does not know where the initial request
> came from when trying to descide where to send answers. Or in other words
> I'd say it's probably a routing problem on the way back.
>
> Baltasar
>
>
> -- 
> Baltasar Cevc
>
> _____ former 03 gmbh
> _____ infanteriestraße 19 haus 6 eg
> _____ D-80797 muenchen
>
> _____ http://www.former03.de
>
This is the setup. 172.31.0.0/21 172.31.7.255 is my internal network, I 
have a registered class C network  the internet. and the 2nd secure 
private network is 192.168.14.0/24 192.168.14.255. The 192.168.14.0/24 
network is then routed to the network I want to reach which is 
10.0.0.0/9.  That routing is handled by the owner of the 10.0.0.0 
network.  I have been routing between these 2 networks for 4 years.  
Sending printer and server data back and forth with no problems.   What 
seems to be happening is that if I route info from both networks to a 
server on my 172.31.0.0 network, it fails.  Example. I have a server 
with address 172.31.5.210 and I want to reach it from the internet and 
the network of 10.0.0.0/9, it won't work.  If I remove the rules for 
either incoming network, it connects with no problem.

Re: Problem with re-directing from 2 sources to one server

[Richmond Dyes]

Thanks by putting the output device in, it worked.

Taylor, Grant wrote:
> Richhmond Dyes wrote:
>> I have a server that I have to reach from 2 different networks, the
>> Internet and another private network called downtown and I also have to
>> reach from the server both networks.  If I have one of the set of rules
>> running, it works fine, but if I put both set of rules on, it doesn't
>> work.  below are my set of rules.  Can anyone tell me a how this can be
>> done?
>>
>> Here is the setup.
>> mynetwork 172.31.0.0/21
>> eth0 172.31.4.254 my network interface
>> eth1 192.168.14.1 interface to downtown which on that network's side
>> routes to 10.0.0.0/9
>> eth2 publicIP to the internet
>> publicnetwork.100 is the virtual address on eth2 called eth2:100
>> 172.31.5.100 is the private ip address of the server I want reached
>> 192.168.14.10 is the virtual ip address on eth1 called eth1:10
>
> What you are wanting to do is a simple enough request and should be 
> possible to do.
>
>> $IPT -t nat -A PREROUTING -d publicnetwork.100 -j DNAT --to-destination
>> 172.31.5.100
>> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source
>> publicnetwork.100
>>
>> $IPT -t nat -A PREROUTING -d 192.168.14.10  -j DNAT --to-destination
>> 172.31.5.100
>> $IPT -t nat -A POSTROUTING -s 172.31.5.100 -j SNAT --to-source 
>> 192.168.14.10
>
> I believe your two POSTROUTING rules are the problem here.  Both rules 
> SNAT *ANY* traffic from your internal server.  I would alter the rules 
> so that they only applied on traffic as it left your two different 
> network interfaces.
>
> I.e.
>
> $IPT -t nat -A POSTROUTING -o eth2 -s 172.31.5.100 -j SNAT --to-source 
> publicnetwork.100
>
> and
>
> $IPT -t nat -A POSTROUTING -o eth1 -s 172.31.5.100 -j SNAT --to-source 
> 192.168.14.10
>
>
>> Then I forward all my 10.0.0.0/9  ip requests to  downtown
>>
>> $IPT -A FORWARD -m state --state NEW -i eth0 -s 172.31.0.0/21  -o eth1
>> -d 10.0.0.0/8  -j ACCEPT
>>
>> Then I forward ip requests from downtown for the server to it.
>> $IPT -A FORWARD -i eth1 -s 10.0.0.0/8 -d 172.31.5.100 -m state --state
>> NEW -j ACCEPT
>>
>> Then I forward ip request from the internet to the server.
>> $IPT -A FORWARD -i eth2 -s 0/0 -o eth0 -d 172.31.5.100 -m state --state
>> NEW -m multiport -p tcp  --dport 22,80,1352 -j ACCEPT
>>
>> Again when I have both set of rules on, it does not work.  any ideas?
>
>
>
> Grant. . . .