Bug in CSV NAT import: not all values for "interface" ingested

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Bug in CSV NAT import: not all values for "interface" ingested

L2 Linker

Hi again!


Running Expedition 1.1.28.


A new bug in CSV import of NAT rules.


I have many lines that contain the same value for the field "interface" ("Interface" in the GUI). Only the first line get this value imported. On the subsequent lines with the same value, that field is empty.


It is, however, not so simple that only the first entry works. Near the end of the import, there is a single line with a different value for the field "interface". In that single line, the correct value is imported.




L5 Sessionator

Would it be possible to share the files with us at fwmigrate at paloa tonetworks dot com?


We will check that may be failing in the import process

  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!