topic Re: Bug in CSV NAT import: only last line imported correctly in Expedition Discussions

Bug in CSV NAT import: only last line imported correctly

Per_Westerlund — Wed, 29 May 2019 11:39:46 GMT

Hi!

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!

/Per Westerlund

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.

Re: Bug in CSV NAT import: only last line imported correctly

sjanita — Thu, 30 May 2019 13:16:51 GMT

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.

Re: Bug in CSV NAT import: only last line imported correctly

Per_Westerlund — Thu, 30 May 2019 21:19:43 GMT

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:

First import

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:

Second import

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.

Re: Bug in CSV NAT import: only last line imported correctly

dgildelaig — Thu, 13 Jun 2019 09:06:14 GMT

Thanks for reporting this.

We will check this behavior. Do you have those objects already declared in the project where you are going to import the NAT rules?

Re: Bug in CSV NAT import: only last line imported correctly

Per_Westerlund — Thu, 13 Jun 2019 09:41:57 GMT

Yes, this was supposed to be the final touch, everything else (addresses, services, routes, security rules .....) was already imported without complaints, all objects referred to were pre-existing.

/Per

Re: Bug in CSV NAT import: only last line imported correctly

Per_Westerlund — Wed, 19 Jun 2019 14:04:38 GMT

Hi all!

I never got a proper followup to this, nor did I find anything in the release notes I managed to find, but when I tried the same example with 1.1.24, it worked as expected. Both columns Source and Destinations are now populated for all rows in the CSV file.