search

google-code-export / wepbuster

Automatically exported from code.google.com/p/wepbuster
2 stars 4 forks source link

can't find APs #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# airmon-ng stop wlan0

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
                (monitor mode disabled)

root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# ifconfig wlan0 down
root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# airmon-ng start
wlan0

Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
3546    NetworkManager
3564    wpa_supplicant
10105   avahi-daemon
10106   avahi-daemon

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
                (monitor mode enabled on mon0)

root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# perl wepbuster 
Error for wireless request "Set Mode" (8B06) :
    SET failed on device mon0 ; Device or resource busy.
MODE: crack
.
Scanning channel 6 for WEP-enabled Access Points
.....
Found 0 AP(s) on channel 6

Scanning channel 11 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 11

Scanning channel 1 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 1

Found no AP. Exiting...

 BSSID              PWR  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH
ESSID                                                                     

 00:14:BF:C3:07:CB  -39       51        0    0  11  54   WEP  WEP         mx

Original issue reported on code.google.com by nandelb...@gmail.com on 3 Jun 2009 at 9:19

GoogleCodeExporter commented 9 years ago 
if you found 4 processes that could cause trouble, wouldn't it be possible that 
they
are the real culprit?? see for your self.. :-) This is interesting.. stay tuned 
for
the non-beta released version! ciao!!

Original comment by subscr1b...@gmail.com on 3 Jun 2009 at 10:02

GoogleCodeExporter commented 9 years ago 
after kill all the processess (NetworkManager, wpa_supplicant, etc.)... 

root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# airmon-ng stop wlan0

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
                (monitor mode disabled)

root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# ifconfig wlan0 down
root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# airmon-ng start wlan0

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
                (monitor mode enabled on mon0)

root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta#  perl wepbuster 11
Error for wireless request "Set Mode" (8B06) :
    SET failed on device mon0 ; Device or resource busy.
MODE: crack

Scanning channel 11 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 11

Found no AP. Exiting...

Original comment by nandelb...@gmail.com on 3 Jun 2009 at 11:29

GoogleCodeExporter commented 9 years ago 
Set failed on device "mon0"??? Could it be that wepbuster is detecting the wrong
card?? check what's inside /proc/net/wireless... open wepbuster in some text 
editor..
there should be an instruction on how to set the wireless card manually... all 
this
should be easier on non-beta release.. stay tuned!! =)

Original comment by markjays...@gmail.com on 3 Jun 2009 at 11:49

GoogleCodeExporter commented 9 years ago 
Itried with another wifi card with the same result...

root@michael:/media/sdc1/home/marc/Desktop/wepbuster-1.0_beta# airmon-ng stop 
wlan0

Interface   Chipset     Driver

wlan0       ZyDAS 1211  zd1211rw - [phy1]
                (monitor mode disabled)

root@michael:/media/sdc1/home/marc/Desktop/wepbuster-1.0_beta# ifconfig wlan0 
down
root@michael:/media/sdc1/home/marc/Desktop/wepbuster-1.0_beta# airmon-ng start 
wlan0

Interface   Chipset     Driver

wlan0       ZyDAS 1211  zd1211rw - [phy1]
                (monitor mode enabled on mon0)

root@michael:/media/sdc1/home/marc/Desktop/wepbuster-1.0_beta# nano wepbuster 

comented several lines and set this others...
##########################   BEGIN DETECT WIRELESS INTERFACE  
###############################################

        # Get the last wireless interface. If the following code doesn't work for
you. Just comment all these lines
        # and set your mac ad wifi interface manually using the variables $wifi_if
and $macaddress

