[EMAIL PROTECTED] wrote:
> What we want is a packet coming in on eth2 to go out on eth2, and the same
for eth0.
> No matter what we tried the packets would come in on eth0 and try to go out
on eth2.
> As we have working on our Sun OS system.
> All we had to do there was turn of routing and ip forwarding.
daniel,
i've been wondering about why linux does this for years....
this doesn't have anything to do with routing, it's all about keeping track of what ip to
respond with.
just tested this on one of our multi-homed solaris 10 servers....
pings come in the non-default gateway interface, but
the response goes out the default gateway interface with
the non-default gateway interface ip address.
(summary: solaris keeps track of what interface the traffic came in on)
linux on the other has short term memory loss.
pings come in the non-default gateway interface, and
the response goes out the default gateway interface with
the default gateay interface ip address.
(summary: linux forgets what interface the traffic came in on)
hope that helps, or confuses the matter further. (:
steven tardy
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
