Adding new IPv6 Track Interface does not get address
Just wanted to understand if this was expected behaviour or a bug. Scenario is a firewall getting an IPv6 address and /56 delegation via DHCP on WAN.
If I add enable IPv6 on a new interface via "Track Interface", that interface does not get an address until i manually release and renew the parent interface (or reboot). It does not get one during a standard DHCP address refresh cycle.
Is this expected?
@griffo I don't suppose by any chance you're on Aussie Broadband?
@vollans I am and I know what you are going to say, but I don't believe it's directly related. I'm actually testing the new DHCP6c client released to address that issue, and I have a WAN address and delegation fine.
It works perfectly for already configured IPv6 track interfaces when the WAN get's it's address, but if I create a new interface, the firewall is not delegating the subnet until the WAN address is fully renewed, not simply refreshed. I don't' believe this was the behaviour in 2.4 but want to understand if it's expected behaviour or not in 2.5
If you're on 2.4 you could answer the question for me - if you add a vlan and set IPv6 to "Track Interface" does pfsense give it an IPv6 address?
@griffo I've just tried, and the answer is a definite no.
JKnott last edited by
Have you used a different prefix ID for the new interface? Each interface requires a unique prefix ID. With a /56, your choices range from 0 - ff.
@jknott Yes, i match the prefix ID to the vlan number. As I said, it works if i restart or for a forced release / renew but otherwise it sits there for hours not gaining a delegated address range.
OK i think I found the "issue". The first interface I ipv6 enabled gave itself the entire /56 delegation, I had to change the prefix id and change it back to make it only grant itself a /64.