Why deauth does it not work?
The same is with kernel 5.9.6 and driver 5.7.0 ;-(
8812 vs 818b
Yeah, I got the same problem
On these drivers 5.9.3.2 https://github.com/morrownr/8812au deauth works on the 5.4.0-54 kernel.
On these drivers 5.9.3.2 https://github.com/morrownr/8812au deauth works on the 5.4.0-54 kernel.
Thank you @oldstanda. The new driver works like a charm.
To share more context of the issue: I wasn't able to conduct a deauth attack with the v5.6.4.2 driver on my AWUS036ACH. I was testing on Kali with 5.8.0-kali2-amd64 kernel.
More specifically, the symptom was:
aireplay-ng -0 returned with no error, but with little ACKs (0 to 3 ACKs per 64 requests)After installing the v5.9.3.2 driver:
# aireplay-ng -0 1 -a xxxx -c yyyy wlan0
09:04:30 Waiting for beacon frame (BSSID: xxxx) on channel 2
09:04:31 Sending 64 directed DeAuth (code 7). STMAC: [yyyy] [19|55 ACKs]
# xxd deauth-failed.pcap
00000000: d4c3 b2a1 0200 0400 0000 0000 0000 0000 ................
00000010: ffff 0000 6900 0000 c963 cf5f 43e8 0400 ....i....c._C...
00000020: 1a00 0000 1a00 0000 c000 3a01 f018 9854 ..........:....T
00000030: e6b4 1062 eb21 7d25 1062 eb21 7d25 0000 ...b.!}%.b.!}%..
00000040: 0700 ..
# xxd deauth-success.pcap
00000000: d4c3 b2a1 0200 0400 0000 0000 0000 0000 ................
00000010: ffff 0000 6900 0000 ee87 cf5f 3c5a 0c00 ....i......_<Z..
00000020: 1a00 0000 1a00 0000 c000 3a01 f018 9854 ..........:....T
00000030: e6b4 1062 eb21 7d25 1062 eb21 7d25 0000 ...b.!}%.b.!}%..
00000040: 0700 ..
Most helpful comment
On these drivers 5.9.3.2 https://github.com/morrownr/8812au deauth works on the 5.4.0-54 kernel.