search

allishwell / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

Reaver is not able to keep right channel on a newest build #168

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
A few things to consider before submitting an issue:
There is a bug on a newest source. Reaver worked right before. But on a newest 
source Reaver changes channel every time when need to try new pin.

Log:
reaver -i mon0 -b  xx:xx:xx:xx:xx:xx -vv

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

[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 11
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Trying pin 12345670
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 11
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 11
[!] WARNING: Failed to associate with xx:xx:xx:xx:xx:xx (ESSID: xxxxxx)
[+] Sending EAPOL START request

Original issue reported on code.google.com by juuso...@gmail.com on 23 Jan 2012 at 9:25

GoogleCodeExporter commented 8 years ago 
This is probably due to a low signal strength from the target AP. Prior to each 
pin attempt, Reaver checks to see if the AP has switched channels (some APs 
will do this periodically). If Reaver can't determine if the AP is on the same 
channel, it will start channel hopping until it finds the AP again.

If you know the AP's channel, you can disable this functionality by explicitly 
specifying the channel (-c 11).

Original comment by cheff...@tacnetsol.com on 23 Jan 2012 at 12:53

GoogleCodeExporter commented 8 years ago 
Yes, I tried also this option and then reaper is answering only: Sending EAPOL 
START request.

I tested also with other modem with same results.

All versions before this (1.4) have worked well and I have got pin successfully 
so I think it must be bug in newest version.

Original comment by juuso...@gmail.com on 23 Jan 2012 at 1:02

GoogleCodeExporter commented 8 years ago 
When you tested previous versions, were all of your test conditions identical 
to what they are now? Same AP? Same location? Same signal strength? Same 
wireless card/driver? 

If you are on the correct channel and Reaver can't initiate an EAP session, it 
definitely sounds like connectivity problems. I have no issues running 1.4 
against any of my APs.

Original comment by cheff...@tacnetsol.com on 23 Jan 2012 at 2:17

GoogleCodeExporter commented 8 years ago 
You're right! I installed everything again from the start point on totally same 
way but when I tested reaver again it works fully!!?!

I have no idea what gone wrong when I updated from v1.3 to 1.4.

Sorry for wasting your time and thanks for great tool also!

Original comment by juuso...@gmail.com on 23 Jan 2012 at 5:24

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
hello guys i've been seeing this "[+] Switching mon0 to channel 7
" and keeps changing channels every sec for like a couple of hours 
i don't know if this will keep it this way or wut 
btw this is the first time i used Backtrack just to get access to a High speed 
internet connection in my neighborhood 
everything went fine from installing Backtrack ,running card on monitor mode 
... ^^
just hope you guys are faster replying this that backtrack changing channels 
forever

Original comment by jinzoc...@gmail.com on 19 Mar 2013 at 4:09