My experience after updating to 24.7.4

[Native2184]

Hi everybody. A long time happy OPNsense user here.
Updated to 24.7.4 and ran into some stuff I'd like to share here to help improving development.

My setup:
-    Dual WAN (Cable and fibre (PPPOE)) with both IPv4 and IPv6 enabled
-    Several client connections to my VPN provider (OVPN because of their native IPv6 support).
   All of the connections are bound to Localhost so that in case my primary connection (FTTH) fails, it'll still establish the connection through the WAN_CABLE interface.


My FTTH provider (KPN) does not give a WAN address, only a /48 prefix.
Before the "Optional prefix ID" option was available, I used an alias to assign an IPv6 address to the WAN_FTTH interface (solved some issues with the firewall not having an IPv6 on that interface).

Recently I switched to the "Optional prefix ID" and deleted the alias without any issues until this update.
After the update was installed all of my VPN connections stopped working.
Found an error in the VPN log: TCP/UDP: Socket bind failed: Addr to bind has no AF_INET6 record
Thought this was strange because an IPv6 address was present.

Switched one of the connections to my WAN_CABLE (which does get a native external IPv6 from DHCP6) and everything went up without an issue.

After I cleared the "Optional prefix ID" option and reinstated the IPv6 alias for WAN_FTTH, the VPN connections started working on the FTTH interface again as well.

Another observation:
When pinging the IPv6 address on the FTTH interface from within the LAN I get a reply from that interface but with the message "TTL expired in transit". This is true when using the "Optional prefix ID" and when using the FTTH alias setup.
Before this update I just received a normal reply.
Cable interface replies as expected with no issues.

If more details are required for better insight, I'd be happy to give them.

[EmanueleP]

I'm happy for you that you managed to update to version 24.7.4 without any problems. Unfortunately, I tried at least twenty times without being able to update and losing the firewall configuration every single time without being able to restore it from the backups. Every time I try to update, it runs everything perfectly to the point that it also displays the new version in system information, then it restarts and starts again with the old version (24.7.3_1). At this point I have to reconfigure all the firewall rules and the WAN port because even though I made the backup and reloaded it perfectly, the settings do not recover them. Has this happened to others?