Re: keep state "issue" / possible feature for the future?

chrisj@ucia.gov wrote:
> ...
> I issue the mount command to do an NFS mount of a remote filesystem.
>
> The remote server is running IPMP - each of the two NIC's
> on the remote server has a test IP address
> (deprecated, non-failover) and an active/usable IP address.
>
> My mount command specifies one of the two active IP addresses
>
> By snoop'ing my interface I see my machine send off a
> PORTMAP C GETPORT ... packet to
> the IP address I specified but (sometimes) the
> remote NFS server decides to reply using its alternate IP
> address which means that the packet is not seen as being
> part of the conversation I initiated and so is dropped.
>
> Any ideas that would allow me to continue to benefit from
> the elegance of the 'keep state' lines above?


This sounds like a bug in mountd in how it sends back UDP
based replies. It should be sending back replies with the
source address set to the original destination address, even
if it has to open a UDP socket for each IP address involved.

If the packet comes out of the same interface as the one it
went in then there might be an option you can use with the
route command to force all packets leaving that interface
to have its source address.

If the packet isn't coming out the same interface and it has
a source address for the "other" interface, I would be filing
a bug with Sun about this problem. I think there is a very
clear expectation on how it *should* work and that this
isn't happening. Include the bugid when you hear back from
Sun on it :)

Darren