search

monk-dot / killerbee

Automatically exported from code.google.com/p/killerbee
0 stars 1 forks source link

zbstumbler No output to screen/csv #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Program exit reports responses received.
2. No output to screen or CSV if using -w flag.

Reported by warezjoe and mstelloh.

Initial and related triage by rmspeers:

Based on the devices I have here, it looks like zbstumbler may be
experiencing a timing issue. Aka, it uses RZUSBSTICK to transmit a
beacon request, and then immediately changes to sniffing mode and tries
to get the response. My initial results show that with some hardware,
positioned close especially, it may be missing the response.

To debug, I suggest the following for you:
- add a line of debugging code to zbstumbler on line 72:
print "Received Pkt with FCF=",pktdecode[0].encode('hex'),"- a beacon
response would be 0080"
- reinstall killerbee (python setup.py install)
- start one RZUSBSTICK in zbdump mode (ex sudo zbdump -f 16 -w
zbstumbler.pcap -i 006:003)
- start another RZUSBSTICK in zbstumbler (ex sudo zbstumbler -i 006:005)
- compare zbstumbler output to the pcap, for example, mine prints out:
"Received Pkt with FCF= 4188 - a beacon response would be 0080"
I then see that a frame with FCF 4188 follows the beacon responses, and
with some more debugging, you may be able to verify this is indeed the
specific frame it is seeing, and see what percentage of the time it sees
it after beaconing on that channel, etc.

Original issue reported on code.google.com by rmspe...@gmail.com on 10 May 2012 at 1:20

GoogleCodeExporter commented 9 years ago 
Hello,

I am a Master student of FH Frankfurt an main. I am trying to use killerbee to 
sniff my zigbee motes (there are 6 zigbee motes separated at a distance of 2-5 
meters) programed with atmel bitcloud stack provided by Atmel corp. I installed 
killerbee firmware in one of the AVR RZ Raven USB stick. But when I use the 
zbstumbler command in ubuntu 11.10, I coudn't get any output on the terminal. 
It stops after displaying the following line:

zbstumbler: transmitting and receiving on interface '003:002'

After that if I press ctrl+C it shows the number of packets transmitted but 
their is no response. I would like to know wheather I have to make some changes 
in the zigbee motes or something else i have to do. 

i am attaching a screenshot also.

Original comment by mahatoso...@gmail.com on 22 Jun 2012 at 10:01

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi,

zbstumbler sends IEEE 802.15.4 beacon request frames and expects IEEE
802.15.4 beacon responses. The target of zbstumbler is a IEEE 802.15.4
or ZigBee coordinator device (not endpoint or routers). The issues are
most likely:
- the Atmel bitcloud stack doesn't conform to this part of IEEE
802.15.4, but instead is some proprietary network protocol (I haven't
looked at it yet so don't know)
- less likely: the motes are too close and do very fast beacon sending
which means zbstumbler may not have a fast-enough turn-around time to
sniff the packet the mote sent. Working on a fix to this.

My suggestion at debugging is doing a zbdump on the channel they're
using. If possible, do one zbdump just of the network being set up (like
power up or something), and another zbdump while you're also running
zbstumbler on another device).

Let me know if you have questions.

Original comment by rmspe...@gmail.com on 22 Jun 2012 at 10:41

GoogleCodeExporter commented 9 years ago 
Hi,
thank you very much for the reply.
I found the problem in my zigbee nodes. They are working on 868MHz and the 
communications are carried out at channel 0. So for these reason I think I am 
not able to sniff the information.

Original comment by mahatoso...@gmail.com on 25 Jun 2012 at 9:30

GoogleCodeExporter commented 9 years ago 
mahatosoma17 closes off his issue. The issue appears to be it was not sniffing 
IEEE 802.15.4 compliant transmissions.

Issue remains open per reports from warezjoe and mstelloh. Assistance in 
debugging per my initial post suggestion is appreciated.

Original comment by rmspe...@gmail.com on 26 Jun 2012 at 2:30

GoogleCodeExporter commented 9 years ago 
No responses -- closing issue. Will reopen if people experience these issues -- 
please try my debugging suggestions and the latest version from SVN.

Original comment by rmspe...@gmail.com on 11 Jun 2013 at 12:32