Aircrack-ng forum

I have the same problem with my two Alfa AWUS036ACHM cards. I've updated aircrack to 1.7 but it seems that aireplay can't deauth 5ghz band

Updated to aircrack 1.7 and followed all the steps above in running the deauth again. I also set my router to 802.11ac and now im about 10 feet away from my router. Despite this Im still getting the exact same results. Im getting barely any ACKS on my 5ghz AP.

┌──(kali㉿kali)-[~]
└─$ sudo aireplay-ng --deauth 0 -a 24:F5:A2:04:9B:34 -c B0:73:5D:D2:D9:5D wlan0mon
22:36:24  Waiting for beacon frame (BSSID: 24:F5:A2:04:9B:34) on channel 157
22:36:25  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
22:36:25  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
22:36:26  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 1 ACKs]
22:36:27  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 1 ACKs]
22:36:27  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 2 ACKs]
22:36:27  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
22:36:28  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
22:36:29  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 2 ACKs]
22:36:30  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 1 ACKs]
22:36:31  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 5 ACKs]
22:36:31  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 3 ACKs]
22:36:32  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 1| 3 ACKs]
22:36:33  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 6 ACKs]
22:36:33  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 3 ACKs]

But significantly more ACKs on my 2.4ghz AP,

┌──(kali㉿kali)-[~]
└─$ sudo aireplay-ng --deauth 0 -a 24:F5:A2:04:9B:33 -c B0:73:5D:D2:D9:5D wlan0mon
22:40:47  Waiting for beacon frame (BSSID: 24:F5:A2:04:9B:33) on channel 7
22:40:47  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [62|65 ACKs]
22:40:48  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [19|62 ACKs]
22:40:48  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [32|67 ACKs]
22:40:49  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [66|69 ACKs]
22:40:50  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [63|66 ACKs]
22:40:51  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 4|64 ACKs]
22:40:51  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0|64 ACKs]
22:40:52  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0|62 ACKs]
22:40:52  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 3|66 ACKs]
22:40:53  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0|64 ACKs]
22:40:54  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0|65 ACKs]
22:40:54  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [46|63 ACKs]
22:40:55  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [66|69 ACKs]
22:40:56  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [66|68 ACKs]
22:40:56  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 4|63 ACKs]
22:40:57  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0|64 ACKs]
22:40:58  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 1|62 ACKs]
22:40:5^C Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 4|27 ACKs]

I then decided to just test if packet injection in general is working. For my 5ghz AP packet injection for some reason is not working at all

┌──(kali㉿kali)-[~]
└─$ sudo iwconfig wlan0mon channel 157
                                                                                                                   
┌──(kali㉿kali)-[~]
└─$ sudo aireplay-ng --test wlan0mon 
22:50:50  Trying broadcast probe requests...
22:50:52  No Answer...
22:50:52  Found 1 AP

22:50:52  Trying directed probe requests...
22:50:52  24:F5:A2:04:9B:34 - channel: 157 - '5GHz'
22:50:58   0/30:   0%

But on the other hand when running the test on my 2.4ghz AP it works fine

┌──(kali㉿kali)-[~]
└─$ sudo aireplay-ng --test wlan0mon
22:52:37  Trying broadcast probe requests...
22:52:37  Injection is working!
22:52:39  Found 3 APs

22:52:39  Trying directed probe requests...
22:52:39  24:F5:A2:04:9B:33 - channel: 7 - '2.4GHz'
22:52:42  Ping (min/avg/max): 21.575ms/51.449ms/158.056ms Power: -20.60
22:52:42  20/30:  66%

22:52:42  14:EB:B6:05:F2:AB - channel: 7 - 'Redacted'
22:52:47  Ping (min/avg/max): 8.803ms/35.619ms/77.291ms Power: -69.67
22:52:47   6/30:  20%

22:52:47  CC:D4:2E:67:E5:B8 - channel: 7 - 'Redacted'
22:52:53   0/30:   0%

