Why does Reaver not want to connect even with a working pincode?

D

Dnomin2019-02-21 02:05:58

Computer networks

Dnomin, 2019-02-21 02:05:58

Raspberry pi 3 model B (connected over ssh)
Tp-link tl-wn722n (qualcomm Atheros Communications AR9271)
airmon-ng start wlan1:

ifconfig

ifconfig 
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:d0:dd:86  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.13  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::fbee:c2a4:bfea:db6c  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:85:88:d3  txqueuelen 1000  (Ethernet)
        RX packets 968  bytes 62728 (61.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 528  bytes 88889 (86.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1mon: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        unspec 60-E3-27-0A-1B-3D-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 5239  bytes 907972 (886.6 KiB)
        RX errors 0  dropped 67  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wash -i wlan1mon

BSSID               Ch  dBm  WPS  Lck  Vendor    ESSID
--------------------------------------------------------------------------------
84:1B:5E:31:4A:FC    1  -37  1.0  No   Broadcom  {essid}

reaver -i wlan1mon -b 84:1B:5E:31:4A:FC -p 63018905 -vv

Reaver v1.6.5 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>

[+] Waiting for beacon from 84:1B:5E:31:4A:FC
[+] Switching wlan1mon to channel 1
[+] Received beacon from 84:1B:5E:31:4A:FC
[+] Vendor: Broadcom
[+] Trying pin "63018905"
[+] Sending authentication request
[!] Found packet with bad FCS, skipping...
[+] Sending association request
[+] Associated with 84:1B:5E:31:4A:FC (ESSID: Nimond)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] 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 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 "63018905"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 84:1B:5E:31:4A:FC (ESSID: Nimond)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] 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 identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin "63018905"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 84:1B:5E:31:4A:FC (ESSID: Nimond)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] 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 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 "63018905"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 84:1B:5E:31:4A:FC (ESSID: Nimond)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] 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 identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin "63018905"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 84:1B:5E:31:4A:FC (ESSID: Nimond)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] 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 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 "63018905"
[+] Sending authentication request
[+] Sending association request
[+] Associated with 84:1B:5E:31:4A:FC (ESSID: Nimond)
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request

Without a pincode, it offers any point to try the pincode 12345670 in a circle, on the raspbian the same problem, I thought that because of the distribution kit, rolled Kali, it did not help.

Reply

Answer the question

In order to leave comments, you need to log in

1 answer(s)

P

Prog, 2019-02-21
@damprog

to start with
#airmon-ng check kill
to be sure
and start the river with the --no-nacks option
and it is better to specify the -c channel