The installer will confirm your hard disk, select Install. Enter your Mac password, then select Add Helper. The macOS installer will download more files to complete the install. Mac Level Filter Callout has 1 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more! Please help add to this by sharing more! Deployment Tips (0).
ContentsIntroduction
This document explains how to configure MAC filters with wireless LAN controllers (WLCs) with a configuration example. This document also discusses how to authorize lightweight access points (LAPs) against an AAA server.
PrerequisitesRequirements
Ensure that you meet these requirements before you attempt this configuration:
Components Used
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
MAC Address Filter (MAC Authentication) 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.
There are two types of MAC authentication that are supported on WLCs:
With local MAC authentication, user MAC addresses are stored in a database on the WLC. 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.
By default, the WLC local database supports up to 512 user entries.
The local user database is limited to a maximum of 2048 entries. The local database stores entries for these items:
Mac Filter Callout Installer Download Filehippo
Together, all of these types of users cannot exceed the configured database size.
In order to increase the local database, use this command from the CLI:
Alternatively, MAC address authentication can also be performed using a RADIUS server. The only difference is that the users MAC address database is stored in the RADIUS server instead of the WLC. When a user database is stored on a RADIUS server the WLC forwards the MAC address of the client to the RADIUS server for client validation. Then, the RADIUS server validates the MAC address based on the database it has. If the client authentication is successful, the client is granted access to the WLAN. Any RADIUS server which supports MAC address authentication can be used.
Configure Local MAC Authentication on WLCs
Complete these steps in order to configure local MAC authentication on the WLCs:
Configure a WLAN and Enable MAC FilteringMac Filter Callout Installer Downloads
Complete these steps in order to configure a WLAN with MAC filtering:
The next step is to configure the local database on the WLC with the client MAC addresses.
Refer to VLANs on Wireless LAN Controllers Configuration Example for information on how to configure dynamic interfaces (VLANs) on WLCs.
Configure the Local Database on the WLC with Client MAC Addresses
Complete these steps in order to configure the local database with a client MAC address on the WLC:
Configure MAC Authentication using a RADIUS Server
Complete these steps in order to configure MAC authentication using a RADIUS server. In this example, the Cisco Secure ACS server is used as the RADIUS server.
Configure a WLAN and Enable MAC Filtering
Complete these steps in order to configure a WLAN with MAC filtering:
The next step is to configure the ACS server with the client MAC addresses.
Configure the RADIUS Server with Client MAC Addresses
Complete these steps in order to add a MAC address to the ACS:
Use the CLI to Configure the MAC Filter on WLC
This document previously discussed how to use the WLC GUI to configure MAC filters. You can also use the CLI in order to configure MAC filters on the WLC. You can use these commands in order to configure the MAC filter on WLC:
Configure a Timeout for Disabled Clients
You can configure a timeout for disabled clients. Clients who fail to authenticate three times during attempts to associate are automatically disabled from further association attempts. After the timeout period expires, the client is allowed to retry authentication until it associates or fails authentication and is excluded again.
Enter the config wlan exclusionlist wlan_id timeout command in order to configure the timeout for disabled clients. The timeout value can be from 1 to 65535 seconds, or you can enter 0 in order to permanently disable the client.
Verify
Use these commands in order to verify if the MAC filter is configured correctly:
Mac Filter Callout Installer Download Windows 7
The Output Interpreter Tool (registered customers only) (OIT) supports certain show commands. Use the OIT to view an analysis of show command output.
Here is an example of the show macfilter summary command:
Here is an example of the show macfilter detail command:
Troubleshoot
You can use these commands to troubleshoot your configuration:
Note: Refer to Important Information on Debug Commands before you use debug commands.
Here is an example of the debug aaa all enable command:
When a wireless client is not present in the MAC address database on the WLC (local database) or on the RADIUS server tries to associate to the WLAN, that client will be excluded. Here is an example of the debug aaa all enable command for an unsuccessful MAC authentication:
Wireless Clients that Try to Authenticate by MAC Address are Rejected; Failed Authentication Report Shows Internal Errors
When you use ACS 4.1 that runs on a Microsoft Windows 2003 Enterprise server, clients that try to authenticate by the MAC address are rejected. This occurs when an AAA client sends the Service-Type=10 attribute value to the AAA server. This is because of Cisco bug ID CSCsh62641 (registered customers only) . AAA clients affected by this bug include WLCs and switches that use MAC Authentication Bypass.
The workarounds are:
Not able to add a MAC filter using the WLC GUI
This can happen becaue of the Cisco bug ID CSCsj98722 (registered customers only) . The bug is fixed in 4.2 release of code. If you are running versions earlier than 4.2, you can upgrade the firmware to 4.2 or use these two workarounds for this issue.
Silent client not placed in run state
If DHCP required is not configured on the controller, the APs learn the IP address of wireless clients when the wireless clients send out the first IP packet or ARP. If the wireless clients are passive devices, for example, devices that do not initiate a communication, then the APs fails to learn the IP address of the wireless devices. As a result, the controller waits ten seconds for the client to send an IP packet. If there is no response from the packet from the client, then the controller drops any packets to the passive wireless clients. This issue is documented in Cisco bug ID CSCsq46427 (registered customers only)
As a recommended workaround for passive devices like printers, wireless PLC pumps and so forth, you need to set the WLAN for MAC filtering and have AAA override checked in order to allow these devices to be connected.
A MAC address filter can be created on the controller that maps the MAC address of the wireless device to an IP address.
Note: This requires MAC address filtering to be enabled on the WLAN configuration for Layer 2 Security. It also requires Allow AAA Overide to be enabled in the advance settings of the WLAN configuration.
From the CLI, enter this command in order to create the MAC address filter:
Here is an example:
Related Information
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |