From owner-freebsd-net@freebsd.org Fri Jun 10 17:06:28 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD001AD9E05 for ; Fri, 10 Jun 2016 17:06:28 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id AA2CC2F68 for ; Fri, 10 Jun 2016 17:06:28 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: by mailman.ysv.freebsd.org (Postfix) id A98C4AD9E04; Fri, 10 Jun 2016 17:06:28 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A934BAD9E03 for ; Fri, 10 Jun 2016 17:06:28 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 921572F67 for ; Fri, 10 Jun 2016 17:06:28 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (unknown [IPv6:2601:1c2:1402:3a86:21c:c0ff:fe7f:96ee]) by echo.brtsvcs.net (Postfix) with ESMTPS id 31A585001C; Fri, 10 Jun 2016 17:06:21 +0000 (UTC) Received: from [IPv6:2601:1c2:1402:3a86:3c4b:52fa:e9fd:a39a] (unknown [IPv6:2601:1c2:1402:3a86:3c4b:52fa:e9fd:a39a]) by chombo.houseloki.net (Postfix) with ESMTPSA id 3B25718DF; Fri, 10 Jun 2016 10:06:20 -0700 (PDT) Subject: Re: DHCPv6 Support in FreeBSD Base To: David Bright , "net@FreeBSD.org" References: <6224EC83-3A81-4CE7-83C5-674628F38958@DELL.com> Reply-To: net@FreeBSD.org From: Mel Pilgrim Message-ID: <4a318c6c-ab03-e63c-979f-502bc2afb97e@bluerosetech.com> Date: Fri, 10 Jun 2016 10:06:24 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <6224EC83-3A81-4CE7-83C5-674628F38958@DELL.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 10 Jun 2016 17:06:28 -0000 On 2016-06-09 14:14, David Bright wrote: > Following up on a conversation I started today at BSDCan > 2016/DevSummit. > > I’d like to see support for DHCPv6 in the base system. I have made > modifications to network.subr and the rc.d init scripts to allow > configuring a network interface to use DHCPv6 in a manner very > similar to that currently used for DHCPv4. This works assuming that > you have a DHCPv6 client. For the purposes of my development I used > the ISC client from ports. > > These changes were based on 10.0-RELEASE and I am in the process of > adapting these changes to 11 so they can be pushed upstream. However, > they will be unusable (albeit harmless) in the base system without a > client. > > * Is there any barrier to updating the dhclient in base to the > current ISC dhclient for both DHCPv4 & DHCPv6? > > * Is there any barrier to replacing the current dhclient-script with > that that accompanies the ISC dhclient? The two scripts are quite > different and my DHCPv6 changes currently are based on the ISC > dhclient-script. > > As I’ve already done a fair amount of this work, I’d be happy to work > on getting it in shape for pushing to HEAD. I had several people > today at the devsummit indicate that they thought that would be a > good idea, but I thought it would be a good idea to ask ahead of time > if there were any known stumbling blocks to doing that. Could the WIDE client be used instead? Unlike the ISC client, it will configure downstream interfaces from PD prefixes without needing an external script. It also completely avoids the problem of trying to update the in-base dhclient.