Date: Sat, 28 Sep 2019 00:36:07 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "Bjoern A. Zeeb" <bz@FreeBSD.org> Cc: Mihir Luthra <luthramihir708@gmail.com>, Hiroki Sato <hrs@allbsd.org>, freebsd-net <freebsd-net@freebsd.org>, "hrs@freebsd.org" <hrs@freebsd.org> Subject: Re: rpc.statd already ipv6 clean? Message-ID: <YTOPR0101MB11635147C66CD4959BF9A2B5DD800@YTOPR0101MB1163.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <F1F47B57-8491-47E8-A144-6CD75193FFAF@FreeBSD.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> <CAEa=dYCv=b7JxW4Ajc%2BgBNaC7z_SEiUhwyPz5vxjUNdkzvVmHQ@mail.gmail.com> <YTOPR0101MB1163687D58A2AEED58AECE21DD860@YTOPR0101MB1163.CANPRD01.PROD.OUTLOOK.COM> <CAEa=dYBoy7ZLDTFV62_dqFeMnc3jmATaq%2BkvYgYvOXzEYaLz=A@mail.gmail.com> <YTOPR0101MB11631BCBCA27985AC11FC104DD810@YTOPR0101MB1163.CANPRD01.PROD.OUTLOOK.COM>, <F1F47B57-8491-47E8-A144-6CD75193FFAF@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote:=0A= >On 27 Sep 2019, at 21:52, Rick Macklem wrote:=0A= >=0A= >> Mihir Luthra wrote:=0A= >>> Hi Rick,=0A= >>> Rick wrote:=0A= >>>> Although I'll admit it isn't something I am particularily fond of,=0A= >>>> FreeBSD likes=0A= >>>> utilities to build/work with only one of ipv4/ipv6.=0A= >>>> To do this, "#ifdef INET" and "#ifdef INET6" is applied to the code=0A= >>>> and the=0A= >>>> Makefile is tweaked to define one or both of these.=0A= >>>> (You can look at usr.sbin/nfsuserd for an example of this.)=0A= >>>=0A= >>> Yes I see. Although I was thinking, wouldn't it be better if we can=0A= >>> take a flag via >getopts for ipv6/ipv4 if the machine supports both=0A= >>> with macro guards around >too?=0A= >> bz@ is the guy to ask. I've cc'd him.=0A= >=0A= >We are also exchanging private emails currently to sort out the=0A= >confusion between =93compiling out=94, transport protocol, and=0A= >addresses/protocol carried inside the (RPC) packets.=0A= >=0A= >This is three different things and all should be sorted. My work is=0A= >mostly on the =93compiling out=94 as I don=92t want/need INET anymore=0A= >mostly. Ensuring that the transport protocol works dual-stack is a=0A= >good, easier part. For RPC and some others making sure to be able to=0A= >not only transport IPv4 addresses in the payload protocol but also IPv6=0A= >addresses can be the hard part. I assume the latter is what you were=0A= >referring to in the lines below?=0A= Yes. I do know there is some code in sys/rpc/rpc_generic.c (around=0A= line# 320-340) which shows how an IP6 address is coded in ascii to=0A= go on the wire. It basically uses inet_ntop() for the host address and=0A= then appends .N.N for the port#.=0A= However, I have no idea when/if rpc.statd uses that?=0A= =0A= >>> Btw, these protocols are old Sun Microsystems ones without any=0A= >>> published=0A= >>> RFC, so what is "correct" is difficult to determine. I suppose the=0A= >>> Open=0A= >>> Solaris sources is the best protocol specification. (Interop. testing= =0A= >>> with Linux=0A= >>> would be nice, since Linux is the "defacto standard" now.)=0A= >>>=0A= >>> Good luck with it, rick=0A= >>>=0A= >>> Thanks for the tips,=0A= >>> Mihir=0A= >> rick=0A= rick=0A= =0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB11635147C66CD4959BF9A2B5DD800>