Also, I just wanted to confirm if you are using just WPA2-PSK auth or something else like iPSK w/o RADIUS? ... View more

Hi @Dhanushkah have you tried reviewing our new Wireless overview page (Wireless > Monitor > Overview) to drill down on specific problematic clients and find the root cause?     ... View more

This is now planned for MR 29.6 (March 2023) ... View more

Sorry, nope. Hopefully, 29.5 ... View more

Sorry, I meant 5K iPSK groups per SSID - the same soft limit we have for WPN. Also, this did not happen in 29.4, ... View more

Not necessarily. PMK calculation only happens in the backend when a new iPSK group is added. This pre-calculation is always done on the backend and pushed to APs as part of their config. ... View more

You might get lucky! ... View more

OK, so for so many PSKs, one of the main hurdles is PMK ID calculation. This is done on the backend and not on the actual devices, which helps offload much of this work from the actual hardware. This and some other tricks make supporting 1000s of PSKs possible. ... View more

We have a bit of Meraki magic to make this happen 🙂     iPSK w/o RADIUS + WPN (and soon, iPSK w/o RADIUS w/o WPN) has a brilliant way of handling 1000s of keys. That makes it possible to support 5K PSKs per SSID without string AP CPU. ... View more

iPSK limit increase for iPSK w/o RADIUS (w/o WPN) did not make it into 29.4. It's coming in the upcoming MR 29 release. ... View more

There is no AP limit. The only limit is 5,000 PSK per SSID and no more than 2x SSIDs per network. However, these are not hard limits but rather documented recommendations. They are not being enforced. ... View more

It's about 5000 PSKs per SSID ... View more

Hi @MX ,   SES ESL integration is a per-AP feature. If you use a template, ESL needs to be enabled on a template level, and a V:Cloud URL needs to be set (assuming that you are using the direct connection to V:Cloud). Then,  ESL functionality must be activated on individual APs within each child network.     There is no impact on BLE functionality for APs that don't have ESL enabled unless you explicitly turn off BLE on the template level.   ... View more

Yes, iPSK w/o RADIUS scale (50+ iPSK groups) should be available in 29.4. Don't forget that WPN builds on top of iPSK w/o RADIUS.   IPSK w/o RADIUS by itself offers:   No RADIUS dependency = No Complexity (obviously)  Multiple PSKs per a single SSID Different policies per PSK based on Group Policy   WPN adds automatic L2 segmentation for devices that use different PSKs.   Because of that, make sure that you are OK with that 1) your wireless clients that belong to different iPSK groups cannot communicate with each other and 2) these wireless clients cannot access wired resources on the same VLAN. This is because we use GUE encapsulation, and wired devices cannot make sense of it.   https://documentation.meraki.com/MR/Encryption_and_Authentication/Wi-Fi_Personal_Network_(WPN)#Caveats_and_Limitations   I understand what you are doing @CWK_Rob  but be aware of WPN caveats if you are not using WPN for its primary purpose - L2 segmentation b/w iPSK groups to improve the use of discovery protocols like mDNS on shared wireless networks 🙂  ... View more

Hi @CWK_Rob ,   You're correct, WPN supports > 50 iPSK groups by default on r29 firmware.  It looks like you tried to use iPSK w/o RADIUS without WPN, which is a valid use case.   Currently, the number of iPSK groups is limited to 50 when using iPSK w/o RADIUS without WPN. However, we are working on scaling iPSK w/o RADIUS to > 50 iPSK groups, and this will be available in the upcoming r29 firmware release.   Once done, both iPSK w/o RADIUS without WPN AND iPSK w/o RADIUS with WPN will support > 50 iPSK groups. Keep an eye on the release notes 🙂 ... View more

That is wonderful!   I would like to highlight that 36,000 API calls per hour is so much higher when compared to our competitors like MIst with 5,000 API calls per hour  (limited by and dependent on AWS) and Aruba 42 API calls per hour (1000 calls per day) (playing catch-up with a super limited number of API endpoints).   Meraki continues to lead the way with the API-first approach with others are still lagging behind 🙂      ... View more

Hmm, you are probably referring to the MX VPN functionality? This is MR beta 🙂 ... View more

Sure - https://documentation.meraki.com/MR/Access_Control/MR_Meraki_RADIUS_2.0 ... View more

Hi Dave, since you already signed up we will be updating your network automatically. That should happen sometime next week. Keep an eye on the updates in our MR 28 Early Adopters Group. Thanks! ... View more

Sure! Please sign up here ... View more