Closed GoogleCodeExporter closed 8 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:
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
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
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
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
Original issue reported on code.google.com by
rmspe...@gmail.com
on 10 May 2012 at 1:20