hcxdumptool: Possible regression with commit 0b9aaad

I am running hcxdumptool on RaspberryPi Zero 2 with Alfa AWUS036ACM. I built the tool from the latest source (commit 20031ae) and when I run it like this:

$ sudo hcxdumptool -i wlan1 -o all.pcapng --enable_status=31

once in a while I am getting these errors:

14:19:44 2427/4 driver is busy/broken: failed to transmit associationrequest
14:19:44 2427/4 driver is busy/broken: failed to transmit associationrequest
14:19:45 2427/4 driver is busy/broken: failed to transmit associationrequest
14:19:45 2427/4 driver is busy/broken: failed to transmit associationrequest

The tool appears to be working but I was curious to find out what is causing these errors and rolled back to version 6.2.6 (commit 2b711d6). With this version I didn’t get any errors for very long period of time. So I did a binary search and I found these errors start to appear with commit 0b9aaad. Unfortunately I don’t understand the code enough to troubleshoot further.

Are these errors false positive or indicate an actual problem?

This is the kernel version:

$ uname -a
Linux raspberrypi 5.15.32-v7+ #1538 SMP Thu Mar 31 19:38:48 BST 2022 armv7l GNU/Linux

If you need any other info, I’d be happy to provide it.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 17 (11 by maintainers)

Most upvoted comments

I think I got it. Please try latest commit.

Running active monitor mode in transmission branch increased traffic 7 times. Now we are running a TX timeout of 1 second, which should be enough for the device to transmit all packets before we’re doing a new request. The device shouldn’t report “busy” any longer.

BTW: By the commit before, I eliminated the warning about deprecated openssl API.