VPN IPsec IPv6 tunnels stopped working when going from 24.1.8 to 24.1.9_4

Started by Skreabengt, June 29, 2024, 04:33:15 PM

Previous topic - Next topic
VPN tunnels for IPv6 has been working flawlessly for many weeks in 24.1.8.

Problems started when going to 24.1.9_4. No changes made to any IPsec or firewall setting, but the update created a mismatch between address families in the firewall rule for ISAKMP (port 500) for IPv6, thus mixing IPv4 with IPv6 peers, see error message below. IPv6 WAN Address in dashboard is also dropped after a while.

"There were error(s) loading the rules: /tmp/rules.debug:131: no routing address with matching address family found. - The line in question reads [131]: pass in log on igc0 reply-to ( igc0 2.242.xxx.xxx ) proto udp from {2a07:3aa1:xxxx::xxxx} to {any} port {500} keep state label "00eff9b1ada77af37818877b66bca707" # IPsec: Site1_Site2_IPV6"

Anyone seen this too or any idea what could be the root cause?

The error message have been there for a long time I discovered in the general firewall log and it just prevents that faulty rule from being loaded. There is several other rules that actually were loaded, so likely is the message not related to my problems, since it worked before, despite this single exception after every boot.

Anyone seen IPv6 WAN Address being dropped after a while?

It didn't happen before version 24.1.9!