Some words about the "Wireless regulatory database for CRDA":
If your device doesn't work, like you expected (not all channels / high not power available), take a look into the wireless regulatory database (crda must be installed):
https://git.kernel.org/pub/scm/linux/ker...xt?id=HEAD
choose a country with less restrictions:
country VE: DFS-FCC
(2402 - 2482 @ 40), (30)
(5170 - 5250 @ 80), (23), AUTO-BW
(5250 - 5330 @ 80), (23), DFS, AUTO-BW
(5735 - 5835 @ 80), (30)
and set it (as super user) on your machine:
$ iw reg set VE
to make it permanent edit (as super user) the config file:
$ nano /etc/conf.d/wireless-regdom
and uncomment this line:
#WIRELESS_REGDOM="VE"
If that doesn't work, the device is firmware coded (like my TL-WN722N). In that case you must patch the firmware to get full access to all channels.
Mostly all(!) issues (hashcat - OpenCL, hcxtools - interfaces) are related to a misconfigured host system (inclusive missing access rights) or driver incompatibility.
I wrote this, because I fell into this trap, like a beginner, due to a kernel upgrade.
I just want to say that: Check your environment after an update/upgrade!
If your device doesn't work, like you expected (not all channels / high not power available), take a look into the wireless regulatory database (crda must be installed):
https://git.kernel.org/pub/scm/linux/ker...xt?id=HEAD
choose a country with less restrictions:
country VE: DFS-FCC
(2402 - 2482 @ 40), (30)
(5170 - 5250 @ 80), (23), AUTO-BW
(5250 - 5330 @ 80), (23), DFS, AUTO-BW
(5735 - 5835 @ 80), (30)
and set it (as super user) on your machine:
$ iw reg set VE
to make it permanent edit (as super user) the config file:
$ nano /etc/conf.d/wireless-regdom
and uncomment this line:
#WIRELESS_REGDOM="VE"
If that doesn't work, the device is firmware coded (like my TL-WN722N). In that case you must patch the firmware to get full access to all channels.
Mostly all(!) issues (hashcat - OpenCL, hcxtools - interfaces) are related to a misconfigured host system (inclusive missing access rights) or driver incompatibility.
I wrote this, because I fell into this trap, like a beginner, due to a kernel upgrade.
I just want to say that: Check your environment after an update/upgrade!