Mike

These experiences led me to add a warning: ``` $ sudo hcxdumptool -i wlp39s0f3u1u1u1 --check_driver initialization of hcxdumptool 6.2.6-34-g1a4c150 (depending on the capabilities of the device, this may take some...

Also freezes and crashes on aircrack-ng suite in combination with this driver: https://forums.kali.org/showthread.php?56804-AR9271-crashes-Linux

I' testing the changes of $ uname -r 5.18.1-arch1-1 and $ lsusb Bus 005 Device 006: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n That is an old TP-TL-WN722N version 1...

Kernel 5.15.34-1.0-lts seems to work,too. Same interface, Arch Linux 32 bit system, older hcxdumptool (to make sure it isn't related to some changes in hcxdumptool), test AP (a single AP...

From your dmesg log I can see a difference: 5.16.0 is EOL and doesn't get the last ath9k fixes. [ 0.000000] Linux version 5.16.0-kali7-amd64 ([email protected]) (gcc-11 (Debian 11.2.0-19) 11.2.0, GNU...

Unfortunately rtl8812au depend on NL80211 (NETLINK) and the initialization must be done by NETLINK (iw INTERFACE set type monitor). ioctl() calls (CFG80211) to set monitor are not accepted by this...

That is correct. All ioctl() calls are working, except of the first initialization (after plug in of the device), which must be done by: ``` $ sudo ip link set...

Using a strong PSK (63 random characters) or WPA3 is a good idea. It doesn't prevent to be attacked, but it make life much harder for an attacker.

Yes, I mentioned that in README.md: `* hcxdumptool is able to capture handshakes from 5/6GHz clients on 2.4GHz (only one single M2 from the client is required) `

That is history since I published hcxdumptool/hcxtools. https://hashcat.net/forum/thread-6661-post-55540.html#pid55540