You can also take a look at this.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Configuring_RADIUS_Authentication_with_a_Sign-on_Splash_Page ... View more

It happened with me, probably it is a cable issue or switch port issue. ... View more

In the situation where you use 802.1X for switches and AP's they will just use their management IP (or the optional secondary management IP) as source for the radius requests. However with a physicial MX for Client VPN where the Radius server is over a site to site VPN it will use an internal VLAN IP address.  We had tested this once a few years back where I doubted that this setup would work since the MX normally uses the interface closest to the radius server as source.  But it actually did work. So you would be looking at any VLAN interface on the MX of a subnet that is allowed over the VPN that is the possible source.  The best thing you could do is just to see the logs in your radius solutions just to see where the actual request is coming from.  In case of AutoVPN you can just use the dashboard capture to see what's happening. ... View more

Thanks a lot @alemabrahao  ... View more

It kind of depends how you had port security set up previously. Meraki supports both explicit MAC address whitelisting and sticky MAC address whitelisting. https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Switch_Ports#Port_configuration   It doesn't however support a MAC address maximum where (for example) you enforce only 1 MAC address to be allowed on the port at any one time, but that MAC address can change. The equivalent of Switch(config-if)#switchport port-security maximum 1   ... View more

Hi Philip, thanks for your reply, may I know what is the reason for not using SMS? ... View more