Why isnt packet injection working on 5ghz band?

It should be 'os=any dist=any'.

It works fine on Ubuntu, but on Kali, for some reason it doesn't see 1.7 as higher than 1.6.
For the time being, download the deb, and install with dpkg: dpkg -i aircrack-ng_1.7-1_amd64.deb)

Hi yes you are correct I am still on aircrack 1.6. I tried installing the latest version from packagecloud but am having difficulty getting it to work. From the aircrack installation instructions I went to the packagecloud site (https://packagecloud.io/aircrack-ng/release/packages/any/any/aircrack-ng_1.7-1_amd64.deb) and ran the first command. Apparently kali is not supported so I cant get the package installation to work.

┌──(kali㉿kali)-[~/Downloads]
└─$ curl -s https://packagecloud.io/install/repositories/aircrack-ng/release/script.deb.sh | sudo bash
Detected operating system as kali/kali-rolling.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/aircrack-ng_release.list...curl: (22) The requested URL returned error: 404


Unable to download repo config from: https://packagecloud.io/install/repositories/aircrack-ng/release/config_file.list?os=kali&dist=kali-rolling&source=script

This usually happens if your operating system is not supported by
packagecloud.io, or this script's OS detection failed.

You can override the OS detection by setting os= and dist= prior to running this script.
You can find a list of supported OSes and distributions on our website: https://packagecloud.io/docs#os_distro_version

For example, to force Ubuntu Trusty: os=ubuntu dist=trusty ./script.sh

If you are running a supported OS, please email support@packagecloud.io and report this.

I decided then to attempt to overwrite the os and dist settings. I loosely remember kali being based off debian 8 or 7? The repo set up seems to work but kali cant seem to find aircrack 1.7

┌──(kali㉿kali)-[~/Downloads]
└─$ curl -s https://packagecloud.io/install/repositories/aircrack-ng/release/script.deb.sh >> install.sh
                                                                                                                                                                                                                                           
┌──(kali㉿kali)-[~/Downloads]
└─$ chmod +x install.sh                                                                                 

┌──(kali㉿kali)-[~/Downloads]
└─$ sudo os=debian dist=jessie ./install.sh
Detected operating system as debian/jessie.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing debian-archive-keyring which is needed for installing
apt-transport-https on many Debian systems.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/aircrack-ng_release.list...done.
Importing packagecloud gpg key... done.
Running apt-get update... done.

The repository is setup! You can now install packages.
Detected operating system as debian/jessie.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing debian-archive-keyring which is needed for installing
apt-transport-https on many Debian systems.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/aircrack-ng_release.list...done.
Importing packagecloud gpg key... done.
Running apt-get update... done.

The repository is setup! You can now install packages.

┌──(kali㉿kali)-[~/Downloads]
└─$ sudo apt-get install aircrack-ng=1:1.7-1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package aircrack-ng is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '1:1.7-1' for 'aircrack-ng' was not found

What am I doing wrong here?

Kali still has aircrack-ng 1.6 despite 1.7 being released for a few months. I know there was some bug about 5GHz in 1.6, but I don't recall when it was exactly fixed.

So, you can compile and install from sources (or use our packages), then try again, and report back.

Installation is explained in the wiki (from sources) and the README.md file, and also in the blog (for the packages).

Three suggestions:
- Run airmon-ng check kill prior to putting the card in monitor mode, as it can interfere with airodump-ng as well.
- Don't be too close, as it's as bad as being too far, and leads to packet loss. Try something like 10 feet.
- Make sure your AP is set to 802.11ac (and not 11ax).

I recently got the aircrack-ng recommended dual band Alfa AWUS036ACM card. The card works fine for packet sniffing on both 5ghz and 2.4ghz networks but it seems to only be able to deauth over 2.4ghz but not 5ghz networks, the deauthing works flawlessly over 2.4ghz but is very inconsistent over 5ghz. Here are the results I got on my 2.4ghz network

┌──(kali㉿kali)-[~]
└─$ sudo aireplay-ng --deauth 0 -a 24:F5:A2:04:9B:33 -c B0:73:5D:D2:D9:5D wlan0mon
10:57:14  Waiting for beacon frame (BSSID: 24:F5:A2:04:9B:33) on channel 7
10:57:15  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [53|63 ACKs]
10:57:16  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 5|64 ACKs]
10:57:16  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [66|67 ACKs]
10:57:17  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [63|63 ACKs]
10:57:18  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [66|65 ACKs]
10:57:18  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [63|64 ACKs]
10:57:19  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [60|63 ACKs]
10:57:19  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [65|65 ACKs]
10:57:20  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [48|46 ACKs]
10:57:20  Sending 64 directed DeAuth (code 7). ^CMAC: [B0:73:5D:D2:D9:5D] [11|11 ACKs]

