Results 1 to 7 of 7

Thread: Problems with D-Link DWA-652 card

  1. #1
    Junior Member imported_Timmay's Avatar
    Join Date
    Sep 2008
    Posts
    30

    Default 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

  2. #2
    Junior Member imported_Timmay's Avatar
    Join Date
    Sep 2008
    Posts
    30

    Default

    Following the "How to configure your Network Card" Backtrack Wiki page has not helped. I just thought I'd throw that out there in case anyone was planning on telling me to read it. So you know I'm currently connected to this page, and the internet from the card in question using Backtrack3 on USB. I just thought I'd let you know what else I've found that doesn't work...

    iwconfig -a - This tells me that there is no such device. Makes no sense since I'm using this wireless card right now.

    This might be easier...

    bt ~ # iwconfig -a
    -a No such device

    bt ~ # iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    wifi0 no wireless extensions.

    ath0 IEEE 802.11g ESSID:"111111" Nickname:""
    Mode:Managed Frequency:2.437 GHz Access Point: 00:11:11:11:11:
    Bit Rate:11 Mb/s Tx-Power:19 dBm Sensitivity=1/1
    Retryff RTS thrff Fragment thrff
    Encryption key:1111--11-11 Security mode:restricted
    Power Managementff
    Link Quality=74/70 Signal level=-22 dBm Noise level=-96 dBm
    Rx invalid nwid:649 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    bt ~ # ifconfig -a
    ath0 Link encap:Ethernet HWaddr 00:11:11:11:11:
    inet addr:192.168.5.100 Bcast:192.168.5.255 Mask:255.255.255.0
    UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1190 errors:0 dropped:0 overruns:0 frame:0
    TX packets:607 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1005524 (981.9 KiB) TX bytes:154005 (150.3 KiB)

    eth0 Link encap:Ethernet HWaddr 00:11:11:11:11:
    BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:16

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

    wifi0 Link encap:UNSPEC HWaddr 00-11-11-11-11-11-00-00-00-00-00-00-00-00-00-00
    UP BROADCAST NOTRAILERS RUNNING PROMISC ALLMULTI MTU:1500 Metric:1
    RX packets:12260 errors:0 dropped:892 overruns:0 frame:402
    TX packets:1532 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:280
    RX bytes:1300479 (1.2 MiB) TX bytes:215223 (210.1 KiB)
    Interrupt:17

    bt ~ # airmon-ng


    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    ath0 Atheros madwifi-ng VAP (parent: wifi0)

    So I try to run:

    Airodump-ng wifi0

    and this is what the screen freezes at:

    CH 0 ][ BAT: 2163 hours 13 mins ][ Elapsed: 0 s ][ 2008-09-24 15:41

    BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID


    BSSID STATION PWR Rate Lost Packets Probes

    So just for kicks i try:

    bt ~ # airodump-ng ath0
    ioctl(SIOCSIWMODE) failed: Invalid argument

    ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
    ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
    sure RFMON is enabled: run 'airmon-ng start ath0 <#>'
    Sysfs injection support was not found either.

    bt ~ # airodump-ng l0
    Interface l0:
    ioctl(SIOCGIFINDEX) failed: No such device
    bt ~ # airodump-ng eth0
    ioctl(SIOCSIWMODE) failed: Operation not supported

    ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
    ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
    sure RFMON is enabled: run 'airmon-ng start eth0 <#>'
    Sysfs injection support was not found either.

    So on this last block it says to run 'airmon-ng start eth0 <#>'

    I don't know what the <#> is in feferrence to so I tried it without it and got:

    bt ~ # airmon-ng start eth0


    Interface Chipset Driver

    wifi0 Atheros madwifi-ng
    ath0 Atheros madwifi-ng VAP (parent: wifi0)

    So I'm right back to where I started from. I'm terribly confused and don't understand why this isn't working. As a side note - because someone might ask - I get the same results when I'm not connected to the internet.

    Thanks,

    Timmay

  3. #3
    Junior Member imported_Timmay's Avatar
    Join Date
    Sep 2008
    Posts
    30

    Default

    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

  4. #4
    Junior Member imported_Timmay's Avatar
    Join Date
    Sep 2008
    Posts
    30

    Default

    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

  5. #5
    Just burned his ISO
    Join Date
    Sep 2008
    Posts
    22

    Default

    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

  6. #6
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    10

    Default

    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.

  7. #7
    Junior Member imported_Timmay's Avatar
    Join Date
    Sep 2008
    Posts
    30

    Default

    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
  •