Firewall Rules [new] populated after update to v26.1.10

[mlenje]

I have been putting off running the migration assistant until I had time to set aside and be able to test everything.  Tonight, when I upgraded to v26.1.10, the Firewall Rules [new] were populated.  Are they active?  Do I still run the migration assistant? Should I rollback to v26.1.9 and run the migration assitant before upgrading to v26.1.10? The relase notes say "o firewall: always show automatic and legacy rules in new rules GUI" but I judt thought that meant if you had already ran the migration assistant?  Thoughts on next steps?

[Monviech (Cedrik)]

Before this update if you pressed Inspect in the nee Rules GUI it would show all automatic and legacy rules. Now it just always shows them.

They are collected via script and displayed only.
https://github.com/opnsense/core/blob/b4fa4cd2e2f6743eaf49e0523b2303fd31c3ee59/src/opnsense/service/conf/actions.d/actions_filter.conf#L199


Just like in the legacy GUI you will see a "Rules from Automation" header below the Automatic Rules header if you have actual rules defined in the new Rules GUI.

So you still have to migrate at some point in the future, but not right away if you still need more time. Don't worry.

This change was made because there was a constant struggle to find the automatic rules in the new GUI. But due to reasons, legacy rules and automatic rules come from the same endpoint internally. They're clearly marked though with their own distinct command symbol. If you click that, it will jump to the legacy rule page.