search

shutup / reaver-wps

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

Invalid percentage value displayed #472

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi guys, I've been running reaver against one of my Netgear routers and have 
come across a strange problem with the percentage being displayed.

The reason I have run the attack against this router is because the WPS switch 
on the routers firmware does absolutely nothing, so even if i turn the switch 
off on the firmware (via telnet or web interface), the WPS still remains active 
and can be cracked. Now I am simply testing distances and cataloging crack 
times so I can implement a rotating psk system as my company does not want to 
fork out for another router. cheap or what?

Anyway, the issue I have is when reaver reached somewhere between 28%-29% then 
the percentage shown jumped to 91.xx%.

When it reached 93.97% I switched over to verbose mode to view what pin it was 
currently on and it displays 31133296, which if I'm right is around the 35-36 
percentile range?

I will wait to see what happens exactly once reaver reaches 100%, perhaps the 
percentage will reset or even correct itself. Hopefully though it won't stop, 
as I am currently testing it at a range where the signal is at -70, and it is 
averaging around 50-60 seconds/pin.

Operating system is the latest update BT5 32-bit Gnome, running on a 64-bit 
Lenovo B517 laptop. Also running the latest available kernel and BT has been 
heavily modified, practically to the point where it is a different OS.

Also, running reaver 1.4.

Original issue reported on code.google.com by bennett_...@hotmail.com on 18 Feb 2013 at 12:33

GoogleCodeExporter commented 9 years ago 
Sorry, forgot to add the reaver details.

Running reaver on wlan1, which is an rt2800 hwun1 chipset. rfkill displays wlan 
as unblocked, all running processes that interfere with monitor mode have been 
killed, then for some reason I have to stop the interface, run 'rfkill block 
wlan' then unblock it again then restart the interface, or reaver and wash 
won't work properly.

reaver -i mon0 -b 30:46:9A:XX:XX:XX -c 7 -l 300 -vv

Original comment by bennett_...@hotmail.com on 18 Feb 2013 at 12:37

GoogleCodeExporter commented 9 years ago 
Reaver is running perfectly normal in your test environment. Reaver found the 
first 4 digits of the pin (3113) and that is the reason for the jump to + 90%. 
If you run in verbose from the beginning you'll see Reaver attacking only the 
first 4 pins. Once achieved it then attacks the next 3 plus the checksum. As I 
said, perfectly normal.

Original comment by bellta...@gmail.com on 18 Feb 2013 at 3:04

GoogleCodeExporter commented 9 years ago 
same as :
https://code.google.com/p/reaver-wps/issues/detail?id=455&start=300

It's not a bug.

Original comment by i.boud...@gmail.com on 23 Feb 2013 at 2:56