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

  • 1
  • Question
  • Updated 4 years ago
  • Answered
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.
Photo of Martin Kane

Martin Kane

  • 72 Posts
  • 7 Reply Likes

Posted 4 years ago

  • 1
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
@Martin, thanks for sharing your observation. We're investigating.
Photo of Martin Kane

Martin Kane

  • 72 Posts
  • 7 Reply Likes
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
Photo of Martin Kane

Martin Kane

  • 72 Posts
  • 7 Reply Likes
... but it would be NICE to know WHICH policies ARE held in the autonomous WLAN?
Photo of Martin Kane

Martin Kane

  • 72 Posts
  • 7 Reply Likes
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)
Photo of Andrew Nisbet

Andrew Nisbet

  • 1 Post
  • 0 Reply Likes
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.