Missing filter attribute 'Interface' for NAT Policies

Announcements

Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

Reply
Per_Westerlund
L2 Linker

Missing filter attribute 'Interface' for NAT Policies

Hi!

 

I'm running Expedition 1.1.28 and working with at large (200+) set of NAT policies imported via CSV. In my case, I would have liked the possibility to apply filters based on the value of the Interface attribute. However, that attribute is missing in the list.

 

Is it possible to have that attribute added?

 

/Per


Accepted Solutions
sjanita
L4 Transporter

ok I know the field you are looking to filter on. I will submit a FR.

View solution in original post


All Replies
sjanita
L4 Transporter

To clarify are you looking for a filter to isolate NAT policies that are configured to NAT using an address-type of 'Interface'

 

Or are you looking for a filter for a source interface if configured?

Per_Westerlund
L2 Linker

I an looking for a filter for the (normally hidden) column 'Interface' in the NAT Policy tab. It belongs to the section where you describe the original packet to be handled. The optional field to describe which interface you are interested among possibly several egress interfaces belonging to a destination zone.

 

Ta answer your question directly, not source NAT of interface type, the other kind.

 

/Per

sjanita
L4 Transporter

ok I know the field you are looking to filter on. I will submit a FR.

View solution in original post

Per_Westerlund
L2 Linker

OK, thanks!

 

/Per

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!