#       open WIFI, "/proc/net/wireless" or die $!;
#       while (<WIFI>){
#        next unless /^\s+\w+\d/;
#        $wifi_if = (split/:/, $_)[0];
#        $wifi_if =~ s/^\s+//;
#        $ENV{'wifi_if'} = $wifi_if;
## Uncomment "last;"below if you want to use your first wireless interface 
instead of
the last;
#        last;
#       }
# 
#        unless (defined $wifi_if){
#               print "\nCan\'t find any wireless card in /proc/net/wireless. 
Try
setting it manually.\nExiting...\n\n";
#               exit;
#        }
#
#       # Get the mac address
# 
#       system "iwconfig $wifi_if mode managed";
#       open IFCONFIG, "ifconfig $wifi_if |" or die $!;
#       while (<IFCONFIG>){
#         next unless /HWaddr/;
#         $macaddress = (split /\s+/,$_)[-1];
#       }

### UNCOMMENT AND SET THESE LINES IF THE ABOVE CODE DOES NOT WORK FOR YOU

$wifi_if = 'mon0';
$ENV{'wifi_if'} = $wifi_if;
$macaddress = '00:02:72:6f:a2:ed';

root@michael:/media/sdc1/home/marc/Desktop/wepbuster-1.0_beta# perl wepbuster 
MODE: crack

Scanning channel 6 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 6

Scanning channel 11 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 11

Scanning channel 1 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 1

Found no AP. Exiting...

and there are two APs in the correct channels...

 BSSID              PWR  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID     

 00:06:B1:20:EC:6A   16       23        0    0   1  11   WEP  WEP         <length: 8>

 00:01:38:DA:C0:41   10        4        0    0   6  54 . WEP  WEP         WLAN_B3

Original comment by nandelb...@gmail.com on 3 Jun 2009 at 1:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Can you do me a favor??

I need the output of the following on your 3945 card:

1. First, make sure the card is NOT in monitor mode, then do this:

airmon-ng

2. Then "airmon-ng start your_interface"

3. Finally, just "airmon-ng".

Original comment by markjays...@gmail.com on 3 Jun 2009 at 4:00

GoogleCodeExporter commented 9 years ago 
of course, but tommorow at 8 o'clock, in a 12 hours, when I arribe at work

Original comment by nandelb...@gmail.com on 3 Jun 2009 at 5:28

GoogleCodeExporter commented 9 years ago 
Card is not in monitor mode...

root@mula-laptop:/home/mula# iwconfig wlan0 

wlan0     IEEE 802.11abg  ESSID:"mx"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:14:BF:C3:07:CB   
          Bit Rate=36 Mb/s   Tx-Power=15 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Power Management:off
          Link Quality=90/100  Signal level:-41 dBm  Noise level=-78 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@mula-laptop:/home/mula# airmon-ng 

Interface   Chipset     Driver

wlan0           iwl3945 - [phy0]

root@mula-laptop:~# airmon-ng start wlan0

Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
2889    NetworkManager
2907    wpa_supplicant
2913    avahi-daemon
2914    avahi-daemon
22053   dhclient
Process with PID 22053 (dhclient) is running on interface wlan0

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
                (monitor mode enabled on mon0)

root@mula-laptop:~# airmon-ng 

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
mon0        Intel 3945ABG   iwl3945 - [phy0]

IF BEFORE TO PUT THE CARD IN MONITOR MODE I KILL THE PROCESS...

root@mula-laptop:~# kill 2889 2907 2913 2914 22053

root@mula-laptop:~# airmon-ng 

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]

root@mula-laptop:~# airmon-ng start wlan0

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
                (monitor mode enabled on mon0)

root@mula-laptop:~# airmon-ng 

Interface   Chipset     Driver

wlan0       Intel 3945ABG   iwl3945 - [phy0]
mon0        Intel 3945ABG   iwl3945 - [phy0]

NOW I TRY WEPBUSTER...

root@mula-laptop:/home/mula/Escriptori/wepbuster-1.0_beta# perl wepbuster 
Error for wireless request "Set Mode" (8B06) :
    SET failed on device mon0 ; Device or resource busy.
MODE: crack

Scanning channel 6 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 6

