02-23-2020, 11:06 AM
Hi ciccio17. Thanks, I'm fine. You too?
This is my test environment:
Arch Linux x86 (archlinux-2020.02.01-x86_64) hcxdumptool, hcxtools, hashcat, JtR
$ uname -r
5.5.5-arch1-1
Arch Linux Arm (ArchLinuxARM-rpi-latest) hcxdumptool, hcxtools
$ uname -r
4.19.102-1-ARCH
Regarding Kernel 5.5.5 many issues are still unsolved:
https://bugzilla.kernel.org/show_bug.cgi?id=202541 -> mostly USB3.0 related, mostly on AMD RYZEN systems
as well as most of the ath9k issues
https://bugzilla.kernel.org/buglist.cgi?...earch=ath9
https://bugs.openwrt.org/index.php?do=de...=&closedto=
As of today, I only use/test devices running mt76 and rt2800usb driver. Both chipsets running fine and out of the box on Raspberry PI A, B, A+, B+, Zero and x86 systems. The maintainers of this drivers are doing an excellent good job!
I won't do any more tests and I will not carry out any further optimizations (hcxdumptool) on other drivers unless they are fixed. That includes the Broadcom chipset (Raspberry's onboard SOC) because the native driver doesn't support monitor mode and packet injection.
ath9k_htc log (as of today):
I used your last git on kernel 4.19 and is totally a different tool for me
-> hcxdumptool refactoring is in progress. Next version will get a different look. I noticed that the RPI drops packets when the system is busy (real time display). So we have to reduce this output to a minimum.
Latest git head of hashcat and hcxdumptool contain a lot of new features. It is a good idea to test them.
This is my test environment:
Arch Linux x86 (archlinux-2020.02.01-x86_64) hcxdumptool, hcxtools, hashcat, JtR
$ uname -r
5.5.5-arch1-1
Arch Linux Arm (ArchLinuxARM-rpi-latest) hcxdumptool, hcxtools
$ uname -r
4.19.102-1-ARCH
Regarding Kernel 5.5.5 many issues are still unsolved:
https://bugzilla.kernel.org/show_bug.cgi?id=202541 -> mostly USB3.0 related, mostly on AMD RYZEN systems
as well as most of the ath9k issues
https://bugzilla.kernel.org/buglist.cgi?...earch=ath9
https://bugs.openwrt.org/index.php?do=de...=&closedto=
As of today, I only use/test devices running mt76 and rt2800usb driver. Both chipsets running fine and out of the box on Raspberry PI A, B, A+, B+, Zero and x86 systems. The maintainers of this drivers are doing an excellent good job!
I won't do any more tests and I will not carry out any further optimizations (hcxdumptool) on other drivers unless they are fixed. That includes the Broadcom chipset (Raspberry's onboard SOC) because the native driver doesn't support monitor mode and packet injection.
ath9k_htc log (as of today):
Code:
$ hcxdumptool -v
hcxdumptool 6.0.1 (C) 2020 ZeroBeat
$ hcxdumptool -I
wlan interfaces:
f81a67027a1f wlp39s0f3u3u1u2 (ath9k_htc)
$ sudo hcxdumptool -i wlp39s0f3u3u1u2 --enable_status=127
initialization...
start capturing (stop with ctrl+c)
NMEA 0183 SENTENCE........: N/A
INTERFACE NAME............: wlp39s0f3u3u1u2
INTERFACE HARDWARE MAC....: f81a67027a1f
DRIVER....................: ath9k_htc
DRIVER VERSION............: 5.5.5-arch1-1
DRIVER FIRMWARE VERSION...: 1.4
ERRORMAX..................: 100 errors
FILTERLIST ACCESS POINT...: 0 entries
FILTERLIST CLIENT.........: 0 entries
FILTERMODE................: 0
WEAK CANDIDATE............: 12345678
PREDEFINED ACCESS POINT...: 0 entries
MAC ACCESS POINT BROADCAST: 0084ed5b1df6
MAC ACCESS POINT..........: 0084ed5b1df7 (incremented on every new client)
MAC CLIENT................: e00db95be6ae
REPLAYCOUNT...............: 61893
ANONCE....................: b0b4a53cddc62c8901bc67bd2f044517bbced62f55d432a810d6745be337e79f
SNONCE....................: b2580bcdc99fbb28b2238e634f1309f64ce10c35f601ddb3657794235f29cd24
...
09:45:00 12 INFO ERROR:0 INCOMING:2026 OUTGOING:301 PMKID:32 MP:0 GPS:0 RINGBUFFER:10
$ dmesg
[ 1732.644558] usb 5-3.1.2: Product: USB2.0 WLAN
[ 1732.644560] usb 5-3.1.2: Manufacturer: ATHEROS
[ 1732.644562] usb 5-3.1.2: SerialNumber: 12345
[ 1732.846948] usb 5-3.1.2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[ 1732.847000] usbcore: registered new interface driver ath9k_htc
[ 1733.143466] usb 5-3.1.2: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[ 1733.393997] ath9k_htc 5-3.1.2:1.0: ath9k_htc: HTC initialized with 33 credits
[ 1733.630748] ath9k_htc 5-3.1.2:1.0: ath9k_htc: FW Version: 1.4
[ 1733.630751] ath9k_htc 5-3.1.2:1.0: FW RMW support: On
[ 1733.630752] ath: EEPROM regdomain: 0x809c
[ 1733.630753] ath: EEPROM indicates we should expect a country code
[ 1733.630754] ath: doing EEPROM country->regdmn map search
[ 1733.630755] ath: country maps to regdmn code: 0x52
[ 1733.630756] ath: Country alpha2 being used: CN
[ 1733.630757] ath: Regpair used: 0x52
[ 1733.634523] ieee80211 phy0: Atheros AR9271 Rev:1
[ 1733.638888] ath9k_htc 5-3.1.2:1.0 wlp39s0f3u3u1u2: renamed from wlan0
[ 1768.128502] device wlp39s0f3u3u1u2 entered promiscuous mode
...
ath: phy0: Short RX data len, dropping (dlen: 8)
...
I used your last git on kernel 4.19 and is totally a different tool for me
-> hcxdumptool refactoring is in progress. Next version will get a different look. I noticed that the RPI drops packets when the system is busy (real time display). So we have to reduce this output to a minimum.
Latest git head of hashcat and hcxdumptool contain a lot of new features. It is a good idea to test them.