IPv6 IP Alias prevents Track Interface from working with DHCPv6 and RA

JKnott

Take a look at your router advertisements. Mine are further up. Also, I'm using SLAAC, not DHCPv6 on my LAN.

dg6464

@JKnott I'm using both with the drop down being "Assisted".

Not sure what you would like me to show for in my RA's... I have both my ULA and GUA prefix's listed there, what do you mean by yours are further up? Do you mean your ULA is on top of the RA's prefix lists?

DHCPv6 I just have on for devices that support it... as I dole out a domain name on that (I don't have a search list defined in the RA function for SLAAC).

Best Regards,

dg6464

chewie198

I can confirm that the latest pull request committed to the 2.5 development branch seems to resolve the problem that I was experiencing. Really appreciate the fix guys! Any chance we could get a dropdown to specify which prefix to use for the DHCPv6 server? In my network I use DHCPv6 to assign ULA addresses but the servers receive their global address via RA's. Beggars can't be choosers and all that, but I appreciate the feature addition either way

chewie198

It looks like I was premature in drawing my conclusion - the assigned prefix still appears to reset to the VIP range after a reboot of the firewall. @viktor_g and I have been relaying information in the Redmine ticket at https://redmine.pfsense.org/issues/5999, but it would be helpful to know whether anyone else is still experiencing this issue on the latest development snapshot. Anyone with a IPv6 PD subnet, or who has experienced this issue previously, willing to add a VIP and test this? All that is needed to reproduce, if you already have a PD subnet, is to add a ULA VIP to the interface and reboot the firewall.

JKnott

@chewie198

I'll give it a try when 2.5 comes out.

viktor_g

@chewie198 Could you check the PM, please?

dg6464

Apologies guys... I absolutely would, but moved service providers and no longer have native IPv6 capabilities with Bell like I did with Rogers. So I've fully disabled IPv6.

JKnott

@jknott

I just tried it and it's still necessary to specify the GUA prefix, when a ULA prefix is added. However, I'm using SLAAC, not DHCPv6 on my LAN.

chewie198

I've been running 2.5 since it came out and it does indeed seem like this has finally been resolved. @JKnott I had a similar issue occur immediately after upgrading the firewall, but after rebooting I haven't seen it happen again. Both my SLAAC and DHCPv6 devices have retained their GUA and ULA addresses for several weeks now, even after multiple firewall reboots.

JKnott

@chewie198

I just tried it again and it seems to be OK. Time will tell.

tnx

apearson

Works here as well