Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
IPSK is an amazing solution for many scenario and verticals.The IPSK solution of Meraki without RADIUS supports only up to 50 PSKs per SSID, which is not really scalable.The solution with RADIUS, however, requires the RADIUS to know in advance the MA...
As a matter of fact, we can achieve extreme flexibility in the use of PPSK with most of vendors because their PPSK-without-RADIUS mode supports many PSKs (not 50 like Meraki).Ref: https://docs.cusna.io/With Meraki, unfortunately we can't make this ha...
My understanding is that the AP only sends a MAC authentication request (with MAC as username/password). The RADIUS validates that the MAC address matches with a valid device (that's why the need to be added in advance).If the RADIUS finds a match, r...
My understanding (and tests) suggest that Meraki does not send it in the access-request (and for obvious security reasons). Is the RADIUS server adding it as attribute in the access-accept back to the AP, so the AP would start the 4-way handshake, an...
Thanks Philip for the feedback. Regardless the "formula" used, the point is that right now Meraki is not sending any information in the access-request that would allow the RADIUS server to understand who is attempting to connect, except for the MAC a...
