That's interesting. No it isn't. In Dual Stack IPv6 connectivity never may rely on any IPv4 configuration parameter, ever. Fritzboxes have been acting strange with IPv6 for some time now. There is a quite recent (german) article linking to some issues by heise in c't 10/2016. Your issue isn't in there. This need to be examined in more detail. Try Wireshark or something and make more sense of the Neighbor Discovery packages (ICMP6).

https://redmine.pfsense.org/issues/6667 Instead of manually copying the file to /conf, you could install the cron package and back up the duid file every hour.  Because the file shouldn't change once created, and performing all kinds of extra writes to a CF or SSD is A Bad Thing, I use "-n" (no clobber) to make the backup. I have the following cron job: *  */1  *  *  *  root  /bin/cp -n /var/db/dhcp6c_duid /conf/dhcp6c_duid …and the shellcmd setting (copying from /conf/ instead of from /conf/dhcp/) above. (This should be improved to use "cp -f" if the timestamp of the copy in /var is newer than the backup.  In most linux distros, the "-u" parameter to cp would take care of that, but I don't see an equivalent in freebsd cp.) The whole idea is that a user could still manually delete the duid file if they needed to "fix" a broken duid (or get a new lease or something.)  If that happens, you'd want a new backup taken.  If DUID changes, update the backup.  Else, don't write to it. Of course, it'd be better still if backing up the duid file was incorporated into the scripts that backup (and restore) the dhcp leases automatically.

Thanks for the reply!

When I had that problem, briefly disconnecting the Ethernet cable was enough to cause a change.  It is standardized in DHCPv6-PD.  I supposed it may have a lease time, as DHCP addresses do.  After all, with barely 4000 /48s for each person on earth, we'd soon run out, if unused prefixes weren't reclaimed.  ;)

I run same 2.3.1-p5 amd64 and HE tunnel is stable as you could ever want.  Only times there are issues with it is when there are issues with my actual ISP connection. What tunnel endpoint are you using?  I use the one in Chicago, they have many many other locations.  They have a status page you can look to find the status of any of the tunnels locations. https://tunnelbroker.net/status.php Lets see your tunnel quality vs your isp quality.. [image: tunnel.jpg] [image: tunnel.jpg_thumb] [image: wan.jpg] [image: wan.jpg_thumb]

It would be nice if pfSense would support filtering based on MAC address, as some other firewalls do.

Turned out I had some typos in my dhcpv6 config after all the testing I'd done. Now starting dhcp6c manually works and ipv6 is up.

Except that that IPv6 address isn't really an IPv6 address… it's intended to be a way to access or reference an IPv4 host using an IPv6 address (also acceptable would be ::ffff:c0a8:201, if you want the real IPv6 look). A little more depth from a post in the Hurricane Electric forums... [It] is an "IPv4-Mapped IPv6 Address".  It's another transition thing that is used to represent v4 addresses in a v6.  It's mainly used as an OS API thing to allow applications to do IPv4 via the IPv6 networking APIs (sockets, etc).  That way, when you write an application and want to do both IPv6 and IPv4, you can use the same calls and structures, etc, for both IPv6 and IPv4.  Without such a mechanism, an application such as a web server would have to reserve a socket and do a separate listen on both an IPv4 and IPv6 socket, manage them separately, etc.  With this mechanism, the application need only do a listen using the IPv6 API, and it can accept both IPv4 and IPv6 connections through the same API.  Doing a TCP connect also works similarly.  If the destination address in the sockaddr structure is a mapped address, it'll go through the IPv4 stack, otherwise it'll use the IPv6 stack. Reference: https://forums.he.net/index.php?topic=635.msg2820#msg2820 So I would expect that using that IPv6 address would create a conflict, if not cause other issues. Additional reference: RFC 4291, Section 2.5.5.2 - IPv6 Addressing Architecture, IPv4-Mapped IPv6 Address

Thanks Chris. I saw you also coded other values to bumb up so that is that and it works fantastic now. I wish you good luck in your future career mate!

On networks with end user devices, yes, it would be a bad practice to use anything other than a /64.

@sheptard: I just updated to 2.3.2-DEVELOPMENT which included a update to dhcp6 and seems things are working better. my internal clients have valid ipv6 addresses and ipv6 dns works just fine. However I can't get any ipv6 traffic to leave my lan, but ipv6 connectivity works just fine on the router. I just installed the DEV version and for me there was no difference. I configured the prefix and other settings as before. I had to manually start dhcp6c as above. After that, everything was the same as it was with the other version. The dhcp6 gateway status is "pending", but ipv6 is working.

Jimp, Many thanks for your reply. The static IP address client (::210) is in the NDP Table but I am not sure if the client is talking to pfSense. Please see the attached NDP Table. Thanks again for your reply! [image: Untitled.jpg] [image: Untitled.jpg_thumb]

Ok … almost that way .. I got a /64 and a /48 from HuricaneElektric The /64 is no between the first PFSense and the CARP-Cluster The /48 is routed to the vIP of the CARP-Clusters WAN-vIP the first /64 out of the /48 is for the LAN now. RA is set to unmanaged for LAN-IPv6 Some stuff with default-GW and firewall arround ... Now it works really fine!

Worked it out, just needed to get my upstream provider to add static routes for those internal LANs to his upstream router. 2222:fc00:0:123::10:21c/64 via 2222:fc00:0:21::10:21c 2222:fc00:0:127::10:21c/64 via 2222:fc00:0:21::10:21c

LOL I was actually just reading through that same post. Seems pretty interesting. I have the old version of the Netgear switch theyre talking about. It has since died. Wonder if I can RMA it! :P Otherwise, I need to pick up a new switch anyway.

ipv6 must be in lowercase https://tools.ietf.org/html/rfc5952#section-4.3 https://forum.pfsense.org/index.php?topic=114173.msg634799#msg634799

Basically - yes. I assign a /64 for each VPN instance, each "LAN" etc etc. As to what you set as the range, it depends completely on what you were assigned by HE. Also, you have to set up the firewall to use IPV6 at all and you have to secure it.