Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: cant send auth request

  1. #1
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    4

    Default cant send auth request

    Hi guys... I finally stumbled across this forum, seems like an EXCELLENT resource!

    Now, I followed the video tutorials at
    (hmm I cant post links yet since I'm new... but may not be needed. but I got it from
    Thread ID 9036
    and I run into the same problem. When I run the following command:
    Code:
    sudo aireplay-ng -1 0 -e pudding -a 00:18:84:1f:67:5d -h 00:c0:ca:1e:15:bd wlan1
    When I do it, I get the following error
    Code:
    feras@feras-laptop:~$ sudo aireplay-ng -1 0 -e pudding -a 00:18:84:1f:67:5d -h 00:c0:ca:1e:15:bd wlan1
    12:57:14  Waiting for beacon frame (BSSID: 00:18:84:1F:67:5D) on channel 2
    
    12:57:14  Sending Authentication Request (Open System)
    
    12:57:16  Sending Authentication Request (Open System)
    
    12:57:18  Sending Authentication Request (Open System)
    
    12:57:20  Sending Authentication Request (Open System)
    
    12:57:22  Sending Authentication Request (Open System)
    
    12:57:24  Sending Authentication Request (Open System)
    
    12:57:26  Sending Authentication Request (Open System)
    
    12:57:28  Sending Authentication Request (Open System)
    
    12:57:30  Sending Authentication Request (Open System)
    
    12:57:32  Sending Authentication Request (Open System)
    
    12:57:34  Sending Authentication Request (Open System)
    
    12:57:36  Sending Authentication Request (Open System)
    
    12:57:38  Sending Authentication Request (Open System)
    
    12:57:40  Sending Authentication Request (Open System)
    
    12:57:42  Sending Authentication Request (Open System)
    
    12:57:44  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'm not sure how to resolve this. My wireless card is a usb alfa AWUS036H and I can run kismet without any issues etc.
    Also, just a note, I'm not using backtrack, but rather I just have all of this setup on a my ubuntu OS. Any direction would be greatly appreciated, and I'll definitely stick around the forums and start learning more

  2. #2
    Member
    Join Date
    Jun 2008
    Posts
    129

    Default

    Because your using Ubuntu you won't have the same drivers or patchs that are in the backtrack kernel so its hard to help as we are not on the same platform.

    Have you tried looking on the Aircrack trac?
    Have you tried moving closer to the AP?

  3. #3
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    4

    Default

    well, regardless, I booted BT3 off of the cd, and did the same instructions I did before, which is the same as "E-Z No Client WEP Cracking Tutorial"

    BT3 detected my drivers automatically, and my card was listed in iwconfig.

    Everything works fine, and it associated successfully. But when I run the -3 command to start collecting all the arp's, the #packets keeps going up, but I stay at 0 ARP's. Not sure how to improve this.

    Any ideas would be appreciated
    thanks

  4. #4
    Member
    Join Date
    Jun 2008
    Posts
    129

    Default

    Unfortunatly its not an exact science and its depends a lot on the AP as to how well any attack works. Sometimes is a matter of waiting to see if it works. Normally APs shouldn't give out ARPs without clients attached so a replay (-3) attack isn't always successful, depending on the make/model of AP.
    Does a normal ARP replay attack work with clients attached?

  5. #5
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    4

    Default

    ok, well Igot it working.
    My issue seems to be that I have to read close to 50k packets before I start getting any ARP's and ACK's. Is there anyway to improve this so it doesn't take so long?

  6. #6
    Senior Member
    Join Date
    Apr 2008
    Posts
    2,008

    Default

    Quote Originally Posted by johnny872005 View Post
    ok, well Igot it working.
    My issue seems to be that I have to read close to 50k packets before I start getting any ARP's and ACK's. Is there anyway to improve this so it doesn't take so long?
    This is simply because there did not happen to be any ARP packets transmitted before this. If you want to improve the speed, simply make sure to have a client connected that generates some traffic and ARPs for you to intercept and replay.
    -Monkeys are like nature's humans.

  7. #7
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    4

    Default

    there's no other way to improve this? I tried it on all 3 of my routers, and it's the same issue.... it takes a very long time before any ARP packets start getting received.

    How do others do this without having any clients connected to the router?

  8. #8
    Junior Member
    Join Date
    Feb 2008
    Posts
    44

    Default

    Patience is a virtue. When I was having problems I would do a chop chop attack (-4) and it seemed to work fine for me. Look into xploitz tutorial if you haven't already for the chop chop. His work is GIANT donation to this forum. Other times it could be you're not close enough to the router, but you said it was on your own network so that shouldn't be a problem.

  9. #9
    Just burned his ISO
    Join Date
    Nov 2008
    Posts
    5

    Default

    i am getting the same error on my senao 2511 not sure how to fix it

  10. #10
    Just burned his ISO
    Join Date
    Sep 2008
    Posts
    4

    Default

    I'm getting a similar problem. For some reason I can't connect to any WEP points anymore. Even in windows. WPA work just dandy.

    I've searched the net and there is a post saying that the Vista driver for his adapter screwed with the internal settings somehow, and he was able to fix it by messing with the driver settings. I don't have vista, but Ive been messing with all the internal settings and still no WEP.

    I can receive packets when there's a client, but I cant authenticate.

    Mac filtering isnt being used, and Im a safe distance from the router.

    I think the firmware somehow got messed during my world tour of linux operating systems.\

    Edit:
    Im playing around with the realtek wireless util and according to this, the adapter can't detect if its open or shared.


    I brokededed it...

    edit 2:

    Tried a different driver with a different computer. Same outcome.

Page 1 of 2 12 LastLast

Posting Permissions

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