Early Access - NAT Exceptions with Manual Inbound Firewall

RaphaelL
Kind of a big deal
Kind of a big deal

Early Access - NAT Exceptions with Manual Inbound Firewall

Hi !

 

Just noticed that 

NAT Exceptions with Manual Inbound Firewall

is now available via the Early Access program 

 

Org -> Early Access -> NAT Exceptions with Manual Inbound Firewall

RaphaelL_0-1714441148781.png

 

 

https://documentation.meraki.com/MX/Networks_and_Routing/NAT_Exceptions-No_NAT_on_MX_Security_Applia...

 

This is nothing new , but you don't have to contact support to enroll which is nice !

4 Replies 4
TYehlik
Meraki Employee
Meraki Employee

WARNING: There is a known issue after enabling the No-NAT with Manual Inbound firewall Early Access Feature. The UI shows the default inbound firewall rule as Deny Any Any, but if the inbound firewall table has no other rules created this will be enforced as an Allow Any Any rule. We are actively working on correcting this behavior.  In the meantime, adding any rule to the inbound firewall will correct this behavior and the default rule will be enforced as expected.

TYehlik
Meraki Employee
Meraki Employee

The issue mentioned above has been resolved.

Mloraditch
A model citizen

Coincidentally I had previously enabled this somewhere to test and things were working, enabled at another client today to further check things out and I guess this issue popped up an issue as inbound client vpn (AnyConnect) was shut off.

The documentation doesn't seem clear that this will happen nor what rules are necessary to avoid it.  Might be helpful to spell out examples in the documentation of how to allow this.

TYehlik
Meraki Employee
Meraki Employee

Thank you for the recommendation. We will look into clearing up the wording in the documentation. 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels