For what its worth.  We disabled 802.11be and and have been stable(ish) from a roaming / client association standpoint.   At least the phones stopped ringing.   We are using CW9176I  WPA3 2.4 / 5 / 6ghz radios enabled on MR 31.1.8.  Tuning off BE was the biggest impact for stability.   Now why did we pay for WiFi 7 when we can't use it...  Maybe one day....     ... View more

I think the issue is not on the Meraki itself, but our device. We tested variety of device such as HP, Mac, Dell and Lenovo. We are using Lenova Thinkpad T16 with AX211 WiFi card, all device not jumping here and there, only Lenovo having this issue. We have contact our local Lenova support, they said "well known issue" but there is no solution for this.  ... View more

Fixed an issue causing switches to restart after stack failovers   Is this know issue has been fixed ? Can someone verify this ? ... View more

Yep already did. This is just a testing, so i put gmail.com as the domain. Since this is a guest wifi, we would try a simple guest configuration first. ... View more

 GET /networks/{networkId}/appliance/uplink/settings   When i run this command, im getting wan1 and wan2 IP from different setting. It doesnt show the public IP on meraki. Please advise ... View more

Cisco Meraki devices can identify the hostname of a client device using NetBIOS, Bonjour, and DHCP. In some instances, the detected hostname may be undesirable. For example, 2 devices on the same network with identical hostnames or a device that has been identified by its MAC address. The hostname can be overridden within the Meraki dashboard by configuring a manual value.    The client's hostname will be determined in the following order of preference: User-specified Name MDNS Name (Bonjour) NetBIOS Name DHCP Hostname   In short, it will depend on the information that Meraki receives from these elements, but there is no guarantee that the hostname will be correctly identified. ... View more