I guess this errormessage is also intressting: From systemlog: /rc.newwanipv6: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid re2_vlan1 re2_vlan2 re2_vlan3' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.3.3-P1 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Config file: /etc/dhcpd.conf Database file: /var/db/dhcpd.leases PID file: /var/run/dhcpd.pid Wrote 15 leases to leases file. Listening on BPF/re2_vlan3/00:0d:b9:33:95:42/192.168.3.0/24 Sending on BPF/re2_vlan3/00:0d:b9:33:95:42/192.168.3.0/24 Listening on BPF/re2_vlan2/00:0d:b9:33:95:42/192.168.2.0/24 Sending on BPF/re2_vlan2/00:0d:b9:33:95:42/192.168.2.0/24 Listening on BPF/re2_vlan1/00:0d:b9:33:95:42/192.168.1.0/24 Sending on BPF/re2_vlan1/00:0d:b9:33:95:42/192.168.1.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that t Command executed via ssh: [2.3.1-RELEASE][root@pfSense.localdomain]/root: /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid re2_vlan1 re2_vlan2 re2_vlan3 Internet Systems Consortium DHCP Server 4.3.3-P1 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Config file: /etc/dhcpd.conf Database file: /var/db/dhcpd.leases PID file: /var/run/dhcpd.pid Wrote 15 leases to leases file. Listening on BPF/re2_vlan3/00:0d:b9:33:95:42/192.168.3.0/24 Sending on  BPF/re2_vlan3/00:0d:b9:33:95:42/192.168.3.0/24 Listening on BPF/re2_vlan2/00:0d:b9:33:95:42/192.168.2.0/24 Sending on  BPF/re2_vlan2/00:0d:b9:33:95:42/192.168.2.0/24 Listening on BPF/re2_vlan1/00:0d:b9:33:95:42/192.168.1.0/24 Sending on  BPF/re2_vlan1/00:0d:b9:33:95:42/192.168.1.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf.  Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug.  These pages explain the proper process and the information we find helpful for debugging.. exiting.

For improved usability I would suggest noting that either in the description or error message that pops up.

Alright, that makes sense. Thanks for the help.

@hcoin: Re #2…. The firm but gentle encouragement I give along these lines has the same result the cashier at the grocery store gives when I explain "But I contribute to open source software, do I still have to pay?" Not an apt comparison at all. If you're paying someone for connectivity and they aren't routing you an IPv6 block for use internally, they aren't providing what you're paying for.

which field on which page?

this fixed it for me

I'm still having this issue with default settings Modem: SB6183 pfSense: 2.3.1 DHCPv6: Pending this fixed it for me: https://forum.pfsense.org/index.php?topic=87623.0

No idea about your issue but for something similar happening on my cable modem. The work-around until the glitch was fixed by the ISP with new modem firmware was to do a DHCP release/renew on the WAN interface in pfSense, much less aggravation than a reboot! http://your-pfsense-box/status_interfaces.php

Yeah, the PPPoE example is exactly the same situation that you have with a tunnel provider such as HE or SixXS. There has to be a separate tunnel network (sometimes called transfer network) with an address space that does not overlap with any of the other subnets used on your systems, otherwise you just can not route anything. On such tunnel network a /64 is used but only two addresses are ever actually used because link is point-to-point with just two peers.

2.3.1-RELEASE-p1 (i386)

@wiz561: @virgiliomi: I'll validate darkcrucible's statement as well… /56 for business, /60 for residential, both for cable internet service. The only Comcast residential offering that offers a smaller prefix is their Gigabit Pro 2Gbps active fiber service, where they give a /48. A touch off-topic, but are there 16 subnets in a /60, where each subnet contains 254 hosts? You're thinking IPv4. A /60 gives you 16x /64 IPv6 subnets. So 2^64 addresses in each.

Just thought that I'd mention a feature request asking for the DUID to be part of the config file, allowing it to be backed up/restored. https://redmine.pfsense.org/issues/3971 I think there's actually a field for it in the config file, but it's probably not used for anything at this point in time as it's blank. As for persistence across reboots, if you're running the nano version or have RAM disk storage enabled, those might be reasons why it's not persistent. Because it's definitely persistent for my pfSense box, and I'm not using RAM disk storage.

Thanks - that nailed it. Looks like though I'd tried the /48 and IP4, I clearly hadn't done both at the same time.

I was just about to post I dropped ipv6 on all but one subnet and started just requesting a /64.  I've gone about a week and it is still working.  I can't get /60 to work for more than 24hrs and I don't really have time to fuss with it right now. Hopefully there will be some solution to this before too long.

Unmanaged = SLAAC (StateLess Address Automatic Configuration) Managed = DHCPv6 Assisted = SLAAC preferred, DHCPv6 available If you set your RA to managed, but don't have a DHCPv6 server on your network (either from pfSense or another device on your network), then your devices won't get an IPv6 address. Also, it should be noted that Android devices only use SLAAC for IPv6 addresses, so you need to either be in Unmanaged or Assisted mode. And Windows will only get an IPv6 address via SLAAC; it won't use RDNSS provided DNS servers. DHCPv6 is required for DNS servers under Windows.

Seems that 6rd border relay need patched stf :(

Thank you for the reply.  Did not know that Assisted was using SLACC.  If I understand your comment, if I set the RA to Managed I will see the leased IPV6  devices and if a device does not support DHCPv6 it will not get an IPV6 address but would still get the IPV4 address from the DHCP v4 server.  is this correct? Thanks

It Maybe a case of my isp hasn't set up their stuff yet.