Always trying pin 12345670 w/ BackTrack 5 R2

[GoogleCodeExporter]

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.)

Reaver 1.4

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

BackTrack 5 R2

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

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

-63

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

According to BSSID Sitecom

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

reaver -i mon0 -b <AP mac> -c 11 -vv
also tried with --win7 --no-nacks

6. Please describe what you think the issue is.

The issue appears with any AP in range. Reaver can't send a pin or receave a 
answer

7. Paste the output from Reaver below.

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Switching mon0 to channel 11
[?] Restore previous session for 00:0C:F6:67:2A:10? [n/Y] n
[+] Waiting for beacon from 00:0C:F6:67:2A:10
[+] Associated with 00:0C:F6:67:2A:10 (ESSID: Sitecom672A10)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[!] WARNING: Receive timeout occurred

Original issue reported on code.google.com by tobias.r...@gmail.com on 14 Mar 2012 at 2:42

[GoogleCodeExporter]

I forgot... It's a AWUS036NH with rt2800usb

Original comment by tobias.r...@gmail.com on 14 Mar 2012 at 2:42

[GoogleCodeExporter]

i have the same problame help pliz

Original comment by grinis1...@rambler.ru on 19 Mar 2012 at 8:02

[GoogleCodeExporter]

I tested many ADSL modems .....Planet ADW-XXXX .....such problem with rlt 8187b 
and Ar9002WB-1NG ...BACKTRACK 5 R2.... They are telecome too!!! please help

Original comment by klui...@gmail.com on 23 Mar 2012 at 9:27

[GoogleCodeExporter]

This proplems is only with telecom modems!!!!!

Original comment by klui...@gmail.com on 23 Mar 2012 at 9:27

[GoogleCodeExporter]

Can we get a list of telcom modems... so that i can clearly know if im affected 
or not. Thanks. 

Original comment by TheTurtl...@gmail.com on 27 Mar 2012 at 3:50

[GoogleCodeExporter]

PLANET ADW-4400, ADW-4401 

Original comment by klui...@gmail.com on 27 Mar 2012 at 8:37

[GoogleCodeExporter]

I tested 15 modems nothing can do with them

Original comment by klui...@gmail.com on 27 Mar 2012 at 8:37

[GoogleCodeExporter]

I live in a contry were this modem is more popular.... and people buy only them

Original comment by klui...@gmail.com on 27 Mar 2012 at 8:39

[GoogleCodeExporter]

Use --no-nacks. You may also need --no-associate and have aireplay-ng 
--fakeauth running.

Original comment by weedy2...@gmail.com on 26 May 2012 at 1:58

[GoogleCodeExporter]

See comment 361  for the coding sequence we use. This problem has been solved. 
You use a slightly altered coding to change the mac. If 361 is removed go to 
aircrack-ng forums general discussions. See comment on reaver 1.4 posted by 
Musket33 on 29 July 12

Musket Team A

Original comment by muske...@yahoo.com on 30 Jul 2012 at 4:30

[GoogleCodeExporter]

try this before doing the reaver attack:

ifconfig wlan0 down
macchanger -m 00:11:22:33:44:55 wlan0
airmon-ng start wlan0
ifconfig mon0 down
macchanger -m 00:11:22:33:44:55 mon0
ifconfig wlan0 up
ifconfig mon0 up

then your reaver attack

reaver ... ... ..

Original comment by x.tactic...@gmail.com on 22 Aug 2012 at 10:40

[GoogleCodeExporter]

the main question why the pin stick with ((12345670)) and doesn't change

Original comment by bloodowm...@gmail.com on 26 Aug 2012 at 10:36

[GoogleCodeExporter]

Me too this problem.Whay the pin doesnot change?

Original comment by nauda...@gmail.com on 18 Nov 2012 at 4:02

[GoogleCodeExporter]

Almost the routers are equal, and have this problem. I tried sugestions and 
didnt work :(

Original comment by xpto...@gmail.com on 21 Nov 2012 at 7:56

[GoogleCodeExporter]

I have this problem on OS X

[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[!] WARNING: 10 failed connections in a row
[+] Trying pin 12345670

how can i fix it?

Original comment by lukas.ch...@googlemail.com on 26 Jul 2014 at 8:26

[GoogleCodeExporter]

how can i fix it

Original comment by ahsunm...@gmail.com on 26 Jul 2014 at 9:09

[GoogleCodeExporter]

the main question why the pin stick with ((12345670)) and doesn't change

Original comment by kkchiu...@gmail.com on 24 Dec 2014 at 10:38

[GoogleCodeExporter]

same for me.... same pin always

Original comment by kingeb...@gmail.com on 16 Jan 2015 at 3:46

[GoogleCodeExporter]

I overcame this issue with the launch of "tcpdump -i mon0" and then on an other 
terminal with launch of reaver. Maybe somebody else will find this useful. 

Original comment by tubo.mat...@gmail.com on 16 Feb 2015 at 10:56