Page 1 of 8 123 ... LastLast
Results 1 to 10 of 77

Thread: Still have problem capturing WPA handshake

  1. #1
    Junior Member
    Join Date
    Jan 2009
    Posts
    59

    Unhappy Still have problem capturing WPA handshake

    I have tried it again this few days but I still cannot capture the WPA handshake.
    The reply from the system is as follow:

    Sending 64 directed DeAuth. STMAC: [00:16:EA:C8:27:30] [0| 0 ACKs]

    What have I done wrong?

    I try to patch the new driver into the Wireless adaptor but it just gives me error: "drivers/net/wireless/zd1211rw/zd_mac.c", No such file or directory...
    Please help...



    Previous discussion please refer to the following link:
    hxxp://forums.remote-exploit.org/showthread.php?t=20998

  2. #2
    Member cr1spyj0nes's Avatar
    Join Date
    Sep 2008
    Posts
    164

    Default

    how far away from the router and client are you?

  3. #3
    Junior Member
    Join Date
    Jan 2009
    Posts
    59

    Default

    My client (victum) is just next to my attacking laptop... less then 10CM
    My wireless router is just 1M away...

  4. #4
    Member cr1spyj0nes's Avatar
    Join Date
    Sep 2008
    Posts
    164

    Default

    what wireless card are you using? please print your airmon-ng, ifconfig output's and will see whats going on.

  5. #5
    Junior Member
    Join Date
    Jan 2009
    Posts
    59

    Default

    Code:
    ifconfig
    
    eth0 Link encap:Ethernet HWaddr 00:0C:29:72:24:0B
           inet addr 192.168.223.129 Bcast: 192.168.233.255 Mask 255.255.255.0
           UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:55 errors:0 dropped:0 overruns:0 frame:0
           TX packet:5 error:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:8338 (8.1KiB)  TX bytes:1344 (1.3KiB)
           Interrupt:18 Base address:0x2000
    
    eth1 Link encap: UNSPEC HWaddr 00-0E-3B-0A-43-61
           UP BROADCAST NOTRAOLERS RUNNING PROMISC ALLMULTI MTU:1500 Metric:1
           RX packets:39930 errors:28483 dropped:0 overruns:0 frame:28483
           TX packets:38056 error:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes: 6359789 (6.0MiB) TX bytes: 950672 (928.3 KiB)
    
    lo --> Loopback (Omited)
    Code:
    airmon-ng start eth1
    
    Found 1 processes that could cause trouble.
    If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to kill (some of) them!
    
    PID         Name
    3451       dhcpcd
    
    Interface              Chipset               Driver
    eth1                    ZyDAS 1211         zd1211rw (monitor mode enable)

  6. #6
    Member cr1spyj0nes's Avatar
    Join Date
    Sep 2008
    Posts
    164

    Default

    what wireless card are you using? usb or bilt in? if built in, what computer are you using? please print your airmon-ng output,

  7. #7
    Junior Member
    Join Date
    Jan 2009
    Posts
    59

    Default

    I am using HWU8DD
    Driver: Rev.B: zd1211rw
    Chipset: Rev.B: zd1211b
    It is a wireless USB adaptor...
    Data obtain from:
    hxxp://backtrack.offensive-security.com/index.php/HCL:Wireless

  8. #8
    Member cr1spyj0nes's Avatar
    Join Date
    Sep 2008
    Posts
    164

    Default

    what do you get when you type,, aireplay-ng --test eth1

  9. #9
    Junior Member
    Join Date
    Jan 2009
    Posts
    59

    Default

    Code:
    aireplay-ng --test eth1
    06:20:49  Trying broadcast probe requests...
    06:20:51  No Answer...
    06:20:51  Found 0 APs
    But last week I can use this equipments to capture packet and crack the WEP key within 14 mins!

  10. #10
    Member cr1spyj0nes's Avatar
    Join Date
    Sep 2008
    Posts
    164

    Default

    ok injection isn't working so you need to ether re patch the driver with hxxp://patches.aircrack-ng.org/zd1211rw_inject_2.6.26.patch 2.6.26 being your kernel, check your kernel by using uname if its different change the link and see if there is one for your kernel,,,
    capturing wep is really just listening for the packets and de authenticating is sending packets to the client hence injecting,

Page 1 of 8 123 ... 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
  •