Rules migration wizard seems to glitch out

[Headless1919]

I upgraded to 26.1_4 today and tested out the rules migration. After removing some warnings during the import process (mostly interfaces which no longer existed), I attempted to import in the new format.

The import seems to work when done in its entirety, but leaves me with ~180 floating rules, most of which are blank and cannot be removed. I also see warning messages in the system logs but attempting to remove what appears to be an offending interface and reimporting does not help.

Does anyone have any ideas before I resort to recreating my rules manually?

[Monviech (Cedrik)]

You might have run into this issue:

https://github.com/opnsense/core/issues/9661

Will be fixed in an upcoming release, just make sure when you edit rules you don't use Excel since it can add "" around rows and thats what probably messed your import up.

[Headless1919]

You might have run into this issue:

https://github.com/opnsense/core/issues/9661

Will be fixed in an upcoming release, just make sure when you edit rules you don't use Excel since it can add "" around rows and thats what probably messed your import up.

I was using Excel, perhaps that is it. I can wait for a new release, thanks Cedrik!

[Monviech (Cedrik)]

Well in a new release it will only prevent you from importing the faulty data, but when you use excel you can still run into the faulty data issue. Best use a plaintext editor that doesnt automatically format rows.

[Headless1919]

That seems to have done it, thanks Cedric. Changes made in Notepad, imported without an issue. Saved me a lot of work!

[nero355]

Well in a new release it will only prevent you from importing the faulty data, but when you use excel you can still run into the faulty data issue.
Best use a plaintext editor that doesnt automatically format rows.

That seems to have done it, thanks Cedric. Changes made in Notepad, imported without an issue. Saved me a lot of work!

When editing Linux/*BSD related files there are IMHO basically only two options :

- When editing from Windows use something like Notepad++ which can safe the file again after editing in a way that it's safe for use with Linux/*BSD systems.
- When editing from Linux/*BSD just use nano or vi and everything will be OK :)

The reason for this is that the file will otherwise contain stuff like "\n" at the end of each line for example and you will encounter one error after the other... horrible!