-
Junior Member
Problems with D-Link DWA-652 card
I’ve been having some problems getting my D-Link DWA-652 to work properly. I’ve searched the forum and found that it is a Madwifi supported adapter that has an Atheros AR5008 chipset. In a post by -=Xploitz=- he said that Backtrack3 final has the adapters for this card. Using the Wireless Assistant – I can see networks in my range. They are there and the card appears to be working. From there I go into a Shell and try to find out what airodump-ng can see – so I type in:
# airodump-ng wifi0
Then the program freezes. Depending on how it’s feeling that day – it either doesn’t show up at all, or it shows up, but doesn’t scan. I have used the program quite successfully with my Netgear WG111v2 using both the Live CD and USB versions of Backtrack3.
I also tried:
# airodump-ng ath0
# airodump-ng wlan0
# airodump-ng whyarentyouworking - and that didn’t help any.
I tried them knowing full well that they wouldn’t work, but I had to rule out the possibilities anyway
Any suggestions would be helpful.
As a side note – the card does work in Windows. I use it for all of my wireless activities while using Micro$oft.
Thanks,
Timmay
-
Junior Member
-
Junior Member
As yet another side note - I am able to use the aircrack suite in windows with this same card. I decided to try Backtrack because I can't inject in Windows, but I can (using airserv-ng,airodump-ng, and aircrack-ng) collect enough packets to find my own WEP key. Just thought that might be useful to someone - somehow.
Thanks,
Timmay
-
Junior Member
Ok - I got it figured out.
I went to the aircrack-ng website. They have a blurb on how to do it. Here's how it goes...
# airmon-ng stop ath0
# airmon-ng start wifi0
This changes the card from managed to monitor mode.
Then to start airodump-ng - instead of using wifi0 as your interface - use:
# airodump-ng ath0
Thanks for the help. And hopefully it will help someone else.
Timmay
-
Try giveing airodump a few more parameters.
At the moment all your giving it is an interface.
Try a channel, ESSIB, BSSID etc
Also make sure you have the interface set to monitor mode correctly
Apologies if I gave the wrong advice but it was the best ideas I had 
Regards,
Dom
-
I have the same dlink and a mini pci ath5008, the 2.6.21.5 kernel does not like either one by itself, and trying to use both at once makes it crash and burn. I bit the bullet and upgraded the kernel, which let's you build the ath5k drivers and ultimately is the less stressful route.
-
Junior Member
Dom.Hutton -
"Try giveing airodump a few more parameters"
The problem wasn't with the parameters, it was with taking the card off of managed mode and putting it into monitored mode, Then using ath0 as the interface instead of wifi0. Once I did that everything works fine.
Aidan -
"I have the same dlink and a mini pci ath5008, the 2.6.21.5 kernel does not like either one by itself, and trying to use both at once makes it crash and burn. I bit the bullet and upgraded the kernel, which let's you build the ath5k drivers and ultimately is the less stressful route."
I will be the first to admit that I know very little about linux. I don't know how to compile anything or upgrade a kernel. I can barely get around my directories. That's why I tried the Live CD, and then the Live USB. The final sequence that I use to get everyting up and running is:
Shell #1
# airmon-ng stop ath0
# ifconfig wifi0 down
# macchanger –-mac 00:11:22:33:44:55 wifi0
# airmon-ng start wifi0
# airodump-ng ath0
# airodump-ng –c (channel) –w (file name) –-bssid (bssid) ath0
Shell #2
# aireplay-ng -1 0 –a (bssid) –h (mac) –e (essid) ath0
# aireplay-ng -3 –b (bssid) –h (mac) ath0
Shell #3
# aircrack-ng (file name)
Hope this helps someone.
Timmay
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
