rmspeers / zigbee-security Goto Github PK

zbWarDrive desired improvements:
1. no beacon requests are sent out on channels that are currently being 
monitored
2. if traffic on a channel drops off for a specified (adjustable at cmd line) 
length of time (perhaps default 5 mins, and only if there are no open devices 
and maybe networks are pending), then stop monitoring on a channel and return 
that one to the scan list, opening up the device for use monitoring another 
channel

What steps will reproduce the problem?
1. Only seen by some people (USB driver, bus, and OS issues)
2. More than one supported capture device connected, typically /dev/ttyUSB* 
mounted devices, such as multiple Tmote/TelosB devices running GoodFET firmware.
3. Reflashing the firmware should be tried first.
4. This issue does not cover having unsupported /dev/ttyUSB* devices connected.

One user describes:
"I just confirmed that, when plugged in alone, all the tmotes
would _eventually_ get detected after a series of reflashes
with gf-telosb-001.hex firmware and/or reset button presses. However,
as soon as another USB device is plugged in, all but one get
lost ("Resynching" ad nauseam)."