No IPv6 address on secondary WAN when using Track
-
So I just had a weird network issue, one of my cables was messed up and it prevented my WAN1 interface from getting DHCP4 from my ISP.
During this time, I noticed that the WAN1 interface DID get an IPv6 address - I hadn't been able to figure out before why it never got one, it was set to track WAN0. All my other IPv6 stuff seems fine.
I thought my ISP was to blame but then noticed a port with the wrong color, replaced the cable and DHCPv4 came back up on WAN1, but now I'm no longer getting the IPv6 address on WAN1.
When this happened, I set WAN1 to static and entered my IP info, it came online and was pingable, surprised me this wasn't nerfed by the ISP, but sure..
Of course a day or so later, my lease expires and that does nerf the static seems, not that any traffic was actually going out over the second port (though my stupid cable modem seems to have all of it's ports having the same MAC, they're all on their own VLANs)
When it was on static, the IPv6 address came up, I'm assuming with Track6 that it was able to get the address via WAN0.
Now that I fixed the cable and can get a DHCP4 address on WAN1 again though, the IPv6 address disappears. Not sure if this is an ISP quirk or if I'm missing something or what the deal is.
Thoughts..? .... wait, so, I just struggled a bit with my ISP's method of matching MAC to IPs (reboot modem mac lock kinda thing) and WAN0 wasn't coming up (probably because I tried a few MAC's and I only have two IPv4 addresses), rebooted modem again with WAN1 unplugged, WAN0 got DHCPv4 and now WAN1 shows both IPv4 and IPv6 addresses..
So that even more makes me think some kind of weird ISP quirk, perhaps I can't do DHCPv4 on WAN0 until after it's gotten an IPv6 address?
Will see if it behaves, I bet a reboot of pfSense right now would result in no more IPv6 address on WAN1.