On Sat, Jul 15, 2017 at 2:17 AM, Stuart Henderson <s...@spacehopper.org> wrote:
> On 2017-07-14, David Higgs <hig...@gmail.com> wrote: > > Comcast provides me with IPv6 via DHCPv6, which I've finally tried to > > configure on my OpenBSD 6.1 router. I am having difficulty maintaining > my > > IPv6 public IP address when using the wide-dhcpv6 package when in client > > mode. > > Switch to dhcpcd, which has a workaround for the vltime/pltime bug, or > use a snapshot, where it has been fixed. Or both. > > > - Is there a security/quality preference between wide-dhcpv6 and > dhcpcd? I > > notice that dhcp6c doesn't appear to support a dedicated chroot/user... > > dhcpcd is more modern and actively maintained. I'm not aware of any > client that does DHCPv6-PD that has privsep though. > > > - Does the project have any near-term plans to write a DHCPv6 daemon to > > live in base? > > I'm not aware of any. > > After a good amount of trial and error, it appears that Comcast will only dole out a single /128 via DHCPv6. Annoying but easy enough to work around with pf(4) nat-to and some static RFC 4193 prefixes. No apparent problems when running dhcpcd. FWIW, I did notice that sometimes my upstream link does not have the accept_rtadv flag set (as per ndp -i $INTF), but I haven't investigated this in depth. Thanks! --david
