Loading...
Loading...
If the client enters wrong PSK a couple of times, the user gets added to Wireless Client Exclusionlist even if the "global client Exclusion Policy is Disabled & WLAN policy profile too has "client exclusion" - Disabled, it has no effect. Looks like this feature is broken. #show wireless exclusionlist client mac-address aaaa.bbbb.cccc detail Client State : Excluded Client MAC Address : aaaa.bbbb.cccc Client IPv4 Address: N/A Client IPv6 Address: N/A Client Username: N/A Exclusion Reason : Wrong PSK Authentication Method : None Protocol: 802.11n - 2.4 GHz AP MAC Address : aaaa.bbbb.cccc AP Name: APaaaa.bbbb.cccc AP slot : 0 Wireless LAN Id : N/A VLAN Id : 39
Client Exclusion feature is not working on 16.12.3 & 17.2.1.
Configure exclusion-list timeout to be lowest 1s. exclusionlist timeout 1
Even if we have "wps Client Exclusion Policy" globally disabled, the client still gets excluded. Excessive 802.11-association failures : Disabled Excessive 802.1x-authentication : Disabled Mac and IP-theft : Disabled Excessive Web authentication failure : Disabled Failed Qos Policy : Disabled wireless profile policy Test_PSK exclusionlist timeout 0 But the client will be found in Exclusionlist if the user enters the wrong key multiple times,
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.