When a user tries to access the WLAN that is configured for MAC filtering, the client MAC address is validated against the local database on the WLC, and the client is granted access to the WLAN if the authentication is successful.īy default, the WLC local database supports up to 512 user entries. With local MAC authentication, user MAC addresses are stored in a database on the WLC. There are two types of MAC authentication that are supported on WLCs: When you create a MAC address filter on WLCs, users are granted or denied access to the WLAN network based on the MAC address of the client they use. MAC Address Filter (MAC Authentication) on WLCs Refer to Cisco Technical Tips Conventions for more information on document conventions. If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. The information in this document is based on these software and hardware versions:Ĭisco 4400 WLC that runs software version 5.2.178.0Ĩ02.11 a/b/g wireless client adapter with firmware 4.4Īironet Desktop Utility (ADU) version 4.4 Prerequisites RequirementsĮnsure that you meet these requirements before you attempt this configuration:īasic knowledge of the configuration of LAPs and Cisco WLCsīasic knowledge of Cisco Unified Wireless Security Solutions This document also discusses how to authorize lightweight access points (LAPs) against an AAA server. If this needs to be permanent bypass you may find this only works so far as the IP Lease for that connection to the Hotspot, and if the IP Lease expires it may break this relation with the Hotspot binding and you will have to delete the and recreate the binding.This document explains how to configure MAC filters with wireless LAN controllers (WLCs) with a configuration example. This would also exclude the 'client' from the stats that our systems provide. In that way when the MAC is encountered connecting to the Hotspot it gets a connection to the internet without having to use the Hotspot login process. It should be possible in the future to 'allow' clients based on their MAC via the Portal systems, but for not, on a Mikrotik, you might, on the Hosts tab of the Hotspot, right click on the MAC of the connected device, and select 'Make Binding'Īnd from there select the 'Type' of 'binding' as "bypassed" It is possible, on the IP -> Hotspot menu, on the settings for the Purple WiFi Hotspot that you set up, to allow clients to bypass the Captive Portal (that is our hotspot service).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |