Open GoogleCodeExporter opened 9 years ago
Signal: 92%
Original comment by demon.ia...@hotmail.com
on 12 Feb 2012 at 9:00
Some people reported having successfully cracked Thomson routers with the "-E
-L -T 2" options. Not sure if it's true though... Either way, there is a new
vulnerability found for Thomson routers that you can calculate the default key
using the serial announced by the WPS technology. More info @
http://www.backtrack-linux.org/forums/showthread.php?t=47519&p=212902&viewfull=1
#post212902
Original comment by miguelfa...@gmail.com
on 12 Feb 2012 at 9:11
[deleted comment]
use the "-E-L-T 2" options.
[+] Trying pin 00475679
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00475679
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00475679
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00475679
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 00475679
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
* thanks for the info.
Original comment by demon.ia...@hotmail.com
on 13 Feb 2012 at 2:10
Maybe you're too far away from the AP. Try a higher value on the option -T,
because "-T 2" is causing all those timeouts.
Original comment by miguelfa...@gmail.com
on 13 Feb 2012 at 8:04
The AP is 7 meters from the adapter.
Reaver test 1 pin per minute.
100,000,000 pin to try to reach 100% (00000000 => 99999999)
WPA cracking takes 4 days to 250key / s to get keys to 100,000,000.
no way to speed up or you can try more pins?
also there are several routers that are blocked for 24 hours.
Original comment by demon.ia...@hotmail.com
on 15 Feb 2012 at 5:03
I'm afraid that your maths is a little out by a fairly large margin
Reaver at worst will require under 11,000 pin attempts, that's why reaver
brings the exploit down to reasonable timescales.
The speed of pin testing is limited by (amongst other things) signal quality,
processing power on the router and how good the programmer was in optimising
his routines.
There's a lot of maths going on for key exchanges occurring between the router
and reaver, as these usually contain a very low end ARM or MIPS processors the
router can often become sluggish or even crash. Adding the possibility of the
router deciding that it is under attack can also cause the router to stop
responding to reaver
Hence the practice adding delays between each try or after say 10 PIN attempts
can often speed up the exploit process.
Original comment by kilby.ct...@gmail.com
on 17 Feb 2012 at 3:53
hi,
i had the same with thomson router :
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
due this WARNING: Detected AP rate limiting you get a 300 second delay , but if
you are patience reaver will do its job after 30 hours it was finnished and
reaver showed me a 64 lenght wpa key
i used basic reaver entry without -L etc
Original comment by heeeen...@gmail.com
on 20 Apr 2012 at 7:42
@ coment 8
mind tellin me the first 4 digit of the pin you found cuz im tryin with a
Thomson TG782T been over 37 hours not even close 2 10% perhaps
Original comment by bersebu...@gmail.com
on 22 May 2012 at 7:59
thanks
Original comment by Annaby2...@gmail.com
on 14 Oct 2012 at 9:30
warning ap rate limiting detected ....same shit how to bypass this shit ? :)
Original comment by realman...@gmail.com
on 29 Dec 2012 at 9:19
plzz help us
Original comment by badraghb...@gmail.com
on 17 Jan 2013 at 2:38
plizzzzz help for thomson WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
Original comment by messaoud...@gmail.com
on 29 Jan 2013 at 3:54
for thomson routers i use aireplay-ng ..... no more 60 seconded to wait
Original comment by asmah...@gmail.com
on 18 Feb 2013 at 3:39
if you want to bypass this message in reaver about failure in association add
-A in your command before vv
Original comment by markdoom...@gmail.com
on 2 Feb 2014 at 5:31
i need thomson wps pin plzzz help me
Original comment by yship...@gmail.com
on 4 Apr 2015 at 12:14
Original issue reported on code.google.com by
demon.ia...@hotmail.com
on 12 Feb 2012 at 8:58