.
Scanning channel 11 for WEP-enabled Access Points
.....
Found 0 AP(s) on channel 11

Scanning channel 1 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 1

Found no AP. Exiting...

Original comment by nandelb...@gmail.com on 4 Jun 2009 at 6:30

GoogleCodeExporter commented 9 years ago 
Yes, that is expected.. The program was written for a wireless card for which a 
monitor interface doesn't have to be created. In your case, during auto 
detection, 
the program tries to do an "iwconfig mon0 mode managed" so it fails, because 
mon0 
must only be monitor and the other interface will be the managed or injecting 
interface.. I'm fixing the code now, it should be flexible after the fix. After 
this, we can concentrate more on adding new features.. stay tuned!! =) -mark

Original comment by markjays...@gmail.com on 4 Jun 2009 at 6:48

GoogleCodeExporter commented 9 years ago 
Just uploaded another beta release.. let me know if it worked for you... =)

Original comment by markjays...@gmail.com on 5 Jun 2009 at 7:19

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
no, not worked here! :(

I'm doing something wrong?

I have a Linksys WRT54G3G with a 128bits wep key enabled, 2 meters behind me. 
Some
weeks ago I cracked this router wep key with the same laptop / wifi card with no
problems.

After boot I downloaded wepbuster beta 2 and I typed the attached file
(wepbuster.txt) commands on a gnome-terminal.

I repeat... I'm doing something wrong?

Thank's!

Original comment by nandelb...@gmail.com on 5 Jun 2009 at 10:13

Attachments:

GoogleCodeExporter commented 9 years ago 
can you download the script again.. the new beta version 0.2... I made some 
corrections, you must have 
downloaded the wrong one... 

After downloading, disable the monitor mode.. Let the program do this for you...
Then if it is still not working.. Open the source code and there are two 
variables you can manually set the 
card.; $inject_iface and $monitor_iface.

your $inject_iface should be wlan0 and $monitor_iface should be mon0

Let me know which one solved your problem... show me the output of the script 
again..

Original comment by subscr1b...@gmail.com on 5 Jun 2009 at 10:38

GoogleCodeExporter commented 9 years ago 
Ah... i made a mistake again... I forgot to reset the $inject_iface and
$monitor_iface back so you will be seeing only wlan0/wlan0 instead of 
wlan0/mon0... I
have added the code to the SVN. You should check out the latest revision..

Original comment by markjays...@gmail.com on 5 Jun 2009 at 12:36

GoogleCodeExporter commented 9 years ago 
i am using the latest code wepbuster-0.1beta0.2   and everything runs great only
problem is it doesn't find any of the WEP access points.  there are two directly
behind me, maybe 15 feet away and is running on chan 6. if i run 'sudo 
airodump-ng -c
6 mon0' they all pop right up. when i run wepbuster everything seems to execute
correctly i get no errors. i am running Ubuntu 9.4 on an Acer Aspire1 with the 
built
in Atheros chipset.  here is my output

Detecting wireless interfaces...

---------------------------------------------------

Found wlan0...
Getting monitor interface...
monitor interface --> mon0

Found 1 useable wireless card(s)
 1) wlan0/mon0

MODE: crack (using: wlan0/mon0 == 00:24:2b:25:0e:cb)

Scanning channel 6 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 6

.
Scanning channel 11 for WEP-enabled Access Points
.....
Found 0 AP(s) on channel 11

Scanning channel 1 for WEP-enabled Access Points
......
Found 0 AP(s) on channel 1

Found no AP. Exiting...

any ideas on what i should do?

Original comment by parki...@gmail.com on 6 Jun 2009 at 4:58

GoogleCodeExporter commented 9 years ago 
try the new beta release and make sure to consult  the updated Troubleshooting 
in the wiki.

Original comment by markjays...@gmail.com on 6 Jun 2009 at 6:25

GoogleCodeExporter commented 9 years ago

Original comment by markjays...@gmail.com on 12 Jun 2009 at 5:05