Kismet RT73 | linksys WUSB54GC

[loonm]

Another wireless/kismet thread. I am sorry

I got myself a linksys WUSB54GC but upon putting it into the usb slot, the light on it doesn't go on. I have a wireless device on my motherboard by defualt but that shouldnt be a problem. Dmesg regonizes it being added tho:

usb 1-6: new high speed USB device using ehci_hcd and address 11
usb 1-6: configuration #1 chosen from 1 choice
phy4: Selected rate control algorithm 'minstrel'
Registered led device: rt73usb-phy4::radio
Registered led device: rt73usb-phy4::assoc
Registered led device: rt73usb-phy4::quality

Iwconfig adds an entry called "wlan1":

wlan1     IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated
          Tx-Power=0 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

Installed the rt73 driver because it dident work 'right out of the box', like another website suggested with:

wget http://homepages.tu-darmstadt.de/~p_larbig/wlan/rt73-k2wrlz-3.0.3.tar.bz2
tar -xjf rt73-k2wrlz-3.0.3.tar.bz2
cd rt73-k2wrlz-3.0.3/Module
make
sudo make install
sudo modprobe rt73

airmon-ng start wlan1 says this:

Found 3 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID     Name
4663    dhclient3
4749    dhclient3
4877    dhclient3
Process with PID 4877 (dhclient3) is running on interface wlan0


Interface       Chipset         Driver

wlan0           RTL8187         rtl8187 - [phy0]
wlan0mon                RTL8187         rtl8187 - [phy0]
wlan0monmon             RTL8187         rtl8187 - [phy0]
wlan1           Ralink 2573 USB rt73usb - [phy4]SIOCSIFFLAGS: No such file or di                              rectory

                                (monitor mode enabled on mon0)

As you can see, lots of wlan0mon got added for whatever reason. When starting kismet_server:

pwn@bt:~$ sudo kismet_server
[sudo] password for pwn:
ERROR: Kismet was started as root, NOT launching external control binary.
       This is NOT the preferred method of starting Kismet as Kismet will
       continue to run as root the entire time.  Please read the README
       file section about Installation & Security and be sure this is what
       you want to do.
INFO: Reading from config file /usr/etc/kismet.conf
INFO: No 'dronelisten' config line and no command line drone-listen
      argument given, Kismet drone server will not be enabled.
INFO: Created alert tracker...
ERROR: Failed to open primary plugin directory (/usr/lib/kismet/): No such
       file or directory
ERROR: Failed to open user plugin directory (/root/.kismet//plugins/): No
       such file or directory
INFO: Kismet will attempt to hop channels at 5 channels per second unless
      overridden by source-specific options
INFO: No specific sources named on the command line, sources will be read
      from kismet.conf
INFO: Using hardware channel list 1,2,3,4,5,6,7,8,9,10,11,12,13,14, 14
      channels on source wlan1
INFO: Source 'wlan1' will attempt to create and use a monitor-only VAP
      instead of reconfiguring the main interface
INFO: Created source wlan1 with UUID 802aa9b6-530c-11df-9860-f302680ee301
INFO: Will attempt to reopen on source 'wlan1' if there are errors
INFO: Created Kismet UI TCP server on port 2501
INFO: Kismet drone framework disabled, drone will not be activated.
INFO: Inserting basic packet dissectors...
INFO: Allowing Kismet frontends to view WEP keys
INFO: Starting GPS components...
INFO: GPS support disabled in kismet.conf
ERROR: Could not open OUI file '/etc/manuf': No such file or directory
ERROR: Could not open OUI file '/usr/share/wireshark/wireshark/manuf': No
       such file or directory
INFO: Opened OUI file '/usr/share/wireshark/manuf
INFO: Indexing manufacturer db
INFO: Completed indexing manufacturer db, 11850 lines 237 indexes
INFO: Creating network tracker...
ERROR: Kismet was not compiled with PCRE, cannot use 'ssidregex' option in
       an apspoof filter
INFO: Creating channel tracker...
INFO: Registering dumpfiles...
INFO: Pcap log in PPI format
INFO: Opened pcapdump log file 'Kismet-20100428-23-24-59-1.pcapdump'
INFO: Opened netxml log file 'Kismet-20100428-23-24-59-1.netxml'
INFO: Opened nettxt log file 'Kismet-20100428-23-24-59-1.nettxt'
INFO: Opened gpsxml log file 'Kismet-20100428-23-24-59-1.gpsxml'
INFO: Opened alert log file 'Kismet-20100428-23-24-59-1.alert'
INFO: Kismet starting to gather packets
ERROR: SetIFFlags: interface wlan1: No such file or directory
ERROR: Failed to bring up interface 'wlan1', this often means there is a
       problem with the driver (such as missing firmware), check the
       output of `dmesg'.
INFO: Attempting to re-open errored packet source wlan1
ERROR: SetIFFlags: interface wlan1: No such file or directory
ERROR: Failed to bring up interface 'wlan1', this often means there is a
       problem with the driver (such as missing firmware), check the
       output of `dmesg'.
INFO: Attempting to re-open errored packet source wlan1

and DMesg shows it cant find the correct firmware

phy4 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
device wlan1 entered promiscuous mode
rt73usb 1-6:1.0: firmware: requesting rt73.bin
phy4 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
rt73usb 1-6:1.0: firmware: requesting rt73.bin
phy4 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
rt73usb 1-6:1.0: firmware: requesting rt73.bin
phy4 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
rt73usb 1-6:1.0: firmware: requesting rt73.bin
phy4 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.

Hope i provided enough info. I am running bt4.

Greets

[ip3t3r]

i've the same problem!...
you've the wusb54gc V3?