Jump to content

Reaver at 90.90% for hours


velkrosmaak
 Share

Recommended Posts

So I thought I finally got reaver working nicely on my pineapple, with the logcheck module sending me grep'd status updates from the reaver log file.

The last few emails from my pineapple say that it's on 90.90%, and has been for the last few hours.

Googled the issue and came across this;

http://code.google.com/p/reaver-wps/issues/detail?id=158

This seems to suggest that upgrading reaver might help, but I didn't know if that might break the pineapple module.

I'm only using switches for reaver that are available via the reaver module, so not -L as some are suggesting might be the cause of the problem.

Thanks for any help!

Link to comment
Share on other sites

Hah, me again.

Just restarted my reaver attack using the web UI and saw this in the on screen log

<b>Fatal error</b>:  Allowed memory size of 8388608 bytes exhausted (tried to allocate 35 bytes) in <b>/usb/modules/reaver/reaver_actions.php</b> on line <b>31</b><br />

Anybody? I have an 8Gb stick attached with logs going to that so can't be full.

Link to comment
Share on other sites

And me once again. I'm not sure if I risk my pineapple's life by increasing the PHP memory limit from 8mb to something a bit higher. What do you think?

I'm so close and it's taken a good couple of days to get this far.

(re: many posts: it's lame being in the UK when everyone else is in the US!)

Link to comment
Share on other sites

And me once again. I'm not sure if I risk my pineapple's life by increasing the PHP memory limit from 8mb to something a bit higher. What do you think?

I'm so close and it's taken a good couple of days to get this far.

(re: many posts: it's lame being in the UK when everyone else is in the US!)

To be fair, if the reaver module causes things to run out of memory, something is done wrong with how the module handles reaver.

Sadly the developer has been away for a while now, so no idea what will happen in the future.

Link to comment
Share on other sites

I could be wrong, but I've seen this in Backtrack. When it happens, it's only on specific AP's. I'm guessing it might either be a bug in Reaver, or some routers have a bug that doesn't tell Reaver the correct PIN was found. Just a guess. Maybe try deleting Reaver's save data, and see if it gets stuck at the same point.?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...