Running Expedition 1.1.21.
Still struggling with Clavister import. Have created CSV files for NAT policy. Address already populated.
When I import the CSV file, the columns 'src' and 'dst' always get the value 'any' not matter what value I put in, except for the last line in the file!!
The very last line in the file populates the columns Source and Destination correctly. This does not work with previous lines. (I have a header line that pre-selects the correct column mapping).
Please fix, is a bit nasty!
PS: If/when you work on this, please take a look at the import logic for tp_source, I want to be able to express interface-hide, and how to do that is not documented as far as I have seen.
The CSV import for NAT policies was recently added and will be enhanced in future releases.
I have sucessfully tested the src and dst (using the headers from;to;src;dst;tp_source;tp_destination;service). can you paste an example of one line from your CSV for the NAT policies? before pasting change the IP's of course.
Here is the beginning and end of the input file I'm currently using:
name;from;src;to;dst;service;description;tag;isdisabled;tp_source . . HttpAll_ResursII_PubAll;Vlan_ResursNetII;ResursNetII_ip_net;Pub_ge4;all-nets;http-all;;Grund;;Pub_ge4 DNSAll_ResursII_PubAll;Vlan_ResursNetII;ResursNetII_ip_net;Pub_ge4;all-nets;dns-all;;Grund;;Pub_ge4
Importing this I get this result:
If I undo that import and change the order of the two last lines of the file and import it, this is the new result:
All previous NAT rules have Source = any, Destination = any. It is always only the last line that shows success in parsing the columns src/dst.
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!