I get this too. RB5009.
Just run it again. I don’t get the error if I run it again.
The error message with "expected end of command (line 1 column 67)" is "normal" on newer RouterOS versions and can be ignored. That's from this command being executed:
:execute runs the script in the string in the background, so the "line 1 column 67" is the position in this string, and it's the position of hw-offload=yes, which is not recognized anymore if your devices does not support L3HW with NAT/Fasttrack.
@rextended put the command in :execute to not to have to deal with version checks (previous versions of the script needed to check for versions to decide whether to add hw-offload=yes or not) because errors in the command will not break the script calling :execute.
2 Likes
Thanks for the reply, I would have answered the same.
7.22rc1 do not add anything new from 7.22beta6
1 Like
Refreshed for new versions 7.21.2 -> 7.21.3 and 7.22rc1 -> 7.22rc2
No changes.
Is it possible to have a dry run option?
In what sense?
You could use the safe mode. Something like this, adhoc from my mind:
/safe-mode/take
run script
ip firewall export
ipv6 firewall export
/safe-mode/unroll
Not exactly a dry run. But somehow. 
Print the change rather than commit immediately
Nothing in RouterOS has this feature.
The script is quite clear and you can clearly read what it does and what it modifies, just follow it,
comparing with what already is your configuration...
To see the changes, if any, just do an export first (and a backup and copy it outside, just in case...),
then apply the script,
then do another export with a different name,
just compare the two files with any of the dozens of programs that compare files to find the differences,
and you're done.