On 7/5/11 4:12 PM, Arun wrote:
Just add default route at your node 10.225.162.28, and make the default
GW for this route as 192.168.28.0/24 or the connected interface. Your
SRV node should pass it to its default gw 192.168.28.1 which should take
care of forwarding it to the destination RN. If your SRV node could NOT
forward the ping reply then add a specific route there like - "pkt comes
from 10.225.162.0 then forward it to 192.168.28.1.
Thanks.
Hi:
There can only be one default gateway, anything else doesn't make sense.
I did try adding a specific route on SRV for RN such that pings arriving
on 10.225.162.28 would be responded correctly. But, then RN can no
longer reach 192.168.28.196. No surprise there really.
So, why do we have this setup? Well, some services like ssh that is used
for administration must arrive on 192.168.28/24 where as the commercial
service has a dedicated network on 10.225.162/24 and to ensure
availability and bandwidth we cannot accept to have ssh coming in on
that network.
I should add that this is a Red Hat Linux, I ask here since the FBSD
implementation of the tcp/ip stack is considered the reference
implementation.
So the question is which behaviour is correct, recommended or accepted?
Stripping the link layer and reply according to the network layer, or
keeping the link layer?
Thanks, Erik
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"
