After importing my Fortinet config, the service object named POWERNEXT was incomplete and I had to fix the protocol and port by myself.
I did some tests and found that the parsing process stopped when it found NEXT after an edit keyword. I've tried different keywords used in the xml but only the NEXT in a service object fails.
Here's an example :
config firewall service custom
set tcp-portrange 995
set tcp-portrange 996
set tcp-portrange 997
set tcp-portrange 998
set tcp-portrange 999
After the import, I have to fix manually the settings for the "NEXT" service object. The 4 other services are good.
I'm using Expedition version 1.2.27 - not sure which other version is affected.
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!