Date: Thu, 26 Sep 2019 18:09:17 +0530 From: Mihir Luthra <luthramihir708@gmail.com> To: Hiroki Sato <hrs@allbsd.org> Cc: freebsd-net <freebsd-net@freebsd.org>, hrs@freebsd.org Subject: Re: rpc.statd already ipv6 clean? Message-ID: <CAEa=dYCv=b7JxW4Ajc%2BgBNaC7z_SEiUhwyPz5vxjUNdkzvVmHQ@mail.gmail.com> In-Reply-To: <20190926.054603.242590258844901628.hrs@allbsd.org> References: <CAEa=dYAEKph9qOcegtEB%2BFXCMqdQpmbrbzOA548cvjk0L3KK4A@mail.gmail.com> <20190925.085753.1800759957383540219.hrs@allbsd.org> <CAEa=dYAnwxPjwZozU6K3GE7-Cjwx0rSemVd0ihrbUAUQw3jOLg@mail.gmail.com> <20190926.054603.242590258844901628.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I think you should learn TI-RPC API first. The nettype specifies a > class of transport protocol, not address family. > > Thanks, I did some more research on TI-RPC today. In `statd.c` what I see is in `create_service()`/`complete_service()`, transport info is being fetched through getnetconfig(), which makes it listen on all transports. I guess its clean in `statd.c` but same can also be done in `procs.c`/`file.c`. Maybe trying all transports until it finds one which is connectionless? Apologies if I got something wrong, new to this topic. Also, while looking at the code, I think it always assumes ipv4 is always present. Like `127.0.0.1` is added to host list always. On ipv6 only machine this may fail. Kind Regards, Mihir
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEa=dYCv=b7JxW4Ajc%2BgBNaC7z_SEiUhwyPz5vxjUNdkzvVmHQ>