MX 67 WAN Appliance Services

Solved
360IT
Here to help

MX 67 WAN Appliance Services

Hello, 

Question about the WAN appliance services on MX devices. I have an MX 67 that is answering login requests on the WAN port. As far as I can tell the MX is configured to not answer those requests, however port 443 is publicly open to connection requests. 

The WAN appliance services config is below. I see no firewall rules allowing the connection either, so I am a little puzzled. Obviously I don't want the MX advertising port 443 and am hoping someone in the community can shed some light on this one. 

 

Thanks in advance! 🙂

 

360IT_0-1721061520094.png

 

1 Accepted Solution
RaphaelL
Kind of a big deal
Kind of a big deal

That's because you have either a legacy backend option enabled by Support OR the Early Access feature enabled ( they are the same 😞 

NAT Exceptions with Manual Inbound Firewall

 

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

View solution in original post

7 Replies 7
KarstenI
Kind of a big deal
Kind of a big deal

What kind of login requests are you talking about? 

360IT
Here to help

Entering the WAN IP in a browser results in the appliance details page and a login prompt when clicking on the configure button. Exactly the same as you would expect when connecting to the MX via IP on the locally connected network.  

The MX config page is accessible via the WAN port, which I do not want. 

RaphaelL
Kind of a big deal
Kind of a big deal

You probably have the remote local status page enabled : 

 

https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Me...

 

RaphaelL_0-1721064783738.png

 

I never enable that page. Filled with security issues and CVEs. Only enabling it if I don't have any other options.

360IT
Here to help

Interesting in that I don't see a Remote device status page option. 

 

360IT_0-1721065016427.png

 

RaphaelL
Kind of a big deal
Kind of a big deal

That's because you have either a legacy backend option enabled by Support OR the Early Access feature enabled ( they are the same 😞 

NAT Exceptions with Manual Inbound Firewall

 

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

RaphaelL
Kind of a big deal
Kind of a big deal

I just checked on of my network that has the legacy NAT Exception option and the Remote status page option is visible. I don't know why it is not showing in your case.

 

Edit : Enable or disable access to wireless et switch device status pages at http://[device's LAN IP].

 

Forget the "Remote device status pages".  Just try to disable the local status page and check if you still have the page accessible.

360IT
Here to help

The NAT Exceptions with Manual Inbound Firewall opt in is disabled. I'll call support to find out about the legacy backend option.

Thanks very much for your quick responses!! 🙂

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