I think you'll need to do policy routing to ensure that packets received on one IP address get returned via the same IP address. Here's some docs on setting it up:
http://lartc.org/howto/lartc.rpdb.multiple-links.html http://linux-ip.net/html/tools-ip-route.html We've used this to solve the case of having two separate, but overlapping, private networks (don't ask). Skylar On Wed, Jul 22, 2015 at 10:43 AM, Ski Kacoroski <[email protected]> wrote: > Hi, > > I hvae a linux webserver that has a primary IP (no web config on it) and > 10 other IPs assigned to it (one for each web site). It also mounts a > backup directory from an EMC VNX via NFS. The EMC exports has the name of > the server in it (machine.nsd.org). It worked fine until we failed over > to our DR site. > > What happened after the failover is that the NFS started using one of the > webserver IPs. I figured this out by doing a tcpdump on the webserver. > The fix was to add the website name to the export list and it works fine. > > My question is why would it pick a different IP? Is there something I can > do to force NFS to always use the same IP instead of randomly picking one > from the 11 IPs that are assigned to the machine? > > Thanks, > > ski > > -- > "When we try to pick out anything by itself, we find it > connected to the entire universe" John Muir > > Chris "Ski" Kacoroski, [email protected], 206-501-9803 > or ski98033 on most IM services > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ >
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
