search

monk-dot / killerbee

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

Error when attempting to run KillerBee on Kali Linux #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Hello, I'm attempting to run KillerBee on Kali Linux but get an error when I 
run zbstumbler.  I'm using Atmel RZUSBSTICKs.

xyz@kaliLinux:~$ sudo zbstumbler
Traceback (most recent call last):
  File "/usr/bin/zbstumbler", line 154, in <module>
    kb = KillerBee(device=arg_devstring)
  File "/usr/lib/pymodules/python2.7/killerbee/__init__.py", line 148, in __init__
    self.__handle_open()
  File "/usr/lib/pymodules/python2.7/killerbee/__init__.py", line 449, in __handle_open
    raise Exception("Unable to open device.  Ensure the device is free and plugged-in.")
Exception: Unable to open device.  Ensure the device is free and plugged-in.

It's like the OS doesn't see the Raven.  With that in mind I did a dmesg and 
the OS can see the device connected. 

[ 1736.578368] usb 2-1.4: USB disconnect, device number 7
[ 1811.399225] usb 2-1.2: USB disconnect, device number 8
[ 1813.383250] usb 2-1.2: new full-speed USB device number 9 using ehci_hcd
[ 1813.478021] usb 2-1.2: New USB device found, idVendor=03eb, idProduct=210a
[ 1813.478028] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 1813.478033] usb 2-1.2: Product: KILLERB001
[ 1813.478038] usb 2-1.2: Manufacturer: ATMEL
[ 1813.478042] usb 2-1.2: SerialNumber: 0004251CA001

Any advice or thoughts on what I might have done wrong?

What is the expected output? What do you see instead?

What version of the product are you using?
[ ] KillerBee 1.0 (from TAR file)
[ ] KillerBee beta (from SVN checkout) Revision # ___
[X] Other: Killerbee-1.0-1kali2 (32-bit)

On what operating system?
Kali Linux

With what Python version? (python -V)
2.7
Is scapy-com installed?

Please provide any additional information below.

Original issue reported on code.google.com by jtnati...@gmail.com on 30 Jul 2013 at 6:17

GoogleCodeExporter commented 9 years ago 
Were you able to get anywhere with this issue? I am having the same problem

Original comment by hammer...@gmail.com on 19 Aug 2013 at 10:21

GoogleCodeExporter commented 9 years ago 
Installing the pyUSB1 trunk has fixed the issue with zbid and my rzusbstick is 
now detected. However now I'm working through the "local variable 'response' 
referenced before assignment" error when running zbstumbler.

Original comment by hammer...@gmail.com on 20 Aug 2013 at 5:33

GoogleCodeExporter commented 9 years ago 
Sorry for just seeing this -- we're not getting notifications when issues post.

The commenter is correct -- installing the trunk version will fix this issue. 
It's a known issue based on how Backtrack/Kali installed KillerBee to the 
distribution, using a very old version. See the wiki posting on it for more 
details.

To the commenter with the local variable referenced before assignment, it's a 
timing issue that affects some users of RZUSBSTICK devices. If this is what 
you're doing, let me know what OS/system you're running on...

Original comment by r...@riverloopsecurity.com on 22 Nov 2013 at 12:15

GoogleCodeExporter commented 9 years ago 
Validated working with trunk on Kali 1.0.6.

Original comment by joshandr...@gmail.com on 30 Jun 2014 at 7:22