Quote from: Burthouse4563 on July 04, 2026, 06:46:16 PMHere's an example rule directly from the export tool from the migration assistant, which throws the same error.
;1;0;0;101;wan;inet;any;lan;0;;any;0;;;;0;0;;;;"LAN to WAN"
Quote from: flushell on July 04, 2026, 05:16:46 PMYes, I see now that if I change then old one to Automatic, the other is on Automatic too now.That's how it's designed to work : I asked about it earlier this week :)
QuoteNote that this update brings the outbound to source NAT migration page, but itAnd from what I have read earlier in this topic : https://forum.opnsense.org/index.php?topic=52261.msg269516#msg269516
is only a formality as outbound NAT will stay in 26.7 although the legacy
firewall rules page will move to a plugin during the major upgrade. It is the
same process that was employed with ISC-DHCP. Due to this addition, however,
the source NAT rules entered in the system will no longer work unless the
mode is set to either "manual" or "hybrid".
Quote from: mschaeffler on July 04, 2026, 03:54:52 PMHi,
Is this only for the Outbound NAT?
What is with Destination NAT?
Thank you
Quote from: meyergru on July 04, 2026, 04:06:42 PMWhere do you want to migrate the destination NAT rules to?
The only reason to migrate "Outbound NAT" to "SNAT" (aka "source NAT") was that this is the more common term. "Destination NAT" is already called correctly.
Quote from: dseven on July 04, 2026, 09:55:49 AMThe 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?