IPv6 no longer working after updating to 2.4.4

As the title says, my IPv6 connectivity has stopped since updating to 2.4.4. What's strange is pfSense is able to obtain an address on both the WAN and LAN side, but it's not assigning an address to any clients.

If you take a look at this below, you can see what I mean:

I even went as far as disabling IPv6 from my ISP and using a Hurricane Electric tunnel, though I'm not really sure what I expected as it seems to be an issue with the DHCP server on pfSense.

Any way anyone can help troubleshoot this? I looked at the logs for DHCP but most of it seems to be for v4 and very little to do with v6.

Does IPv6 connectivity work from the firewall, but not client behind the firewall?

What's strange is when I was playing around with it the other day I was able to ping6 hosts from the firewall itself. Today that doesn't seem to be the case, despite having an address assigned to it.

Do you have an IPv6 gateway configured as default for IPv6 (System > Routing), and is it showing under Diagnostics > Routes?

Yes, and yes..

Do clients on the LAN obtain an IPv6 address?

No, which seems to be the main problem. What's strange is after my last post a few minutes ago under Interaces -> LAN, I turned IPv6 connectivity to none and then back to Track Interface and for about 30 seconds I was assigned an address on my computer, but it's now gone.

If you filter that log for anything from dhcp6c it should show you quite a bit in debug mode. You'll need to increase the amount of lines it shows quite a bit, I'd set it up to 250 at least to be sure.

If that is the case then it stands to reason that it's a problem with your configuration and not 2.4.4 in general. It could still be a bug, but one triggered only by your specific combination of environment+settings.

Isolate your interface settings that are different vs a stock install and put them back one by one until it breaks.

@xero9 i had similar problems changing from 2.4.3_1 to 2.4.4. the way to migrate is the one i always use: backup the configuration, clean installation and then restore the configuration. i found different problems in three different installations in three different environments, one in bare metal and two in virtual environments based on xen.

i reported it as a bug and i was asked to report it in this forum. it was also mentioned that it was environment + settings, that is nothing.

i have reconstructed the configuration step by step manually, parameter by parameter until arriving at an exact configuration to those i had in 2.4.3_1 and everything works again.

my conclusion is that something is broken in the backup and restore mechanism by xml file. that method is breaking random configurations in different environments.

i have the configurations working for several years in different environments, it is the first time something like this happens when changing the version using the xml file.

and it is the first time that i have to reconstruct by hand all the configurations, a terrible job.

i repeat that there are no differences between the configurations, i have checked it.

i insist that it is an error in the backup - restore mechanism using the xml file.

I would test a theory but everything is working as it should now, so I don’t want to mess with it, but today I “broke” my IPv6 again, but it wasn’t really my fault. The DHCPv6 service wasn’t handing out ips to all of my systems and static addressing wasn’t working so I was looking deeper in to it and I think previously I had set RA to Managed and because I had an incorrect DUID (there was a space instead of a : in an entry) it was causing the DHCP server to not run.

I’m wondering now if I restore using the XML file if it would break entirely again or not but based on your experience I’ll just stick with things the way they are.

Confirmed. I also had issues with my firewall after upgrading to 2.4.4.
After the upgrade the firewall and restoring my config the firewall gui would freeze after a while, rendering internet connectivity unavailable. I also needed to start from scratch to overcome the problems. I was thinking that the problems could be related to the gateway monitoring feature but wasn't able to confirm that.