Stopping any of the scan/sniff scripts requires the usb device to be reset most of the times

[PlasmaHH]

I am trying to write a scanner based on this to figure out if we have vulnerable devices in the company and then decommission them.

I have successfully installed the firmware on a logitech unifying dongle and now trying to scan, which works ok, but almost every time I cancel the script and start it again I get timeout errors from the usb library until I reset the USB device.

Could this be that while it is in (pseudo) promiscious mode it can't be initialized/enter it again? And that it would make sense to have a "reset" command for the driver to properly put it into the state it has after powering on, and call that command upon any kind of exit from the scripts?

[khmann]

I've spent some time with this is a different context (I only transmit) and it's definitely a library/firmware "USB problem" not a "radio problem" - everything with the dongle is polled and if your os/app doesn't properly accept the USB result packet of the command, the dongle gets stuck.

It's seems possible if you added an on-exit handler to your script to do something benign like change the channel (and read the response packet) you could work around the problem but I've not gotten anywhere with it.