Title says it all. It's a minor thing but should be a simple fix.

Right now the meraki devices failover after a 300s waiting period while testing is being done prior to the device switching from WAN1 to WAN2. IN this soft failure situation the customer is having all kinds of issues connecting externally. There should be configurable settings in the device. IN an RDP environment any latency or loss above 3 - 5 seconds and end users start to freeze and get disconnected from sessions. IF soft wan failures due to latency and loss were configurable so you didnt have to wait the full 300 seconds this would be ideal. Fail after 3 missed pings. This way connection based items such as RDP are limited in the outage time they have to take.

There should be a way to specify a different external IP for Guest WIFI networks. ideally i rather not have the Guests and Local Users on the same External IP

I wish I could label the physical ports on the MX from the security appliance page or have it display the client name of the device connected to that port.

I would like to see Meraki implement Site-to-Site VPN Translation for non-Meraki firewalls.

I have VPN with multiple third party firewalls through vendors that I share info with and I think is crazy that Meraki does not offer this feature since its common on all modern firewalls.

This feature currently only works for Meraki to Meraki firewalls and no everyone will have a Meraki firewall

You have NAC built-in to the wireless side of the house, but not easily doable with the switch side of the house. Our network is airgapped and wireless is totally physically segregated from the corporate LAN. We would love to utilize Meraki for NAC at the switch level, even with a simple whitelist, but the functionality doesn't exist.