Results 1 to 3 of 3

Thread: wepbuster with DWL-G650 returning attack unsuccessful

  1. #1
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    3

    Unhappy wepbuster with DWL-G650 returning attack unsuccessful

    Hi,

    Yes, I am a newbie, and apologize for asking for such basic assistance. I am running BT4 installed, on a HP Pavilion dv5000 and am using a D-Link AirPlus DWL-G650 (which I'm told should work).

    I have taken the following steps:

    - I have followed the instructions supplied by the aircrack-ng website to verify that I am able to do injection.
    - I have verified that I am able to put my D-Link card into monitor mode.
    - I run sudo perl wepbuster
    - I choose my wlan1 card
    - Both WEP AP's that I have set up fail to be cracked, they are not using mac filtering.

    I get the following from wepbuster:

    Code:
    Pwning "TestAP" (XX:XX:XX:XX:XX:XX)     Tue Jul 21 20:09:11 2009
    Checking for mac filtering...
    Can't associate. aireplay-ng died!
    
    Attack was unsuccessful. Possible reasons:
    
    Too many to mention. =)
    Try running this command manually:
    
    "aireplay -1 1 -a XX:XX:XX:XX:XX:XX wlan1 -e "TestAP" -h XX:XX:XX:XX:XX:XX 2>&1"
    So, I run the command (adding in the missing -ng of course) and get this:

    Code:
    ...
    ...
    ...
    20:11:16  Sending Authentication Request (Open System)
    Attack was unsuccessful. Possible reasons:
    
        * Perhaps MAC address filtering is enabled.
        * Check that the BSSID (-a option) is correct.
        * Try to change the number of packets (-o option).
        * The driver/card doesn't support injection.
        * This attack sometimes fails against some APs.
        * The card is not on the same channel as the AP.
        * You're too far from the AP. Get closer, or lower
          the transmit rate.
    I realize that this is very generic but am hoping for some assistance in narrowing down the problem. I suspect driver related issues, as everything else is 'out of the box' so to speak.

    If it helps, when starting kismet I get the error "could not connect to Kismet server." I'm not really interested in getting kismet set up at the moment (one thing at a time) so, please help a newbie to get started

  2. #2
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    3

    Default

    As an afterthought...I installed the madwifi driver...is there a way to tell that it's working properly? Not sure how to make sure the card is actually using it.

  3. #3
    Just burned his ISO
    Join Date
    Jul 2009
    Posts
    3

    Default

    Crap, found the issue. Card is a prism2.5 ...

    search for ticket 288 on aircrack-ng bugs.



    Time to get a non-prism card.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •