Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PROBLEME WITH REAVER/BROADCOM4313 #734

Open
GoogleCodeExporter opened this issue Sep 5, 2015 · 0 comments
Open

PROBLEME WITH REAVER/BROADCOM4313 #734

GoogleCodeExporter opened this issue Sep 5, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

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)?
UBUNTU 14.04 LTS
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 DB
4. What is the manufacturer and model # of the device you are trying to
crack?
TPLINK
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 78:54:2E:F5:C3:88 -vv
6. Please describe what you think the issue is.
probleme with the driver brcmsmac
7. Paste the output from Reaver below.

root@Dan-000:/home/oberon# wash -i mon0

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

BSSID                  Channel       RSSI       WPS Version       WPS Locked    
    ESSID
--------------------------------------------------------------------------------
-------------------------------




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

[+] Waiting for beacon from 78:54:2E:F5:C3:88
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
[!] WARNING: Failed to associate with 78:54:2E:F5:C3:88 (ESSID: (null))
^C
[+] Nothing done, nothing to save.



Original issue reported on code.google.com by xzeron...@gmail.com on 6 Aug 2015 at 12:26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant