Keep it in mind:   Client Isolation is available for SSIDs configured for Bridge mode however is disabled by default. When a SSID is configured for bridge mode, clients are bridged through the Access Point potentially to a specific VLAN. Upon connection to the AP, clients will be permitted to make a DHCP request on the VLAN they are assigned to. After DHCP is completed, the MAC address of the default gateway is tracked for the particular client.      NAT Mode Client Isolation SSIDs that are configured for NAT Mode also have basic client isolation. Basic Client Isolation is enabled by default when the SSID is configured for NAT mode and cannot be disabled.  The implications of enabling NAT mode are as follows: Devices outside of the wireless network cannot initiate a connection to a wireless client. Wireless clients cannot use Layer 2 discovery protocols to find other devices on either the wired or wireless network. For more information on NAT mode, please see NAT Mode with Meraki DHCP. ... View more

In your other post I posted a screenshot;   https://community.meraki.com/t5/Wireless/Client-Isolation/m-p/282828 ... View more

Go to Firewall and Traffic shaping, select the SSID and aneble it.   https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation ... View more

Yes, they work without any problem. ... View more

The @PhilipDAth's statement is correct. ... View more

I would try the new version as it has fixes for some bugs.   Bug fixes General stability, performance, and experience improvements 6GHz/160MHz mesh not forming on MR57, CW9166I, CW9166D1, CW9164I APs APs do not send beacon frames on the 5GHz radio (Wi-Fi 7 APs) Increased CPU & memory utilization on MR57 APs ... View more

One question, what is the average number of clients per access point? ... View more

You can call them.   https://documentation.meraki.com/General_Administration/Support/Ways_to_Contact_Meraki_Support#Contact_Support_by_Phone ... View more

This version is old, I suggest you  upgrade to version 17.15.3 which is recommended by Cisco. ... View more

What version are you running? Older versions rely on a container for Meraki monitoring. Newer versions (17.15.x and above) have native support. ... View more

You can try using add_host to create a temporary host with variables attached. ... View more

Were you able to test with another DNS server? ... View more

This usually indicates that your Meraki device isn't receiving responses to its DNS requests, preventing it from resolving dashboard URLs and other internet addresses. Try using a different DNS server IP address to see if the issue persists. Just out of curiosity, do you have a firewall that might be restricting something? ... View more

"But in this case, I believe the internet connection will be local, and we won't be enabling the "default route" to be the Hub. I heard this from support; it makes sense, right?"   Yes that is right.   "Regarding this configuration, "Once this is done, activate this /30 network in the auto VPN and set the hub to the spokes," that would indeed be the step, right? 1st - Addressing & VLANs Routed Mode Single LAN - I would need to change the default address on the DC from 192.168.128.1/24 to my real network 192.16.168.1/30 (Enable)"   Yes this should work. ... View more

I think it could go even further. On the C9800, you can create regular expressions to define which RF profile, site tag, and policy tag should be applied to access points based on a specific condition. For my clients, I always use the access point name in the condition to apply tags. So, I believe Meraki could have something similar. ... View more

Yes, that statement is correct. ... View more

Will you be working with a hub and spoke topology? If so, I believe the hub will be located in the main DC, correct? The hub needs to have an interface directly connected to this network or a route. Once this is done, activate this /30 network in the auto VPN and set the hub to the spokes. This way, they will receive the route automatically.   https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN_-_Configuration_and_Troubleshooting ... View more

Hi, unfortunately, No NAT configuration is not currently exposed via the Meraki Dashboard API. ... View more

Yes, I am.   End-of-support (EOST) date: The last date a product will be affirmatively supported by Cisco Meraki, typically five years following the EOS date. ... View more

Theoretically, the end of support for this camera is December 31, 2030, and the end of purchase date is December 31, 2025, so you should be able to renew support. See the list of dates.   https://documentation.meraki.com/General_Administration/Other_Topics/Meraki_End-of-Life_%28EOL%29_Products_and_Dates     Summary End-of-sale (EOS) announcement: Date of official end-of-sales notice, typically six months prior to the last order date. End-of-sale date: The last date to order the product through Cisco Meraki point-of-sale outlets. After this date, the product is no longer available for sale via any channel. End-of-support (EOST) date: The last date a product will be affirmatively supported by Cisco Meraki, typically five years following the EOS date.   ... View more

Have you tried restarting the MX? ... View more

Unfortunately not, in this case the ideal would be to replace the hardware with an equivalent model. ... View more