Hey Friends, Welcome to Hackingloops. Today we will learn how to bypass MAC Address Filtering on Wireless Networks. MAC Filtering or MAC Whitelist or Blacklist is an security option provided in most routers to allow or restrict particular MAC Address to allow access or restrict the Internet. If this setting is enabled then only the Machines which are allowed by MAC Filtering can use a particular Access Point. Today we will learn how to bypass MAC Filtering on Wireless Network Routers.
1- Simple way change: this will change your mac simply, wont reflect in wifi settings, you may not connect to secured password protected networks. This function mostly works with most users. 2- Hard way change: Now you will see the fake mac address in wifi settings, you can connect to secured password protected networks. Secure your Wifi connection with MAC Filtering/ Access Control Have you ever been caugt in a situation where your wifi routers security is compromised or som. If you would like to limit which computers can access the Internet through the router,you can set MAC Filtering to achieve it. Step 1 You should know the MAC addresses of the computers which you would like to allow them to access the Internet.You can check them on the computers with command prompt. (1)Click Start-Run, type cmd and press Enter. (2) Type ipconfig/all at the prompt window.
Most of people are aware what MAC Address is but let me brief all to revise basics. MAC Address stands for Media Access Control Address and is a unique identifier assigned to all network interfaces. With MAC filtering you can specify MAC addresses which are allowed or not allowed to connect to the network. For many occasions this might be sufficient as a security measure which makes it a little harder to use the network when the password is even known to users. So let’s start our tutorial on how to bypass MAC Address Filtering by spoofing MAC Address.
Hacking Wireless Networks bypassing MAC Address Filtering
Steps to Bypass MAC Address Filtering on Wireless Routers :
How to set MAC filtering in netgear router.
Step 1 : Consider that we have router which has MAC Filtering Configured. Say AA-BB-00-11-22 is an MAC Address which is white listed in MAC Filtering to use the Wireless Network.
Step 2 : Let’s login into our KALI Linux Machine and Put the Particular WIFI Adapter into Monitoring mode using AIRMON-ng, this can be done by typing below command at terminal:
airmon-ng start wlan0
Step 3 : Now it may happen some KALI Linux Process is showing some error. If yes then kill the process which KALI Linux is reporting having issues, it can be done using below command:
kill [pid]
Step 4 : Now launch Airodump-ng to locate the wireless network and the connected client(s) using the following command:
airodump-ng –c [channel] –bssid [target router MAC Address] –i wlan0mon
Airodump-ng now shows us a list of all connected clients at the bottom of the terminal. The second column lists the MAC Addresses of the connected client which we will be spoofing in order to authenticate with the wireless network.
Note: You will get above list only when someone is connected to that Wireless Network already, else you will get a empty list.
Step 5 : Now we have the MAC Address, Let’s use the MacChanger to Spoof the MAC Address :
Let’s spoof the MAC address of your wireless adapter but first we take need to take down the monitoring interface wlan0mon and the wlan0 interface in order to change the MAC address. We can do this by using the following command:
Airmon-ng stop wlan0mon
Step 6 : Now we take down the wireless interface who’s MAC address we want to spoof with the following command:
ifconfig wlan0 down
Step 7 : Now we can use Macchanger to change the MAC address:
macchanger -m [New MAC Address] wlan0
And bring it up again:
ifconfig wlan0 up
Now that we have changed the MAC address of our wireless adapter to a white listed MAC address in the router we can try to authenticate with the network and see if we’re able to connect.
That’s it Guys! Now You are able to connect to network. Now in most cases Wireless Networks are also password protected, to hack that you can use earlier methods that i have explained in earlier tutorials.
Keep Learning!! Keep Connected!!
![]() 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:
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:
Wifi Mac Filter App ShortcutConfigure 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 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
Mac open app with shortcut. 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
Macos document based app. Complete these steps in order to configure a WLAN with MAC filtering:
Wifi Mac Filter App Download
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:
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:
Mac Address Filtering Wifi
Wireless Clients that Try to Authenticate by MAC Address are Rejected; Failed Authentication Report Shows Internal Errors
Mac Filter App Wifi Hotspot
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.
Google Wifi Mac Filtering
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:
Wifi Mac Filter App InstallerRelated InformationComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |