007GTi NextG ( Ralink RT2870/3070 rt2800 usb) problem

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

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

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?

-50

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

Dlink DSL-2680 (Firmware Version: v1.08 Hardware Version: A1)

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

reaver -i mon0 -b 1C:BD:B9:8C:FF:48 -vv

6. Please describe what you think the issue is.

before I tested reaver with     Intel 3945ABG   iwl3945 and it work fine now Im 
trying with 007Gti nextG antena(Ralink RT2870/3070  rt2800usb) and i have 
problem with association 

7. Paste the output from Reaver below.

Intel 3945ABG
] Switching mon1 to channel 1
[?] Restore previous session for 1C:BD:B9:8C:FF:48? [n/Y] y
[+] Restored previous session
[+] Waiting for beacon from 1C:BD:B9:8C:FF:48
[+] Associated with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[+] Trying pin 00155670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00165679

Ralink RT2870/3070  rt2800usb
+] Switching mon0 to channel 1
[?] Restore previous session for 1C:BD:B9:8C:FF:48? [n/Y] y
[+] Restored previous session
[+] Waiting for beacon from 1C:BD:B9:8C:FF:48
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)

tested many times same thing happen

Original issue reported on code.google.com by qpe...@gmail.com on 23 Feb 2012 at 1:34

[GoogleCodeExporter]

new thing while i was trying to associate in terminal i put aireplay-ng -9 mon0 
and it work for a moment 

[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[+] Associated with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[+] Trying pin 00195676
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] 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 00195676
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)
[!] WARNING: Failed to associate with 1C:BD:B9:8C:FF:48 (ESSID: TALKTALK-8CFF48)

Original comment by qpe...@gmail.com on 23 Feb 2012 at 2:26

[GoogleCodeExporter]

the router is defending or overheated. why this happens. happened to me and 10 
days later. 1 pin per minute testing.

Original comment by demon.ia...@hotmail.com on 23 Feb 2012 at 2:46

[GoogleCodeExporter]

so why It is working normal on my second card?

Original comment by qpe...@gmail.com on 23 Feb 2012 at 2:53

[GoogleCodeExporter]

I have the same problem, too.
I'm using backtrack 5 R2 with an Alfa AWUS036NH (which is nowadays often used 
for pen testing).The chipset is a Ralink RT2870/3070 It uses the rt2800usb 
driver. Is there a workaround to get the card working properly?
With Backtrack 5 R2 the kernel has been updated to 3.2.6.
Please help all the users and let's solve this problem with a fix.

Original comment by expose...@gmail.com on 12 Mar 2012 at 10:27

[GoogleCodeExporter]

I have the same problem, using Backtrack 5 R2 with an Alfa AWUS036NH, this is a 
known issue; Is reaver planning to support rt2870/3070?

Original comment by alejandr...@gmail.com on 12 Jul 2012 at 6:17

[GoogleCodeExporter]

Antenna is working fine some old routers react really slow. What worked 
for me  unlock antenna to full 2Watt power by custom region in linux and 
authentication by reaver not aireplay. Try different settings see what 
is working for you

Antenna is working 100% good

Original comment by qpe...@gmail.com on 13 Jul 2012 at 5:25

[GoogleCodeExporter]

I think the problem is not the AP nor reaver, it is the chipset, and this is 
the reason:
After each received packet, receiver has to answer with an ACK, but most cards 
in monitor mode doesn't do that (it is logical, they are in *monitor* mode). If 
the AP doesn't see the ACKs, it will think the packets have been lost and 
re-send them.
There are, however, some chipsets that acknowledge the packets sent to them 
even in monitor mode (I have only seen this on an Atheros chipset), and with 
them reaver works great.

So, if your card doesn't acknowledge the packets, you will notice many lines 
with "Failed to associate", but don't panic, after some time, it will associate.
And then it will receive each packet more than one, first the identity request: 
no problem, reaver send an identity response for each request received,
then the M1: here we have trouble, because when reaver receives a M-message 
repeated or out-of-order, it restarts the handshake immediately.
But you can change this behaviour (and make reaver ignore repeated or 
out-of-order messages) using the argument -N (--no-nacks). The repeated packets 
will still be printed, but ignored by reaver and the handshake can continue.

Hope this help.

Original comment by a123a654...@gmail.com on 30 Aug 2012 at 3:59