Is the device really blocked?

[AY2022]

Hi All, 

Would like to see whether this is 'normal' for everyone

From the clients page of a device, device policy is set to Blocked (all), followed by Save. 

I gave it 5 min and then click disconnect client. 

I then waited another 5 min and refresh the page. 

Under overview > status, I still see the same device associated since (most recent date / time), with all the other information filled. 

When I checked the device physically, the IP show on the portal matches to what the device is getting. 

So I'm wondering whether the device policy (block) is really working? How can I tell? 

Thank you.

[alemabrahao]

Blocked does not mean that it will be prevented from connecting.

What will happen is that the device will not be able to access network resources, both internal and external. So yes, it is normal.

[alemabrahao]

Look at this.

[Brash]

Applying a block policy doesn't prevent the device from WiFi association. It just means that they won't be able to browse to anything.

So you'll still see them as connected in the Meraki portal but they should be blocked from accessing anything.

Reference: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Blocking_and_Allowing...

[AY2022]

Thanks for the prompt reply and sharing. 

Is there a way to prevent that particular device from successfully connecting?

I do not want to change the password (as it will affect other devices), but I want to "flush" this device out so that I can remove the saved SSID (which is the wrong SSID in the first place) from it.

[alemabrahao · Accepted solution]

Nope. Just changing the password, or using another authentication method like 802.x for example.

[TBHPTL]

Even if you did block their mac address, they would just change it... the way to prevent them from getting an IP is to implement 802.1X on the SSID. no valid creds = no  IP,  no access. Client will attempt to join but will fail every time.