Messages

I'm also having the same problem as you but don't know how to solve it.

1. Take out the configuration from OpnSense
2. Rename config file as config.xml
3. Put the file to a same directory with migrate.exe
4. Run migrate.exe from command line (command prompt)
5. Untick reboot firewall
6. Restore new_config.xml to OpnSense

So this is quite weird. I reverted back to 24.7 kernel from another thread and it fixed the problem.

It was on a Wireguard connection. Looks like other Wireguard connections survived the upgrade. Have to visit that office.

Coming from 24.1.10_8.

I'm having two offices, the first one is 10.0.0.0/16 and the other one is 10.1.0.0/16. Until I upgraded to the newest version I've been able to connect 10.1 from 10.0. After upgrade it looks like the route to 10.1 is lost. As it is using an independent fiber the Internet works, but I'm not able to connect internally to that network anymore. Before the upgrade networks were co-operating fine.

On the other end there is an Edgerouter X.

Any suggestions what to check?

I broadened network mask from /24 to /23 on one network. When using ips from the new block Unbound refuses to give answers to queries. Unbound allowlist has the new /23 in its rules, but its not working. As a workaroud I made a new network /24 manually (the new block) and after that queries work normally. Also the original /24 works even though it is /23 in the list. Is this a bug or something?