This is what I expect to see and sure enough my client is disconnected from the AP. However when I try to deauth on my 5ghz AP this is what I get instead.

┌──(kali㉿kali)-[~]
└─$ sudo aireplay-ng --deauth 0 -a 24:F5:A2:04:9B:34 -c B0:73:5D:D2:D9:5D wlan0mon
11:23:00  Waiting for beacon frame (BSSID: 24:F5:A2:04:9B:34) on channel 157
11:23:00  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:01  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:02  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:02  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:03  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 1 ACKs]
11:23:03  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:04  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:04  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:05  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:06  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:07  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 1 ACKs]
11:23:07  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 2 ACKs]
11:23:08  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 2 ACKs]
11:23:08  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 1 ACKs]
11:23:09  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 1| 1 ACKs]
11:23:09  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:10  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:11  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:12  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 0 ACKs]
11:23:12  Sending 64 directed DeAuth (code 7). STMAC: [B0:73:5D:D2:D9:5D] [ 0| 2 ACKs]
^C

For some reason Im getting significantly much less ACKS from both my AP and my client when running a deauth on my 5ghz AP and my client remains connected to the network. Some additional info

- Im running a kali 2022.3 VM on virtualbox on a windows 10 host
- Im not using any custom specific linux drivers, I heard AWUS036ACM was plug and play, and kali detected the card out of the box for me so I didnt install anything
- Im on the latest version of aircrack, Ive additionally ran apt update and apt dist-upgrade
- I ran airmon-ng check kill prior to the deauth and the interface is confirmed to already be in monitor mode
- I double and triple checked that the AP BSSID and my clients MAC have been typed in correctly so no chance of a typo there
- Everything is being ran as root
- My network card is on the same 5ghz channel as the AP that Im trying to deauth, I set its channel using the "iwconfig wlan0mon channel" command
- My AP and my client are both in range of my network card, im sitting a few feet away from my AP and my client (which is my phone) is right next to my network card. I know being next to the AP usually decreases transmission but this decrease seems far too drastic and moving away from it does not increase the ACKS I get

Any reason why this is the case? How can I get deauthing to work on 5ghz?

I have been using these Linux drivers with all my pen test distro's, Debian based like Kali and Parrot, Arch based like BlackArch, RPM based like Fedora security spin distro..

They will of course compile and work with any Linux distro if you are just adding tools to your own Linux system.

They work as expected with monitor mode and packet injection and because they are dkms compiled drivers, they will automatically update whenever you update your system or kernel.

https://github.com/morrownr

For some attacks you actually need 2 adapters, you have to use 1 to masquerade as the access point, and another to be able to de-authenticate the clients of the real AP to try and get them to connect to your twin.

Buy another adapter!

Use a good adpater and attach a larger higher gain aerial to it.

Attackable depends on how their set up..

Hello.  I want to use airodump-ng to scan the Wi-Fis around me, is there a way to increase the range of available Wi-Fis?
I hope the translator translated well.