restart from entered pin

[GoogleCodeExporter]

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)

r112 svn

1. What operating system are you using (Linux is the only supported OS)?

Ubuntu Natty

2. Is your wireless card in monitor mode (yes/no)?

yes, rt73usb

3. What is the signal strength of the Access Point you are trying to crack?

-60db

4. What is the manufacturer and model # of the device you are trying to
crack?

Belkin N150 F9K1001 v1

5. What is the entire command line string you are supplying to reaver?

reaver -i mon0 -vv -S -a -w -p 26165677 -b XX:XX:XX:XX:XX:XX

6. Please describe what you think the issue is.

Trying to restart from an aborted run and keeps repeating same pin instead of 
continuing on

7. Paste the output from Reaver below.

Original issue reported on code.google.com by artherto...@gmail.com on 22 Feb 2012 at 3:55

[GoogleCodeExporter]

It's trying the same pin because you've told it so.

run this line:

reaver -i mon0 -vv -S -w -b XX:XX:XX:XX:XX:XX

is it asking you if you want to continue from last session ?
if so - press Y [enter]

Original comment by xFxIxC...@gmail.com on 29 Feb 2012 at 4:08

[GoogleCodeExporter]

my problem is there was no saved session, was running it from a live-cd 
and shutdown for the night, wanted to resume next day ... eneded up 
restarting from beginning :(

Original comment by artherto...@gmail.com on 29 Feb 2012 at 9:13

[GoogleCodeExporter]

I see...try this:

reaver -i mon0 -vv -S -a -w -p 26165677 -b XX:XX:XX:XX:XX:XX

ctrl + c (to stop it...after at least one try)

then reaver -i mon0 -vv -S -w -b XX:XX:XX:XX:XX:XX

It should ask you if you wanna start from previous session and it should go on 
from there.

Also I've read somewhere on this forum (or was it just google) I believe about 
a guy that has achieved this same thing by editing some files 
(reaver-1.4/src/keys.c perhaps?)

Original comment by xFxIxC...@gmail.com on 1 Mar 2012 at 2:36

[GoogleCodeExporter]

there is no default setting for continue from PIN.
so if you stopped the bf and tried a pin, no chance to continue from
the prior one. 

Original comment by atys....@gmail.com on 7 Jul 2012 at 7:35

[GoogleCodeExporter]

I found simple workaround to this issue:

- start reaver as mentioned with the correct BSSID

- wait for at least one successfuly confirmed pin [ie. M4/M6 received] 

- find the corresponding buffer file with the name of BSSID in the form 
<bssid>.wpc [15D62D769332.wpc example], it should be located in the current dir 
[user/root] or reaver's [if exists, ie. /etc/reaver or /usr/local/etc/reaver 
{when compiled with make install from svn}]

- open this file with text editor and modify the first number NNNN (it contains 
the counter - the high part of last checked pin) to desired restart value

- the same applies for the lower part of the pin, this value is contained on 
the second line of the file in the form LLL 

- for clarity, the pin is in the form as NNNNLLLx, x is checksum

The buffer file is saved only when at least one pin is checked, in the case it 
is still not, you may use file from another bssid and correct its name and the 
two values. 
Hope this helps.

A6XP 

Original comment by agent...@gmail.com on 13 Feb 2013 at 4:04

[GoogleCodeExporter]

Maaan thank you very much, it works!! 

Original comment by juananto...@gmail.com on 1 Jul 2013 at 7:17