What steps will reproduce the problem?
1. run zbstumbler against certain products which may use hardware or low-level
802.15.4 beacon response implementations
2. short physical distances to test device seem to raise this issue
3. pcap from zbdump of zbstumbler session will show the real beacon responses,
but these are not caught by zbstumbler fast enough
What is the expected output? What do you see instead?
zbstumbler sometimes does not report the discovered network even when a beacon
responses was elicited.
This could be addressed in two ways:
1. push a function to the firmware to send a given frame and receive the next
frame and return it (also should measure time delta)
2. make a version of zbstumbler that uses two devices, one to send and another
to listen for the beacon responses -- they need to follow eachother across
channels when receiving/transmitting.
Original issue reported on code.google.com by rmspe...@gmail.com on 15 Nov 2011 at 12:08
Original issue reported on code.google.com by
rmspe...@gmail.comon 15 Nov 2011 at 12:08