Yes, we have sent a targeted communication to customers that actually have these APs in their networks. A public documentation is also available.  ... View more

MR36 is Wi-Fi 6 AP is there have no been even end-of-sale announcement yet for this SKU.   Edit: there is nothing in the linked thread about end of life/support for MR36.  ... View more

Yes, I'm confused about the model as well.   There is one big upcoming change that will cause really old APs to be truly disconnected from Meraki Cloud for the first time.   https://documentation.meraki.com/Platform_Management/Product_Information/Compatibility_and_Firmware/Firmware_Upgrades/Overview_and_FAQ%3A_TLS_1.0_and_1.1_Deprecation   We have to do this because TLS 1.0/1.1 protocols used by these APs to talk to Meraki dashboard have been long obsolete. Firmware mitigation is available for some APs that are capable of running MR 26.X or newer firmware. ... View more

Actually, you are right. There should be not dependency between Named VLANs/VLAN profiles and IPv6.   However, I'm a bit confused about this part "In my setup I can't get an IPv6 address via DHCP". Did you mean SLAAC and not DHCP(v6)? There are not many clients that support DHCPv6 and SLAAC is a preferred method of IPv6 assignment. There was a known issue with W-Fi 7 APs but it was resolved in MR 32.1.4:     It would be helpful to take a packet capture on both wired and wireless interfaces to ensure that the AP passes traffic back and forth between an DHCPv6 (if this is indeed in use) and a client. ... View more

@MK2 are you referring to https://documentation.meraki.com/Switching/MS_-_Switches/Design_and_Configure/Configuration_Guides/Port_and_VLAN_Configuration/Named_VLANs_in_MS_Configurations on MS switches?   At least on the wireless side I'm fairly certain that we don't have IPv6 support for named VLANs. ... View more

This is not a supported use case, so please do not use Campus Gateway in this way. If you need a remote SSID termination, please use VPN tunnel data to concentrator MX appliance or another appropriate option. ... View more

There is special firmware release for Campus Gateway and APs in the same network. Please refer to https://documentation.meraki.com/Wireless/Design_and_Configure/Deployment_Guides/Campus_Gateway_Deployment_Guide#Deploying_Campus_Gateway ... View more

Yes, WPN requires bridge mode, obviously.  ... View more

But, in any case, MR52 cannot be upgraded to MR 31.X. Only Wi-Fi 6 and newer APs can be upgraded to MR 31.X. ... View more

Correct, MR52 is limited to MR 30.X branch -   https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Product_Firmware_Version_Restrictions    We have another MR 30.X release upcoming with critical fixes for Wave 2 APs. What issues are you trying to resolve? ... View more

I'm assuming you meant CW9162I-MR, Yes, as long as this is a cloud-managed APs running Meraki firmware the Meraki mesh will work. ... View more

Meraki mesh is proprietary and only works between Meraki APs, yes. ... View more

Hi @rsage_voda   This is not a bug, but a feature! 🙂 Cisco has partnerships with Intel, Apple, Samsung, and Zebra, which allows us to receive additional information from these client devices including authentication failures, disconnect reasons, etc.)    Error code 30 is generated in cases of a WPA3 authentication error related to a PMF validation problem. We are developing several client analytics and root cause analysis features that leverage this rich information from our partners, and we are continuously improving these features.   Clearly, we still have some work to do to make these error codes easier to understand. ... View more

Thanks! Could you DM a link to your network? ... View more

Hi folks, DHCP issue on Wi-Fi 7 APs have been confirmed as a regression in MR 32.X and is being looked into. If you have a support case open, please ask am NSE to attach to 12574561 (parent case). Thanks! ... View more

Hi @ACE1 , which regulatory domain your network is using? ... View more

@CharlieCrackle case on point! ... View more

Thanks for reporting @MansHedberg . This mesh issue has been confirmed and engineering is looking into it. ... View more

Hi team, our RADSec implementation only supports TLS. There is no DTLS support. ... View more

Hi @Lurick , please open a support case and DM me the case number. Thanks! ... View more

81% of 2.4GHz radios have been shut down by FRA. Although client SNR remains acceptable, 25% of clients are still using the 2.4GHz band. The coverage from neighboring active radios remains strong. Client RF health scores are also good. While FRA appears to be aggressive, it seems to benefit both the network and the client experience.   Currently, FRA considers client count before shutting down a radio—typically, only radios with fewer than three clients are shut down. Additionally, radios with no clients are automatically taken down during the night.   However, this approach could be improved. FRA should consider the average client count over the course of a day, rather than making decisions based solely on instantaneous or nighttime client presence. We will take action to enhance FRA accordingly.   Finally, based on the AP notes, this is a multi-floor deployment and FRA is might not be able to fully account for such scenarios. This would require further improvements.  ... View more