06-19-2019 09:40 AM
I'm working on producing a CSV file to use as a source for NAT rules. Right now I only need interface hide NAT (using default interface address as hide address).
I have not been able to find any documentation (including the latest published CSV import guide) that has an example that gives any hint to how the fields 'tp_source' and/or 'interface' should be formatted to get this behaviour.
I don't need updated documentation, but would very much appreciate a single example of a line from a CSV file that Expedition can ingest correctly, getting the expected interface hide NAT result.
/Per Westerlund
07-09-2019 08:13 AM
Bumping this.
No help?
I have tried to export NAT rules from Expedition (to Excel) that contains interface hide, but even that export removes the interface that is present in the original NAT rule in Expedition.
Please give us a way to handle importing NAT from CSV, there are still some firewalls (Clavister) that are not natively supported.
/Per
07-09-2019 12:42 PM
There are certainly improvements that need to be made to the CSV import specifically for import of NAT policies using CSV.
The current supported field mappings are described in the link below. The current CSV for NAT does not support the interface option as a field mapping.
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!
