pfSense

Might also be related to this bug that was closed as a dupe: https://redmine.pfsense.org/issues/3290

Related: https://forums.whirlpool.net.au/archive/9004zpv9-6#r67799588

If i release/renew it never gets a v6 address again, but if I release, wait 20 seconds, renew it works immediately.

Sam McLeod wrote:

If the upstream ISP on the WAN link has an IPv6 failure / outage, PFSense does not release and renew the IPv6 lease.

I have the same issue as well with the same ISP.

see also #6691

Can't find if this is being tracked elsewhere now but it's still an issue.

Last night all PFSense users in the states of Victoria and Tasmania using AussieBB (a major ISP in Australia) that had planned maintenance at 4AM~ found that all IPv6 traffic was failing (e.g. ping6 google.com) - upon release and renew an IPv6 WAN address was not assigned by PFSense and they had to wait at least 20s between the release and renew on the WAN link for v6 to get an assignment.

• Is there any update on when this will be fixed?

Had another outage caused by PFSense not having the bugfixed dhcp6c client

(refs https://forums.whirlpool.net.au/thread/3mnkq4v9?p=726#r14510)

Looks like Opensense has a bugfix for the issue:

• Forum post: https://forum.opnsense.org/index.php?topic=20369.0
• Bugfix: https://github.com/opnsense/dhcp6c/issues/25

It's still open Sam K McLeod - Not fully fixed yet.
look towards the end of that issue (https://github.com/opnsense/dhcp6c/issues/25#issuecomment-742310113 specifically)

Looks like this will be a good one to pull in though, once it's wrapped up

Hi, considering the fact that the user only saw the patched version not fix the issue one time, would it be possible to review the upstream fixs implemented by the wide-dhcpv6 and look to implement the same in a dev release? I just don't see much priority given to this by Opnsense considering the reporter has not returned in over a month.

As someone affected by this bug on an almost daily basis, i'd be happy to provide whatever testing may assist.

Really keen to see some progress with this, it's impacting me on an almost weekly basis.

Please let me know if there is any further debugging or information I can provide to get this moving.

Same here - it's a very common issue for me as well, more than happy to get involved in helping nail this one if I can.

I updated this morning to the latest 2.5 release which had the dhcp6-20080615.2_4 client. I then rebooted this afternoon to install the latest build, and it failed to retrieve a DHCP6 address on reboot. Logs are below and seem a little confusing to me. This is the last mention of dhcp6c in the log, it's now 3 hours later and there's nothing showing it trying to get a new address.

(Logs in next post)

Apart from the initial failure to get an address on the WAN interface, i've not lost DHCPv6 on the WAN interface in 5 days, and it's normally a daily event. So it's likely the bug has been quashed and I experienced some other esoteric issue.

Thanks all for your efforts on this, great to see it in the 2.5.0 release today!