How does Secure Connect deal with NAT rules?

Bucket
Getting noticed

How does Secure Connect deal with NAT rules?

If spokes receive a default route from the SC hubs, does that mean NAT (1:1, 1:many, port forwards) on the spoke stops working when SC is enabled?

1 Reply 1
PhilipDAth
Kind of a big deal
Kind of a big deal

I haven't tested this - but I would expect this to be the case (nat stops working).

 

You would need to change the device to being in hub mode so its Internet didn't go via SecureConnect.

 

 

BUT - could you configure it as a zero trust application and access it using that method?

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.