Both test benches are identical: in each setup there is a box with IP 192.168.100.2 trying to read via NFS from 192.168.100.1. If you find another way to do that, I am your man, 'cause NFS re-exporting does not work with knfsd, and synchronising two machines all the time is not an option... Basically, the network interface where the packet originated has to somehow be remembered at the routing stage. I only see source address mangling to do that... Cheers, Hervé. > But if you giving eth0 IP addresses on two different subnets then you > could just plug everything that's on eth1 onto the same network as eth0. > > Just because it's Linux doesn't mean you can redefine IP routing and > expect it to work. > > > -----Original Message----- > From: netfilter-bounces@xxxxxxxxxxxxxxxxxxx > [mailto:netfilter-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hervé > Sent: Wednesday, February 02, 2005 8:41 AM > To: netfilter > Subject: Re: Two NICS with same IP and same client IP > >> Hervé wrote: >>> >>> In my case, the point is to help the routing by modifying the source >>> address. For example, you give eth0 two addresses: 192.168.100.1 and >>> 192.168.101.1, and eth1: 192.168.100.1 (yes, the same) and >>> 192.168.102.1. >> >> what's the point ??? >> > I have two identical test benches, in which one box has a fixed IP > address, hence I can't change the subnets. > What is more, this box always accesses the same IP address for the server. > > Yeah, not so easy, but hey, it's Linux, so it's possible! > > Cheers, > Hervé. > >
