Just a quick report that I upgraded from the 25.7.11 development version to 26.1.r1, so far without issues.
Switching back to Community doesn't replace the automatically installed os-isc-dhcp-devel plugin with the non-devel version, but I think that's expected. It's an additional manual step which might be worth mentioning in the upgrade instructions.
I keep hostwatch disabled for the time being, so no statement about that.
Cheers
Maurice
Same for me, I did pgrades two OPNsense installation.
One from an installation which was on the Development channel, by switching as France explained, no issue.
The other was on the Dev channel too (not that it matters), exported config (to be sure) and reinstalled using the DVD ISO. The config was found on the ZFS pool and installation when smooth, and with the config found on the ZFS pool.
The only confusing thing was that after the installation and before the reboot the text on the console told me that the OPNsense GUI will be reachable on 192.168.1.1. That specific installation is IPv6 only, so I wasn't sure if the config was applied correctly - but it was.
Ah, oui, naturellement. ;)
I added a note about the plugin situation in the forum announcement post.
The "https://192.168.1.1" is a bit of a hardcoded relic.
https://github.com/opnsense/core/blob/e75192ca461dfa/src/sbin/opnsense-installer#L53
From an imported config where "lan" may not exist it can be difficult to extract the correct value from. Let's call it an artefact for now.
Cheers,
Franco
I switched to 26.1-RC1 as well. Most things worked OOTB, however, I found that the NAT rules filter associations were gone, showing only "Manual" instead, although some link still exists as evidenced by the associated firewall rules being non-editable as usual.
After I tried the first steps of rules migration, all new style rules had no categories and were disabled per default. I wonder what would have happened if I followed the instructions and just removed the old rules at that point.
I tried to understand how the NAT rule linkage relates to new/old rules, but failed. Since it was a production system, I did not dare to remove the old rules.
What is irritating is that "floating rules" now are just the ones that have more than one interface, so if you add an interface to any existing interface rule, the rule shifts to floating rules (and also the other way around). However, I like that, because with the old style rules, you manually have to re-create a rule in the floating section. One has to get accustomed to this, however, because I also used 1-interface-only floating rules for blocking in the floating section just because of the priority being greater than implicit port forwarding rules.
Uwe, can you check the CSV if the enable flags and categories are exported correctly for you?
Thanks,
Franco