wash -i mon0 not show my ESSID (Thomson) But show with airodump-ng mon0

[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. What operating system are you using (Linux is the only supported OS)?
Backtrack R2
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?
Thomson
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 00:1D:68:E7:61:1F -vv
6. Please describe what you think the issue is.
airodump-ng mon0 shows my ESSID But wash -i mon0 not show my ESSID (Thomson) 
But it shows all my neighbor's  ESSID Fxcept Thomson ie I  have problem with 
only my own thomson modem  neighbor's Thomson also not shwing I use a Linksys 
modem instead of Thomon There is no problem
see result with
 Pin cracked in 9548 seconds
[+] WPS PIN: '13867209'
[+] WPA PSK: 'XXXXXXXXXXX'
[+] AP SSID: 'Linksys
ISSUE IS ONLY THOMSON IS NOT WORKING
NB:Same Thomson modem I am Using now with Alfa
7. Paste the output from Reaver below.

root@bt:~# reaver -i mon0 -b 00:1D:68:E7:61:1F -vv

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

[+] Waiting for beacon from 00:1D:68:E7:61:1F
[+] Switching mon0 to channel 1
[!] WARNING: Failed to associate with 00:1D:68:E7:61:1F (ESSID: ThomsonE26EC0)

NB: I tesred with Lynksys instead of Thomson it is cracked

Original issue reported on code.google.com by jamalpal...@gmail.com on 9 Apr 2012 at 11:28

[GoogleCodeExporter]

I am facing same problem with THOMSON. I think REAVER not supporting  THOMSON 
modem.
I am using Alfa and BTR5 R2 with reaver . with airodump-ng mon0 command am 
getting total eight ESSID including 3 THOMSON But  wash -i mon0 command result 
is   only 5 ESSID Without thomson. I used Live CD and  VM Ware Both Results 
ware same. Also tested with Different computers.Result was same.I think THOMSON 
Router cant hack with Reaver.
Anybody can help ?
Thank you                  

Original comment by hamee...@gmail.com on 11 Apr 2012 at 7:05

[GoogleCodeExporter]

i want hack wpa with reaver thomson 
trying 5 password
detected this problem 
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
and continue trying 5 password again

WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking
WARNING: Detected AP rate limiting, waiting 60seconds before re-checking

what i do 
i hope to help me someone

Original comment by brahimr...@gmail.com on 18 Apr 2012 at 1:33

[GoogleCodeExporter]

download eapeak and test to see if that tool identifies your router as 
supporting WPS with the --check-wps flag.  If the router does not support WPS 
via EAP, then reaver & wash are working properly.

Original comment by ryanjna...@gmail.com on 18 Apr 2012 at 9:50

[GoogleCodeExporter]

can you explicit me 
please i don't know what i do 
please ryanjna 

Original comment by brahimr...@gmail.com on 28 Apr 2012 at 9:28