Re: Multiple Network Gateways
Volkan YAZICI <yazicivo@ttmail.com> writes:
> On Fri, 15 Jul 2011 15:58:10 +0200, lee writes:
>> Volkan YAZICI <yazicivo@ttmail.com> writes:
>>
>>> ,===========. eth0 ,-------.
>>> || internet || <-----------------> | reyiz |
>>> `===========' 10.10.98.100 `-------'
>>> ^
>>> eth1 | 192.168.100.100
>>> |
>>> |
>>> |
>>> ,-------. eth3 |
>>> | pampa | <----------------------------+
>>> `-------^ 192.168.100.98
>>>
>>> [...]
>>
>> So there are a lot of hosts not shown on the scheme?
>
> Yep, and pampa will be the gateway to 192.168.100.0 network for reyiz.
Reyiz is already on the same network as pampa and therefore doesn't need
a gateway to reach this network.
>>> reyiz# route -n
>>> Kernel IP routing table
>>> Destination Gateway Genmask Flags Metric Ref Use Iface
>>> 10.10.98.96 0.0.0.0 255.255.255.240 U 0 0 0 eth0
>>> 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
>>> 0.0.0.0 192.168.100.98 0.0.0.0 UG 0 0 0 eth1
>>> 0.0.0.0 10.10.98.110 0.0.0.0 UG 0 0 0 eth0
>>>
>>> The problem here is that there exists two entries in the routing table
>>> for 0.0.0.0 network pointing to both eth0 and eth1. But I just want to
>>> have 192.168.100.0 network requests to be handled by eth1, the rest
>>> should be redirected to eth0.
>>
>> There are no 0.0.0.0 networks, only 192.168.100.0 and 10.10.98.96. Try
>> 'route' instead of 'route -n' ...
>
> I intentionally used -n, I know there are no 0.0.0.0 networks. But it
> still doesn't answer to my question that how can I make just
> 192.168.100.0 requests get routed through 192.168.100.98 gw machine.
It seems to me as if the routing you have does exactly what you want
unless you really want to /force/ *all* traffic to the network
192.168.100.0 to go through 192.168.100.98 instead of going directly to
this network. Or do you actually see any traffic to the 10.10.98.96
network being routed through 192.168.100.98?
--
html messages are obsolete
Reply to: