Date: Sat, 1 Nov 2014 11:23:13 -0400 From: Tom Pusateri <pusateri@bangj.com> To: Rui Paulo <rpaulo@me.com> Cc: freebsd-net@freebsd.org, Chris Inacio <nacho319@gmail.com> Subject: Re: Help with IPv6 router gateway config, Comcast, DHCP, dnsmasq Message-ID: <92438892-0AAC-4866-B7D9-BAA5B4AF9D9D@bangj.com> In-Reply-To: <44D1EB57-CFB0-4E78-822C-29A9FEA85A66@me.com> References: <CAG_PEez92O0%2Ba-_OsQ%2BmUx_s58ttkPcvW05e8x3-CHWHv2kp1g@mail.gmail.com> <44D1EB57-CFB0-4E78-822C-29A9FEA85A66@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 1, 2014, at 1:53 AM, Rui Paulo <rpaulo@me.com> wrote: > >> 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. > > There's an alternative: dhclient from ports which includes DHCPv6 support with prefix delegation. > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?92438892-0AAC-4866-B7D9-BAA5B4AF9D9D>