Then you need to create ACL's as per your access control requirement and then go to Security==>Local Policies create the policies as required and associate the correct ACL's. Finally go to WLAN and polciy-mapping and set the policies you created. This way you can achieve your requirement, but please note that the other devices trying to connect to the WLAN will not be informed why they cannot connect.
My preferred way is to use an advanced Radius server like ISE, Clearpass etc. and do device profiling. Based on the outcome of the profiling allow access and who gets denied will be redirected to a splash page which says why there access was rejected.
Listen: https://smarturl.it/CCRS8E33 Follow us: https://twitter.com/ciscochampion The goal for stadium and large venue Wi-Fi is to deliver an exceptional, fast, and reliable wireless experiences to tens of thousands of fan...
We are pleased to announce the immediate availability of the IOS-XE release 17.6.1 for the Catalyst Wireless Controllers. The new code is now posted on the CCO and can be found at this link:
This version now introduces experimental new feature, "Upgrade Advisor, targeted to one of common case generators: what are the supported versions and how to upgrade my current controllers and APs
It supports both AireOS and IOS-XE, covering since ...
Thank you for the overwhelming response to the First and Second EFT refresh of 8.10MR6!
We are excited to announce the third refresh of 8.10 MR6 EFT Program for PRODUCTION deployments.
While the CCO release of 8.10MR6 is just a few we...
Greetings!Thank you for the overwhelming response and feedback for the first 17.3.4 EFT/Beta release.
Now we are excited to announce the second refresh of 17.3.4 EFT/Beta Program for PRODUCTION deployments.
This release is the s...