Open GoogleCodeExporter opened 9 years ago
#wps transaction failed (code: 0x02), re-trying last pin
#wps transaction failed (code: 0x03), re-trying last pin
I've experienced the same issues using an Alfa rtl8187. I've found the solution
to the problem is to play with the "-d" flag.
Start at "-d 15" or higher until you stop receiving the (code: 0x02) (code:
0x03) errors. Then work your way down. Each router I've tested likes a
different value.
I was also using the "--no-nacks" argument.
Original comment by cryptom...@gmail.com
on 4 Feb 2012 at 6:07
Hello,
- What is strange, it's OK with other PC with same alfa without -d option (2
pin/second)... So I will try with -d 15 but I'm not sure it will be OK.
- When I use --no-nacks option, I always have NACKS appears on the verbose
mode, is this option works ?
- I've seen something strange... If I power off my WRT320N during 4~5 days and
try to use Reaver after, it can go up to 20% without problem ! When it have
timeouts, I power off/on router and re-launch Reaver, and at this time it
cannot go up more than 1% !!!
Original comment by thecle...@free.fr
on 5 Feb 2012 at 12:12
I've updated WRT320N firmware from 1.03 to last 1.05.
Result : Reaver without any parameter, 100% success.
Wanna crack WPS ? Flash your router to last FW version ! lol
Original comment by thecle...@free.fr
on 5 Feb 2012 at 9:47
Original issue reported on code.google.com by
thecle...@free.fr
on 30 Jan 2012 at 9:37