Closed GoogleCodeExporter closed 9 years ago
You put down that you are using version 2.3; I assume you meant 1.3? If you're
using version 1.3 your session state will be auto-saved, so you can ctl+c to
quit, and then re-start reaver against the same AP with the -vv flags. It will
ask you if you want to restore the session; answer 'y' (no quotes) and it will
pick up where it left off.
Original comment by cheff...@tacnetsol.com
on 6 Jan 2012 at 12:43
Thank you for the fast reply. Now i am seeing the recieve timeout.
Going to give the ap some time and resume again. Perhaps i am locked
out of the ap
On Jan 5, 2012, at 7:44 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 6 Jan 2012 at 1:01
Can you try walking over to the AP, power cycling it, and then resume reaver?
Original comment by peac...@tacnetsol.com
on 6 Jan 2012 at 3:28
No but i am doing some tests on the cisco i have here.. The light on
the router blinks when wps starts, getting it to blink is hit or miss
and if i miss the first pin i believe that calls for a reboot.
Although i am testing a power cycle too. The other attack is paused
till i figure out some order to things.
JeffMoses.com
On Jan 5, 2012, at 10:28 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 6 Jan 2012 at 3:34
I have tried running mac changer pulling up and down mon -0 the ap i
have in house is just sitting not starting the wps cycle at all after
a reboot of both and a new mac.. No pulsing cisco...
JeffMoses.com
On Jan 5, 2012, at 10:28 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 6 Jan 2012 at 3:39
jeff, can you provide pcaps please?
Original comment by cheff...@tacnetsol.com
on 9 Jan 2012 at 6:51
Working on that now... I think that this is actually a range issue..
Running two attacks now to confirm ... What is the pcap process?
JeffMoses.com
On Jan 9, 2012, at 1:51 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 9 Jan 2012 at 6:55
Probably the easiest way is to use Wireshark. If your capture file is very
large, you can use the display filter of 'eapol || eap' (no quotes), and save
only the displayed packets to a file.
Original comment by cheff...@tacnetsol.com
on 9 Jan 2012 at 6:57
Thanks should be able to add it at some point today.
JeffMoses.com
On Jan 9, 2012, at 1:58 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 9 Jan 2012 at 7:01
I am suspecting a network card issue.. I am running almost all
broadcom dell machines. I plan to pick up a new card tomorrow and
rerun some attacks. Do you think my logic is sound?
JeffMoses.com
On Jan 9, 2012, at 1:58 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 9 Jan 2012 at 11:19
Well I'm not sure that it's a card issue since you were able to complete 45% of
the attack, which means Reaver appears to be working with your existing card.
Hard to tell without pcaps of what Reaver is actually sending and receiving
though.
Original comment by cheff...@tacnetsol.com
on 10 Jan 2012 at 1:46
Original comment by cheff...@tacnetsol.com
on 11 Jan 2012 at 5:03
This is a problem running backtrack and a broadcom b43 chipset. I
picked up a usb alfa adaptor with a high gain antenna and have run 4
attacks at 1 second per attempt.. Fyi
JeffMoses.com
On Jan 11, 2012, at 12:03 PM, "reaver-wps@googlecode.com"
<reaver-wps@googlecode.com> wrote:
Original comment by jeffmose...@gmail.com
on 12 Jan 2012 at 5:52
Thanks for the info Jeff. I'll add the b43 chipset to the wiki.
Original comment by cheff...@tacnetsol.com
on 17 Jan 2012 at 12:49
No problem. I had an idea for a feature, It would be nice to specify an
audible alarm for when a pin is found. Something in the line that could
point to a simple wav or midi file. perhaps a small alert could be included
with the reaver source?
Original comment by jeffmose...@gmail.com
on 17 Jan 2012 at 1:25
Original issue reported on code.google.com by
jeffmose...@gmail.com
on 6 Jan 2012 at 12:38