topic Re: Blocked clients DON'T get blocked from the new autonomous networks in ZoneDirector

Blocked clients DON'T get blocked from the new autonomous networks

martin_kane — Fri, 20 Dec 2013 08:09:22 GMT

Was about to submit a case once I noticed previously blocked WLAN clients again appearing on a WLAN! Then realised that it was because I had changed the network type to autonomous - so obviously the client MAC addresses were not being checked with the ZD! I wonder what other effects this has? Device policies ignored? Rate restrictions ignored? I mean, blocking being ignored is pretty serious.

Re: Blocked clients DON'T get blocked from the new autonomous networks

keith_redfield — Fri, 20 Dec 2013 16:05:26 GMT

@Martin, thanks for sharing your observation. We're investigating.

Re: Blocked clients DON'T get blocked from the new autonomous networks

martin_kane — Fri, 20 Dec 2013 18:11:03 GMT

I don't know that it's actually a fault as such... Seems to make sense that if a WLAN is autonomous from the Zone Director that it won't check policies held in the ZD. It's really just a warning I posted, rather than a complaint - but worth sharing "my" mistake so others don't make it.

Martin

Re: Blocked clients DON'T get blocked from the new autonomous networks

martin_kane — Fri, 20 Dec 2013 18:13:29 GMT

... but it would be NICE to know WHICH policies ARE held in the autonomous WLAN?

Re: Blocked clients DON'T get blocked from the new autonomous networks

martin_kane — Fri, 20 Dec 2013 21:51:36 GMT

Have noticed (since changing the WLAN back to Standard) that the supposedly "blocked device" is now caught in a trap of "failing authentication too many times" - so that's not normal behavious for a blocked device either.

(Blocked device is an Apple TV, BTW)

Re: Blocked clients DON'T get blocked from the new autonomous networks

a_n_6322397 — Sat, 01 Feb 2014 03:14:01 GMT

Here's a quick update for anyone following this:

ZoneDirector’s Block Clients (system wide) feature will not prevent listed clients from connecting to an autonomous WLANs when a L2 ACL is assigned to the autonomous WLAN.

When no L2 ACL is assigned to the autonomous WLAN the Blocked Clients feature functions as expected.

As a work around you can copy individual clients MAC to the assigned L2 ACL to prevent these clients from connecting to the associated autonomous WLAN.

The ongoing status should follow in release notes for subsequent 9.7 releases.