I saw people using Wlandump instead hcxdumptool.. any difference on the output?
wlandump-ng is the predecessor of hcxdumptool. It has less functions and it depend on libpcap. That make it slow.
hcxdumptool doesn't depend on libnl, libpcap, wiringpi and other wrappers. That will make it fast.
Could be possible to create a minimal raspberry distro just for hcxtools and access via ssh only?
Yes. This is a backup of my headless system, controlled via ssh:
$ ls -All
total 477912
-rw-r--r-- 1 root root 21043310 5. Jun 17:41 rpiboot.tgz
-rw-r--r-- 1 root root 468330646 5. Jun 17:43 rpiroot.tgz
from this base system:
ArchLinuxARM-rpi-latest.tar.gz 02-Jun-2019 17:47 43059753
No, beautiful GUI, no unnecessary tools - only speed!
BTW:
The gz files doesn't contain images. I don't like the idea to backup a system by "dd".
wlandump-ng is the predecessor of hcxdumptool. It has less functions and it depend on libpcap. That make it slow.
hcxdumptool doesn't depend on libnl, libpcap, wiringpi and other wrappers. That will make it fast.
Could be possible to create a minimal raspberry distro just for hcxtools and access via ssh only?
Yes. This is a backup of my headless system, controlled via ssh:
$ ls -All
total 477912
-rw-r--r-- 1 root root 21043310 5. Jun 17:41 rpiboot.tgz
-rw-r--r-- 1 root root 468330646 5. Jun 17:43 rpiroot.tgz
from this base system:
ArchLinuxARM-rpi-latest.tar.gz 02-Jun-2019 17:47 43059753
No, beautiful GUI, no unnecessary tools - only speed!
BTW:
The gz files doesn't contain images. I don't like the idea to backup a system by "dd".