NAT Migration Tool

Started by Burthouse4563, July 03, 2026, 04:40:25 PM

Previous topic - Next topic
I just upgraded to 26.1.11_5 and performed firewall rule migration without issues. I went ahead and started looking at the NAT migration. I'm using manual NAT outbound rule currently. I exported my rules without issue. When I attempt to import, though, I get validation failed for every rule with the following error.

@uuid;"Invalid UUID offered (;1;0;0;1;wan...

I added a single manual rule to see what it was expecting and upon export got

1bdd4169-e821-40ba-98b0-83fdc10c8378;1;0;0;100;lan...

So clearly the new NAT rules are expecting more than what the old ones are exporting with regard to UUID.

Is this a known error, or will it be fixed in an upcoming release? I'd prefer not to manually input all rules; I will if I have to, but if this is going to get fixed, I'll wait.

Thanks to the team for what you do.

Today at 09:55:49 AM #1 Last Edit: Today at 10:07:44 AM by dseven
The UUID can be empty (otherwise it must be a properly formatted one):

https://github.com/opnsense/core/blob/20070de6fca7fc83605c856bd0b84753a86fa7c2/src/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/ArrayField.php#L334-L348

I wonder if your CSV file somehow got corrupted with unprintable characters, or something. Did you do anything with the file other than let your browser save it during export, then open it for import? Try a different browser maybe?

Edit: ... actually, looking at your error message again, it looks like it's considering the whole line to be the UUID, so parsing the CSV seems to have failed somehow. I still wonder if something happened to corrupt the file...

Edit 2: Oooh, I have a theory - do any of your rules have a comma (,) or semicolon (;) in their description?