"AcCeSsDeNiEd" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have 2 gateways/systems setup:
>
> Gateway A:
> eth0= 10.10.1.1
> eth1= 10.30.1.15
>
> Gateway B:
> eth0=10.30.1.1
>
> I have set up a static route that says if the 10.10.1.0 network wants to
reach the
> 10.30.1.0 network, use the 10.30.1.1 gateway. This works, both the
network's users
> (10.10.1<->10.30.1) can reach each other.
>
> However, this breaks Gateway A's local access to the 10.30.1.0 network.
> I suppose it's because locally on A, the packets get routed via 10.30.1.1.
> When it reaches B, B detects that it's a local IP (10.30.1.15) and sends
it back directly to
> 10.30.1.15
> (as opposed to 10.30.1.1).
>
> I hope I've explained properly.
>
> Any ideas/help?
>
> How can I tell A not to use 10.30.1.1 if wants to locally access
10.30.1.0?
>
> Thanks.
>
>
>
> To e-mail, remove the obvious
I'm not sure exactly how you have things setup, but it sounds like to me
that you don't even really need gateway B. Your Gateway A is on both
networks simultaneously, therefore routing between the two can be handled on
that single machine. I'm thinking you should try removing the static route
you setup that links the two and put in a static route that tells any
traffic bound for the 10.30.1.0 network to use 10.30.1.15, which is the IP
of Gateway A's NIC on that network. Gateway by itself should be able to
talk on both network without any fancy routing because it has NICs on both.
But for other PC's on the 10.10.1.0 network, Gateway A needs to tell
connections to 10.30.1.x coming from them to go out through its 10.30.1.15
NIC.
|