From owner-freebsd-net@FreeBSD.ORG Sat Nov 1 15:23:18 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 15FF9C38 for ; Sat, 1 Nov 2014 15:23:18 +0000 (UTC) Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E204C1B5 for ; Sat, 1 Nov 2014 15:23:17 +0000 (UTC) Received: from [172.16.21.114] (cpe-098-122-037-156.sc.res.rr.com [98.122.37.156]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id B642D1D2E; Sat, 1 Nov 2014 11:21:30 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: Help with IPv6 router gateway config, Comcast, DHCP, dnsmasq From: Tom Pusateri In-Reply-To: <44D1EB57-CFB0-4E78-822C-29A9FEA85A66@me.com> Date: Sat, 1 Nov 2014 11:23:13 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <92438892-0AAC-4866-B7D9-BAA5B4AF9D9D@bangj.com> References: <44D1EB57-CFB0-4E78-822C-29A9FEA85A66@me.com> To: Rui Paulo X-Mailer: Apple Mail (2.1990.1) Cc: freebsd-net@freebsd.org, Chris Inacio X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 15:23:18 -0000 > On Nov 1, 2014, at 1:53 AM, Rui Paulo wrote: >=20 >> I find the man pages for dhcp6 pretty awful. The man pages describe = the >> options - but not being able to find what /64 is assigned to dhcp6c = other >> than running in debug mode seems crazy. >=20 > There's an alternative: dhclient from ports which includes DHCPv6 = support with prefix delegation. >=20 Chris' config error caused dhcp6c not to configure his downstream = interface. dhclient from ports will only work with the default prefix length = assigned by the provider. For all providers I have encountered, this is = /64 and a good choice. But if you want multiple /64's for multiple = interfaces, you have to request a larger prefix (/56 or /60 depending on = the policy of the provider). dhclient in ports will not let you do this. In Chris' case, he only has a single downstream interface (for now) and = so dhclient in ports would work for that. Tom=