I posted this earlier, but can't find it anymore...
Attempting to convert a Fortigate config to PAN, and the MT gets confused by several lines in the config that were intentionally split by the Fortinet due to length. Basically, any lines longer than about 990 chars are split with an exclamation mark + newline + space at the break point.
Basically, say the following snippet if part of a long line, and assume the O in LO is the 990 character:
..... VERY LONG LINE .....
the Fortinet config would generate the following in the config output:
..... VERY LO!
NG LINE .....
I used an underscore above (in red) to reflect the space at the start of the 2nd line. MT gets confused during import, and creates strange objects, and misses a bunch of stuff.
Its the first time we found this.Let us fix it. If you can send some real examples to email@example.com will help us to speed up the process :-)
Fix 3.2.1 implemented.
Added warning when a address wildcard type is found. we dont support yet those kind of netmaks
Added Fix to support multiline configs splitted by !
Please let us know if it works.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!