linksys wusb54gs and BT2 live cd

[Eazy_E322]

I can't get BT (BT2 live cd) to recognize my wusb54gs ver 2.1 as a network device. It shows up under USB devices but thats it. Any suggestions?

Ok, so here's what I've done since initially asking this question:

1. First off, I ditched the BT2 live cd approach and went with the BT3b USB boot method.

2. Found a howto that uses ndiswrapper here:
ubuntuforums.org/showthread.php?t=225206
only to come to the realization that while the adapter worked, ndiswrapper doesn't support monitor mode...this led to more searching that ultimately lead me to

3. Found another howto touting "ndiswrapperless" installation of the wusb54gs here:
ubuntuforums.org/showthread.php?t=540942&highlight=wusb54gs
which again got the adapter working, and this time even to go into monitor mode (or at least not give and error when trying to do so), however when trying to run airodump-ng I get an error suggesting I make sure the adapter is up (which it is) and in monitor mode (which its supposed to be)

So here I sit, back at square one...anybody have any other ideas, there maybe a workaround using the ndiswrapperless approach, but I'm still picking up linux as I go so I'm probably overlooking it if its there.

[tybalt]

You'll need to post some more info if your looking to get much help. At least least list the exact commands your using to get this point. Also of the messages you're receiving. BT distros (for the most part) already come with patched drivers. Ndiswrapper will get you no where you want to be with pentesting. Stick with the drivers already supplied. Some useful commands that you could use would be:

dmesg | tail

lsusb

I seen a few ppl out there having some issues determining the chipset of some version of these devices

[linkdead]

can you do me a favor type "lsusb" in terminal and show me the output for the linksys dongle i might be able to help

haha the above wasn't there before oh well what tybalt said

[Eazy_E322]

After dmesg | tail (the WUSB54GS is wlan1, wlan0 is my 3945):

bt ~ #dmesg | tail
wlan0: RX non-WEP frame, but expected encryption
wmaster0: RX non-WEP frame, but expected encryption
wlan0: RX non-WEP frame, but expected encryption
wmaster0: RX non-WEP frame, but expected encryption
wlan0: RX non-WEP frame, but expected encryption
wmaster0: RX non-WEP frame, but expected encryption
wlan0: RX non-WEP frame, but expected encryption
wmaster0: RX non-WEP frame, but expected encryption
wlan0: RX non-WEP frame, but expected encryption
wmaster0: RX non-WEP frame, but expected encryption

After lsusb:

bt ~ # lsusb
Bus 2 Device 2: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever
Bus 2 Device 1: ID 0000:0000
Bus 1 Device 4: ID 13b1:0014 Linksys
Bus 1 Device 3: ID 154b:0002 PNY
Bus 1 Device 1: ID 0000:0000
Bus 3 Device 1: ID 0000:0000
Bus 5 Device 1: ID 0000:0000
Bus 4 Device 1: ID 0000:0000

[tybalt]

Bus 1 Device 4: ID 13b1:0014 Linksys

From what I gather this device has a BCM4320SKFBG chipset.

Quoting the Wiki:

Broadcom 43xx based cards should be able to inject - a bit sloppy but should work.

Looks like you got a sloppy one. Doing a Google search "13b1:0014 chipset". Doesn't return much results either. I reckon that these are pretty new devices/revisions

[Eazy_E322]

Alrighty...here's my solution to the problem:

1. Sell WUSB54GS on eBay

2. Buy another card

Should have done this a while ago, but oh well.

[imported_spankdidly]

Alrighty...here's my solution to the problem:

1. Sell WUSB54GS on eBay

2. Buy another card

Should have done this a while ago, but oh well.

Best solution I've heard all day!