@pablot: @kpa: @pablot: @JKnott: And the addresses being leased by SLAAC cant't be viewed on the DHCPv6 lease status, right? SLAAC has nothing to do with DHCPv6.  It gets the prefix via RADVD and provides the rest of the address, using either a MAC based or random 64 bit number.  If DHCPv6 is used, it's generally for providing things like server addresses.  However, it's not needed for DNS servers, as that can be provided by RDNSS. ok, and is there a way to check what IP addresses have been asigned by SLAAC? (like the way I can see the DHCP Leases) No such way. The RA daemon that advertises the route and the prefix does absolutely nothing else but those functions, selection of the address from the advertised prefix happens completely on the client (of course assisted with duplicate address detection but even that does not involve the RA daemon). ok, thanks for your help, I'm learning a lot!!!! :) Just one more… I cannot make my clients to ping a host on internet, the names resolve ok to the IPv6 addresses, but somehow I guess I do not have a gateway configured properly or something is "closed" at the pfSense box that blocks traffic. I had this issue when I first setup a 6rd tunnel. The fix for me was to disable gateway monitoring on the ipv6 gateway. It wasn't responding to pings so pfSense would treat it as being down.

If you want IPv6 until your ISP brings it online just get a HE tunnel, easy enough to setup - you can get a FREE /48 from them and there you go IPv6 no need for your isp to support it..

Hmm. I have an HE.NET tunnel and happily get DHCPv6 + /56 PD from Cox. I have been watching it for a while. They are honoring the DUID and not changing my prefix despite new modems and WAN MACs. My IPv4 address with them as changed at least three times since I started getting delegated this prefix.

@doktornotor: Have you tried the "Request only an IPv6 prefix" checkbox on WAN? Yes. There is my config : [image: 273700Capturedecran20170216a160943.png] @hda: You need more (say /60, /56 or /48) from your ISP, to be able to create more /64 LAN's. The first ISP in Belgium (Proximus) provide only one /64 per client :-(

I think this problem would be solved already if pfSense would not be restricted to CIDR. If a full subnet mask would be used, the top 64 bit could just be left 0 and the lower 64 bits (or at least the EUI-48 part could be 1 so that the IP+subnet mask would ignore the IPv6 prefix and only match the host-specific part. That's how firewall rules for dynamic IPv6 subnets can be easily implemented in ip6tables on Linux. I have idea however if the CIDR restriction is a pf issue and whether a full subnet mask can be easily implemented. Stefan

@kpa: You can use both the static address and the random address at the same time. If you need to open any inbound traffic you use the static address based on the MAC address and for all outgoing traffic that is going beyond the pfSense router the random address gets used automatically. Best of the both worlds. It's the way I think I'm gonna go, the only thing is that I can't set per-host rules and, more importantly, if the Traffic Graph section ever gets updated to support IPv6, I'll have no clue who is hogging my bandwidth, which is something I often rely upon (only 20 down/2 up).

@hda: If your /56 prefix does not change, then just don't do Track Interface. Assign Static LAN's prefix + subnet, suiting your LAN-host IP number. Use RA Managed (DHCP) or Router Only (Static) Unfortunately, it's dynamic.  It still seems buggy that pfSense would abandon its static routes after a network bounce though…

FYI regarding the Windows 10 Anniversary DHCPv6 renewal issue… according to the very last post in  this MS Technet discussion, the fix will be in the March 2017 monthly update.

The are the values of my test system (CentOS 7): [root@test01 ~]# sysctl -n net.core.wmem_max 212992 [root@test01 ~]# sysctl -n net.core.rmem_max 212992 [root@test01 ~]# sysctl -n net.ipv4.tcp_rmem 4096    87380  6291456 [root@test01 ~]# sysctl -n net.ipv4.tcp_wmem 4096    16384  4194304 I checked them on a few other of my CentOS systems and they all give the same results back. I did not make any kernel modifications via sysctl. The bandwidth issue is also visible when I do a curl -vv http://www.google.com from the PfSense Box

Thanks for the reply! I will do that in the future, but i was exactly curious on how to do this. I'm running pfsense 3.2.1 so I'm ipv6 ready.

Yes @marjohn pointed out the error of my ways Simply setting the IPv6 Prefix ID to 1 rather than 0 means I can split my /56 across another LAN

Hi, indeed it turned out to be client I was testing it, which was using dhcpcd. It works on other machines here, including Windows 10, GNU/Linux (both with Connman, NetworkManager). Since I was getting DHCPv6 in assisted mode I never suspected the client. Sorry for bothering everyone, but this turns out not to be an issue with pfsense after all. Kind regards, Bartosz

@luckman212: Yesterday I upgraded from 2.3.2 to 2.3.3 and from there up to 2.4.  My build is now 2.4.0.b.20170131.2311. Took a bit of time to get the cobwebs brushed away, remove some no-longer-needed Patches, etc but for the most part it was smooth and painless. So far so good, can't say if the dhcp6c issue is resolved yet but I'll know soon enough.  I saw some additional fixes were pushed today that haven't made it into snaps yet so that should get even better. Yes, the PR today has gone upstream, a strange one that, deleting the pid file before all processes are complete is not nice. :)

Use an HE.NET tunnel or get an ISP that does real IPv6.

Err, no i don't think you can start a dhcp server without a scope definition (valid poole range). It would defeat the purpose the server. Just enter a scope and define any static leases you desire outside of the defined pool. Then pick the assisted mode from the router advertisments page. Or maybe just forget about the dhcpv6 server and use static addresses on the clients.