Aircrack-ng
Posted: Mon 31 Oct 31 2016 8:24 pm
1. Ensure the correct chipset is being used - best bet in SG - TP-LINK TL-WN722N
2. Install Aircrack-ng
3. Insert "blacklist wmi" into /etc/modprobe.d/blacklist.conf
- uncertain if this helps anything
4. run "ifconfig -a"
- ascertain interface name
- in my case it wasn't "wlan0" as documents suggest
- it was "wlx18a670d5c25"
5. After starting "sudo airmon-ng start wlx18a670d5c25"
- you might get a message or two asking you to:-
a) sudo airmon-ng check kill
- do this to kill interfering processes
- it is uncertain if this will have any side effect on wpa supplicant functions
b) sudo rfkill unblock the interface name
- however, this is an incorrect instruction
- the correct way is to run "sudo rfkill list" and see which interface is blocked
- then using the NUMBER of the interface, run "sudo rfkill unblock 4" for example
- do this for all blocked interfaces, just to be safe
6. After the last step, the interface "wlx18a670d5c25" will have disappeared from the "ifconfig -a" list
- it is replaced by "wlan0mon" rather than the "mon0" as suggested by documentation
7. run "sudo airmon-ng start wlan0mon"
- this brings up a realtime updated list of beacons received
2. Install Aircrack-ng
3. Insert "blacklist wmi" into /etc/modprobe.d/blacklist.conf
- uncertain if this helps anything
4. run "ifconfig -a"
- ascertain interface name
- in my case it wasn't "wlan0" as documents suggest
- it was "wlx18a670d5c25"
5. After starting "sudo airmon-ng start wlx18a670d5c25"
- you might get a message or two asking you to:-
a) sudo airmon-ng check kill
- do this to kill interfering processes
- it is uncertain if this will have any side effect on wpa supplicant functions
b) sudo rfkill unblock the interface name
- however, this is an incorrect instruction
- the correct way is to run "sudo rfkill list" and see which interface is blocked
- then using the NUMBER of the interface, run "sudo rfkill unblock 4" for example
- do this for all blocked interfaces, just to be safe
6. After the last step, the interface "wlx18a670d5c25" will have disappeared from the "ifconfig -a" list
- it is replaced by "wlan0mon" rather than the "mon0" as suggested by documentation
7. run "sudo airmon-ng start wlan0mon"
- this brings up a realtime updated list of beacons received