getting a callback ip address for nfsv4 client

Julian Elischer julian at elischer.org
Mon Mar 30 15:00:41 PDT 2009


Rick Macklem wrote:
> Well, since the last one turned out to be too easy, here's one I think
> is a little tougher...
> 
> The nfsv4 client needs to know an ip address for the machine, that can
> be used by servers to do callbacks on the client. I currently use the
> following, which I know isn't correct, but usually works ok:
> 
>     loopb = htonl(INADDR_LOOPBACK);
>     TAILQ_FOREACH(ia, &in_ifaddrhead, ia_link) {
>         if (IA_SIN(ia)->sin_addr.s_addr != loopb)
>             return (&(IA_SIN(ia)->sin_addr.s_addr));
>     }
>     return (NULL);

It's important that the address you use be an address that is in the
same 'security domain' as the client..

The best way to do that is to find an address that is on the interface
that will be used to send the packet out.

So you want to do a route lookup so use rtalloc or friends
(see route.c).

you want to use the same code that is used in ip_output  (or is it 
{udp/tcp}_output?) to fidn the local address when teh user specifies
INADDR_ANY.



> 
> Now, I could just make it a constant set by an rc script (argument to
> the callback daemon or a sysctl variable), but that's a bother for
> laptops using dhcp and similar. I think allowing an argument to the
> callback daemon is a good fallback, but it would be nice if it didn't
> normally have to be set for things to work ok.
> 
> Any ideas on how to do this?
> 
> Thanks in advance for any help, rick
> ps: Part of the reason that the above loop doesn't seem to be good
>     enough is that it requires "options VIMAGE_GLOBALS" to build.
> 
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"



More information about the freebsd-arch mailing list