From owner-freebsd-net@freebsd.org Fri Sep 27 22:14:11 2019 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D70F412EF63 for ; Fri, 27 Sep 2019 22:14:11 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46g5g75JnQz4Rbs; Fri, 27 Sep 2019 22:14:11 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 7EC262D25; Fri, 27 Sep 2019 22:14:11 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 31FD18D4A154; Fri, 27 Sep 2019 22:14:08 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 340DAE707B9; Fri, 27 Sep 2019 22:14:08 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id n-jOG9F_cZBr; Fri, 27 Sep 2019 22:14:06 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:58ea:7c85:750a:d274]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 97B2DE707B8; Fri, 27 Sep 2019 22:14:05 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Rick Macklem" Cc: "Mihir Luthra" , "Hiroki Sato" , freebsd-net , hrs@freebsd.org Subject: Re: rpc.statd already ipv6 clean? Date: Fri, 27 Sep 2019 22:14:04 +0000 X-Mailer: MailMate (2.0BETAr6137) Message-ID: In-Reply-To: References: <20190925.085753.1800759957383540219.hrs@allbsd.org> <20190926.054603.242590258844901628.hrs@allbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Sep 2019 22:14:11 -0000 On 27 Sep 2019, at 21:52, Rick Macklem wrote: > Mihir Luthra wrote: >> Hi Rick, >> Rick wrote: >>> Although I'll admit it isn't something I am particularily fond of, >>> FreeBSD likes >>> utilities to build/work with only one of ipv4/ipv6. >>> To do this, "#ifdef INET" and "#ifdef INET6" is applied to the code >>> and the >>> Makefile is tweaked to define one or both of these. >>> (You can look at usr.sbin/nfsuserd for an example of this.) >> >> Yes I see. Although I was thinking, wouldn't it be better if we can >> take a flag via >getopts for ipv6/ipv4 if the machine supports both >> with macro guards around >too? > bz@ is the guy to ask. I've cc'd him. We are also exchanging private emails currently to sort out the confusion between “compiling out”, transport protocol, and addresses/protocol carried inside the (RPC) packets. This is three different things and all should be sorted. My work is mostly on the “compiling out” as I don’t want/need INET anymore mostly. Ensuring that the transport protocol works dual-stack is a good, easier part. For RPC and some others making sure to be able to not only transport IPv4 addresses in the payload protocol but also IPv6 addresses can be the hard part. I assume the latter is what you were referring to in the lines below? >> Btw, these protocols are old Sun Microsystems ones without any >> published >> RFC, so what is "correct" is difficult to determine. I suppose the >> Open >> Solaris sources is the best protocol specification. (Interop. testing >> with Linux >> would be nice, since Linux is the "defacto standard" now.) >> >> Good luck with it, rick >> >> Thanks for the tips, >> Mihir > rick