A few things to consider before submitting an issue:
0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode. If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal. If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here. We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap). Issue
reports with pcap files attached will receive more serious consideration.
Answer the following questions for every issue submitted:
0. What version of Reaver are you using? (Only defects against the latest
version will be considered.)
1. What operating system are you using (Linux is the only supported OS)?
BT5 3R
2. Is your wireless card in monitor mode (yes/no)?
yes
3. What is the signal strength of the Access Point you are trying to crack?
-58db
4. What is the manufacturer and model # of the device you are trying to
crack?
D-link
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b xx:xx:xx:xx:xx -a -vv
6. Please describe what you think the issue is.
7. Paste the output from Reaver below.
Reaver si comporta in modo particolare... mentre con le precedenti reti o non
si connetteva o si bloccava al 99.99% con una nuova D-link comparsa in wash
pochi giorni fa, qualsiasi pin provi è quello giusto....in pratica si associa
alla rete, prova un pin a caso e dopo 2-3 secondi dice pin wps trovato e mi
restituisce lo stesso identico pin provato...questo con qualsiasi pin, mi
restituisce sempre il primo pin che prova anche se diverso dai precedenti.
Fin'ora non sono riuscito a farlo funzionare questo programma mi dite cosa ho
sbagliato?
Reaver behaves particular ... with previous networks would not connect or stuck
at 99.99%. Now with a new D-link appearance in the wash a few days ago, any pin
it try is the right one .... in practice the output is:
associated with the network,
trying pin xxxxxxxx
and after 2-3 seconds says
wps pin found and gives me back the exact same pin ...
this appened with any pin, It always returns the first pin that test even if it
isn't the same than above.
Until now I could not get it to work with any network or router (Telecom,
NETGEAR, D-Link, Linksys etc)
Please tell me what I did wrong?
Original issue reported on code.google.com by francesc...@gmail.com on 29 Oct 2012 at 12:32
Original issue reported on code.google.com by
francesc...@gmail.comon 29 Oct 2012 at 12:32