Skip to main content

77 Messages

 • 

1.2K Points

Fri, Dec 20, 2013 8:09 AM

Answered

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

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.

Responses

683 Messages

 • 

11K Points

7 years ago

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

77 Messages

 • 

1.2K Points

7 years ago

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

77 Messages

 • 

1.2K Points

7 years ago

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

77 Messages

 • 

1.2K Points

7 years ago

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)

1 Message

 • 

62 Points

7 years ago

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.