From owner-freebsd-net@FreeBSD.ORG Sun Sep 2 21:50:52 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50919106564A for ; Sun, 2 Sep 2012 21:50:52 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from rush.bluerosetech.com (rush.bluerosetech.com [IPv6:2607:fc50:1000:9b00::25]) by mx1.freebsd.org (Postfix) with ESMTP id 20A5A8FC1C for ; Sun, 2 Sep 2012 21:50:52 +0000 (UTC) Received: from vivi.cat.pdx.edu (vivi.cat.pdx.edu [IPv6:2610:10:20:214::6]) by rush.bluerosetech.com (Postfix) with ESMTPSA id 18DF01142E for ; Sun, 2 Sep 2012 14:50:45 -0700 (PDT) Received: from [127.0.0.1] (c-76-27-220-79.hsd1.wa.comcast.net [76.27.220.79]) by vivi.cat.pdx.edu (Postfix) with ESMTPSA id 6909F24CD6 for ; Sun, 2 Sep 2012 14:50:43 -0700 (PDT) Message-ID: <5043D4B3.7010009@bluerosetech.com> Date: Sun, 02 Sep 2012 14:50:43 -0700 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.6esrpre) Gecko/20120713 Thunderbird/10.0.6 MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: How to do both DHCPv4 and DHCPv6 at the same time? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2012 21:50:52 -0000 Comcast does IPv6 using DHCPv6 and DHCPv6-PD. At least in 8.3-p3, the in-base dhclient doesn't do DHCPv6. I installed the net/isc-dhcp42-client port and am successfully using as a workalike drop-in replacement with the following in /etc/rc.conf: dhclient_flags="-lf /var/db/dhclient.leases.${ifn} -pf /var/run/${name}.${ifn}.pid -cf /usr/local/etc/dhclient.conf" dhclient_program="/usr/local/sbin/dhclient" According to the port's dhclient man page, I need add "-6" to dhclient_flags to make dhclient do DHCPv6. The problem is the network scripts in the base don't differentiate between DHCPv6 and DHCPv4, so adding that would break my network config (or at least prevent the system from getting an IPv4 address). Writing my own RC script for this is completely the wrong solution, so I'm sure I'm overlooking something. What am I missing?