Rule migration: Inverting destinations is only allowed for single targets

Started by szotsaki, Today at 03:22:17 PM

Previous topic - Next topic
I followed the migration wizard steps and after importing the rules I was given four "lines" in a pop-up window without further explanation. Whether they are errors or just warnings, or whether the said rules were migrated or not were not clear.

These are two examples:
destination_net Inverting destinations is only allowed for single targets to avoid mis-interpretations bf920f1c-a9ab-4383-8dd7-9ca5e9b8c2f7;1;keep;;371;pass;1;0;lan;in;inet46;any;;;;;0;1;0;0;0;;;;;;;;;;;;;;;;;;;;;;;"Allow access to WAN";0;lan;;1;PrivateIPv4,PrivateIPv6;
destination_net Inverting destinations is only allowed for single targets to avoid mis-interpretations 2ace6415-7b35-4c42-9bb8-ee5415de71ec;1;keep;;451;pass;1;0;opt1;in;inet46;any;;;;;0;1;0;0;0;;;;;;;;;;;;;;;;;;;;;;;"Block access to other internal networks but allow access to the Internet";0;opt1;;1;PrivateIPv4,PrivateIPv6;

After the import, I see them in the new rule set table, but I cannot edit them:



I can look up for the "reference" for these rules with the button, but will they be gone after I remove the old rule set? Currently, I assume so.

Could you please handle these kind of rules during import gracefully?

Additionally, I find the old rules editor a lot better from UX perspective:
  • Physical keys (up, down, PgUp, PgDn) work on the page right away, no need to click around
  • Having two scrollbars next to each other (page in page) is weird, just to have an Apply button in the bottom.
  • Restricting a huge table on a huge monitor into a small area with many borders feels very cluttered.