IPv6 Track Interface not getting IPv6
-
This might also be relevant:
https://redmine.pfsense.org/issues/5999
I do have a Virtual IPv6 address on my WAN (because my Internet provider (Aussie Broadband) appears to have broken routing on the IPv6 address that it assigns to my router WAN via DHCPv6).
-
If it's the same as I experienced, I just manually added the ISP's prefix on the Router Advertisement. For some reason, pfSense stops automatically doing that, when you add a ULA prefix. However, I don't think that's your issue, as I don't recall you mentioning ULA before. I'm on a cable modem, so I can't help with PPPoE or IPoE.
-
Would really like to know how you've got IPv6 working with ABB.
@JKnott said
So, you must work on the LAN Down Under.
This was sent to me when the movie was still relatively recent.
-
Then there's the network song This LAN is Your LAN.
-
I've got 2.4.5-p1 running now. Today I switched the power off and back on. When the NBN device and the router restarted, all the IPv6 addresses were assigned properly. So that's a good improvement!
Other than the pfSense upgrade to 2.4.5-p1, I haven't changed any configuration. So maybe it's an improvement in 2.4.5-p1. But, I can't say for sure, because it's possible my Internet provider has made some configuration changes which improved it.
-
Make sure you have Do not allow PD/Address release on the WAN page set.
-
A comment on Whirlpool says:
A lot of routers use the WIDE-DHCPV6 package. And many of them have not incorporated the patch listed below. Without the patch, if the DHCP client gets a response that it wasn't expecting, it just gives up and stops trying.
โ Add patch 0018 to ignore advertise messages with none of requested data and missed status codes.
https://metadata.ftp-master.debian.org/changelogs/main/w/wide-dhcpv6/wide-dhcpv6_20080615-22_changelog
Patch: https://pastebin.com/a8wCHdHD
Does pfSense use the WIDE-DHCPV6 client? If so, does it incorporate this patch?
-
@JKnott said in IPv6 Track Interface not getting IPv6:
Make sure you have Do not allow PD/Address release on the WAN page set.
Is this generic advice, or advice tuned to my Internet provider (Aussie Broadband)?
If it's generic advice, why is Do not allow PD/Address release a user option?
-
its there, on the wan interface page
Its not tuned to aussies :)(but its not that important, since this is meaningful only when interfaces close gracefully.
On a power outage, line disconnection etc, you never get the time to send such things anyways)
And isp's often don't really care and always issue a new prefix upon reconnection -
I'm in Canada, so it's not an Aussie thing. As for why it's there, previously it wasn't and the prefix would frequently change. I suppose there is a reason why someone would want to always release the prefix, but I don't know what that is, other than perhaps changing ISP or something.