On Fri, 2008-07-25 at 17:24 -0500, Steven Tardy wrote: > [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)
I actually wondered about this. I thought I had remembered there was some strange behavior from ICMP on Linux with this issue and it appears you might have confirmed that. But that shouldn't affect actual TCP and UDP connections since they have to be sourced from the IP that the request came in on, only ICMP right? Later, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
