06-09-2019, 10:36 PM
No, hcxdumptool running own monitor mode.
Just stop all tasks which take access to the device and than run hcxdumptool. If you forgot one task, hcxdumptool will tell you that.
airmon-ng running iw. Sometimes iw creates an interface (netlink), which hcxdumptool doesn't like. To get full advantage, hcxdumptool need full access to the physical device. It control the device running ioctl() commands. That is very fast.
Read more here:
https://www.quora.com/What-are-the-diffe...octl-calls
especially this parts here:
"Netlink messages can be lost for various reasons (e.g. out of memory), while ioctls are generally more reliable due to their immediate-processing nature."
"Control: ioctl should be your first choice, unless there’s an overriding reason, due to its immediacy and reliable delivery."
I fully agree with this!
Just stop all tasks which take access to the device and than run hcxdumptool. If you forgot one task, hcxdumptool will tell you that.
airmon-ng running iw. Sometimes iw creates an interface (netlink), which hcxdumptool doesn't like. To get full advantage, hcxdumptool need full access to the physical device. It control the device running ioctl() commands. That is very fast.
Read more here:
https://www.quora.com/What-are-the-diffe...octl-calls
especially this parts here:
"Netlink messages can be lost for various reasons (e.g. out of memory), while ioctls are generally more reliable due to their immediate-processing nature."
"Control: ioctl should be your first choice, unless there’s an overriding reason, due to its immediacy and reliable delivery."
I fully agree with this!