getting a callback ip address for nfsv4 client

[Rick Macklem]

On Sun, 12 Apr 2009, Tim Kientzle wrote:

>
> In general, the client doesn't know what address to use
> in this case.  In fact, I've been a little confused by this
> conversation all along.  It sounds like the client is
> looking up it's own address in order to tell the server
> how to contact the client?  Why?  The server already
> knows the source IP address on the incoming packets
> from the client; that's much more robust than anything
> the client could look up.
>
No misunderstanding, except that the nfsv4 designers put the callback
address in the SetClientID request, so a client must explicitly specify
it. (I can only guess that they wanted the client to be able to specify
an alternate routing or maybe some vendors wanted to be able to put the
callback server on a separate machine/interface or ???)

To me, it would have been simpler to just put callback RPCs in the same
TCP stream as the client->server RPCs, but they didn't do that
either.

For nfsv4.1, there is a large glob of stuff called Sessions, 
which handles the transport layer and the connections for callbacks are
created by the client, which avoids the problem.

rick