This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
RUCKUS Self Help |   ASK the Pack
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

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

martin_kane
Contributor

‎12-20-2013 12:09 AM

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.
5 REPLIES 5

a_n_6322397
RUCKUS Team Member

‎01-31-2014 07:14 PM

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.
0 Kudos
Copyright © 2024 Khoros, LLC