google-code-export / wepbuster

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

No such file or directory at wepbuster line 1147, <IFCONFIG> line 9. #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. perl wepbuster

What is the expected output? What do you see instead?

I see:

MODE: crack
.
Scanning channel 6 for WEP-enabled Access Points
...........No such file or directory at wepbuster line 1147, <IFCONFIG> line 9.

I expect that works

What version of the product are you using? On what operating system?

1.0_beta on ubuntu 9.04

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

GoogleCodeExporter commented 9 years ago
Try

sudo -i
airmon-ng stop [device, mine is wlan0]
ifconfig [device] down
airmon-ng start [device]
perl wepbuster

This worked for me (eeebuntu 3.0, based on ubuntu 9.04)

Original comment by Skydance...@gmail.com on 3 Jun 2009 at 8:26

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
The program should work without a glitch if the wireless card has been setup
properly before running. The code shouldn't be that difficult to understand the 
way
it is auto detecting the wireless card. stay tuned for the non beta version
release!... =).. Line 1147 is trying to open the output of airodump-ng.. seems 
like
the script couldn't run airodump... save yourselves from trouble, modify
aircrack-ng.c and airodump-ng.h.

Original comment by markjays...@gmail.com on 3 Jun 2009 at 10:07

GoogleCodeExporter commented 9 years ago
having this same issue.
Ubuntu 9.04
Netgear WAG511 v2 (Atheros)
Using today's trunk build of aircrack-ng

Destroy everything
Run wlanconfig ath create wlandev wifi0 wlanmode sta
Run iwconfig:

lo        no wireless extensions.

eth0      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11Ta  ESSID:""  Nickname:""
          Mode:Managed  Frequency:5.76 GHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-83 dBm  Noise level=-83 dBm
          Rx invalid nwid:14313  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

/proc/net/wireless shows:

Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
  ath0: 0001    0.  -96.  -96.   24551      0      0      0      0        0

If I destroy ath0 and try to run wepbuster, it recognizes that there are no
devices...so it's seeing the empty wireless file.

Original comment by hoopyfro...@gmail.com on 4 Jun 2009 at 5:10

GoogleCodeExporter commented 9 years ago
Can you do one thing? put the card in monitor mode and show me what's inside 
/proc/net/wireless

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

GoogleCodeExporter commented 9 years ago
Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
ath0_rename0: 0000    0.  -96.  -96.       0      0      0      0      0        
0

disregard the weird "ath0_rename0" name.  The creation of the VAP is just 
started
acting a little goofy right now for some unknown reason.

Original comment by hoopyfro...@gmail.com on 4 Jun 2009 at 7:05

GoogleCodeExporter commented 9 years ago
Another shot:

Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
  ath2: 0000    0.  -96.  -96.       0      0      0      0      0        0

Original comment by hoopyfro...@gmail.com on 4 Jun 2009 at 7:16

GoogleCodeExporter commented 9 years ago
ah... nevermind that /proc/net/wireless.... i'm doing everything through 
airmon-ng... hope i'll get it right.. just 
finished writing the needed function.. will test it right away as soon as i get 
this silly vmware to cooperate..

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

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

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

GoogleCodeExporter commented 9 years ago
I have the same error:

$svn info

Ruta: .
URL: http://wepbuster.googlecode.com/svn/trunk
Raíz del repositorio: http://wepbuster.googlecode.com/svn
UUID del repositorio: 338c5770-4ddc-11de-9ee4-913ee803a954
Revisión: 16
Tipo de nodo: directorio
Agendado: normal
Autor del último cambio: markjayson.alvarez
Revisión del último cambio: 16
Fecha de último cambio: 2009-06-05 09:28:01 -0300 (vie 05 de jun de 2009)

Details:
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo perl 
wepbuster 

Detecting wireless interfaces...

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

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

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

Use of uninitialized value in concatenation (.) or string at wepbuster line 257,
<IFCONFIG> line 9.

MODE: crack     (using: wlan0/mon2 == )

Scanning channel 6 for WEP-enabled Access Points
............No existe el fichero ó directorio at wepbuster line 1208, 
<IFCONFIG> line 9.

Aircrack-ng version:
ulises2k@black2k:~/programas/aircrack-ng$ svn info
Ruta: .
URL: http://trac.aircrack-ng.org/svn/trunk
Raíz del repositorio: http://trac.aircrack-ng.org/svn
UUID del repositorio: 28c6078b-6c39-48e3-add9-af49d547ecab
Revisión: 1558
Tipo de nodo: directorio
Agendado: normal
Autor del último cambio: misterx
Revisión del último cambio: 1558
Fecha de último cambio: 2009-06-02 14:57:15 -0300 (mar 02 de jun de 2009)

Original comment by ulises2k on 5 Jun 2009 at 12:43

GoogleCodeExporter commented 9 years ago
can you tell me what happens when you do "iwconfig wlan0 mode managed"? After 
that, i'm doing "ifconfig 
wlan0" to get the mac address, kindly check the output of that as well. If the 
first one does not require putting 
the card to managed mode (i need that command so that ifconfig will show 
xx:xx:xx:xx:xx as mac address 
instead of xx-xx-x-x--x- etc...

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

GoogleCodeExporter commented 9 years ago
pleasecheckout r17, see if it works for you..

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

GoogleCodeExporter commented 9 years ago
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo iwconfig 
wlan0
mode managed
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo ifconfig 
wlan0
wlan0     Link encap:Ethernet  direcciónHW 00:18:de:03:f4:2e  
          inet dirección:192.168.100.55  Difusión:192.168.100.255  Máscara:255.255.255.0
          dirección inet6: fe80::218:deff:fe03:f42e/64 Alcance:Vínculo
          ARRIBA DIFUSIÓN CORRIENDO MULTICAST  MTU:1500  Métrica:1
          RX packets:19289 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10181 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000 
          RX bytes:11149985 (10.6 MB)  TX bytes:1963460 (1.8 MB)

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ ls
README.TXT  wepbuster
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ svn up
U    wepbuster
Actualizado a la revisión 17.
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo perl 
wepbuster 
syntax error at wepbuster line 177, near "unless $inject_iface "
Global symbol "%monitor_iface" requires explicit package name at wepbuster line 
177.
Execution of wepbuster aborted due to compilation errors.

Original comment by ulises2k on 5 Jun 2009 at 1:03

GoogleCodeExporter commented 9 years ago
Tried the just uploaded version.

I first destroyed everything...pulled the card and plugged it back in.  At this
point, I'm starting fresh with wifi0 and an automatically created ath0.

lo        no wireless extensions.

eth0      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.427 GHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Here's the output after running:
(Note the now detected ath2 (exist in monitor mode) - did wepbuster create 
this?)
(ath0 auto-created running in managed mode)
(I selected ath0 when prompted on this run)

Detecting wireless interfaces...

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

Found wifi0...
Getting monitor interface...
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device ath1 ; No such device.
ath1: ERROR while getting interface flags: No such device
monitor interface --> wifi0

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

Found ath0...
Getting monitor interface...
monitor interface --> ath0

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

Found ath2...
Getting monitor interface...
monitor interface --> ath2

Found 3 useable wireless card(s)

Select which one to use [1] (You HAVE 3 seconds)
 1) wifi0/wifi0
 2) ath0/ath0
 3) ath2/ath2

2

MODE: crack (using: ath0/ath0 == 00:14:6c:e8:dd:14)

Scanning channel 6 for WEP-enabled Access Points
............No such file or directory at wepbuster line 1208, <IFCONFIG> line 8.

Next run, I selected the ath2 device. Here's the output
(Note the error about not finding ath1.  Why is it looking for ath1 all the 
sudden?)
(Note: There is a TON of APs around me LOL...you have NO idea :)

Detecting wireless interfaces...

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

Found wifi0...
Getting monitor interface...
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device ath1 ; No such device.
ath1: ERROR while getting interface flags: No such device
monitor interface --> wifi0

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

Found ath0...
Getting monitor interface...
monitor interface --> ath0

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

Found ath2...
Getting monitor interface...
monitor interface --> ath2

Found 3 useable wireless card(s)

Select which one to use [1] (You HAVE 3 seconds)
 1) wifi0/wifi0
 2) ath0/ath0
 3) ath2/ath2

3
Error for wireless request "Set Mode" (8B06) :
    SET failed on device ath2 ; Invalid argument.

MODE: crack (using: ath2/ath2 == 
00-14-6C-E8-DD-14-E0-E3-00-00-00-00-00-00-00-00)

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

After making these runs, here's the output of iwconfig:

lo        no wireless extensions.

eth0      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
          Rx invalid nwid:52937  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath2      IEEE 802.11g  ESSID:""  Nickname:""
          Mode:Monitor  Frequency:2.412 GHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath1_rename  IEEE 802.11g  ESSID:""  Nickname:""
          Mode:Monitor  Channel:0  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Here's the contents of /proc/net/wireless now:

Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
  ath0: 0001    0.  -96.  -96.   59485      0      0      0      0        0
  ath2: 0000    0.  -96.  -96.       0      0      0      0      0        0
ath1_rename: 0000    0.  -96.  -96.       0      0      0      0      0        0

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 1:08

GoogleCodeExporter commented 9 years ago
arg... forgot the parenthesis... check out again.. =(

Original comment by markjays...@gmail.com on 5 Jun 2009 at 1:08

GoogleCodeExporter commented 9 years ago
syntax error at wepbuster line 177, near "unless $inject_iface "
Global symbol "%monitor_iface" requires explicit package name at wepbuster line 
177.
Execution of wepbuster aborted due to compilation errors.

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 1:13

GoogleCodeExporter commented 9 years ago
argh again..... this is getting out of hand... which card are you using? which 
driver?

Basically, this is what wepbuster does, it runs:
1.  airmon-ng  and get the list of wireless cards, for each one, it executes 
airmon-ng start ifac
2. when airmon-ng start was acted on a wireless card, it returns the monitor 
interface in case it has created 
one for that interface.

Can you do this steps manually and let me know what you are seeing..
First, start with a clean one,

Do airmon-ng and tell me what you see.

Then try to airmon-ng start each interface found in the previous list.

Original comment by markjays...@gmail.com on 5 Jun 2009 at 1:17

GoogleCodeExporter commented 9 years ago
hoopy, that syntax error is because of the missing parenthesis.. checkout the 
latest revision..

Original comment by markjays...@gmail.com on 5 Jun 2009 at 1:20

GoogleCodeExporter commented 9 years ago
by the way, if all else fails, try manually setting your $inject_iface, 
$monitor_iface, and $macaddress for 
$inject_iface.. I've commited some changes again... check out the latest..

Original comment by markjays...@gmail.com on 5 Jun 2009 at 1:28

GoogleCodeExporter commented 9 years ago
Still only seeing the .2 release.  Are you incrementing version numbers?

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 1:42

GoogleCodeExporter commented 9 years ago
For the archive, no because these are minor syntax errors.. I'm updating the 
tarball
however. Also, much easier if you will just checkout using svn... 

Original comment by markjays...@gmail.com on 5 Jun 2009 at 1:47

GoogleCodeExporter commented 9 years ago
Output of latest version:

syntax error at wepbuster line 177, near "unless $inject_iface "
Global symbol "%monitor_iface" requires explicit package name at wepbuster line 
177.
Execution of wepbuster aborted due to compilation errors.

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 1:57

GoogleCodeExporter commented 9 years ago
I reboot the computer & exec this commands:

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ svn up
En la revisión 21.
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ ifconfig 
eth0      Link encap:Ethernet  direcciónHW 00:18:f3:b5:1c:04  
          ARRIBA DIFUSIÓN MULTICAST  MTU:1500  Métrica:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupción:18 Dirección base: 0x8c00 

lo        Link encap:Bucle local  
          inet dirección:127.0.0.1  Máscara:255.0.0.0
          dirección inet6: ::1/128 Alcance:Anfitrión
          ARRIBA LOOPBACK CORRIENDO  MTU:16436  Métrica:1
          RX packets:1912 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1912 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:0 
          RX bytes:95600 (93.3 KB)  TX bytes:95600 (93.3 KB)

vmnet1    Link encap:Ethernet  direcciónHW 00:50:56:c0:00:01  
          inet dirección:172.16.182.1  Difusión:172.16.182.255  Máscara:255.255.255.0
          dirección inet6: fe80::250:56ff:fec0:1/64 Alcance:Vínculo
          ARRIBA DIFUSIÓN CORRIENDO MULTICAST  MTU:1500  Métrica:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmnet8    Link encap:Ethernet  direcciónHW 00:50:56:c0:00:08  
          inet dirección:172.16.81.1  Difusión:172.16.81.255  Máscara:255.255.255.0
          dirección inet6: fe80::250:56ff:fec0:8/64 Alcance:Vínculo
          ARRIBA DIFUSIÓN CORRIENDO MULTICAST  MTU:1500  Métrica:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  direcciónHW 00:18:de:03:f4:2e  
          inet dirección:192.168.100.55  Difusión:192.168.100.255  Máscara:255.255.255.0
          dirección inet6: fe80::218:deff:fe03:f42e/64 Alcance:Vínculo
          ARRIBA DIFUSIÓN CORRIENDO MULTICAST  MTU:1500  Métrica:1
          RX packets:1075 errors:0 dropped:0 overruns:0 frame:0
          TX packets:608 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000 
          RX bytes:622303 (607.7 KB)  TX bytes:119324 (116.5 KB)

wmaster0  Link encap:UNSPEC  direcciónHW
00-18-DE-03-F4-2E-00-00-00-00-00-00-00-00-00-00  
          ARRIBA DIFUSIÓN CORRIENDO MULTICAST  MTU:1500  Métrica:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          colisiones:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo airmon-ng

Interface       Chipset         Driver

wlan0           Intel 3945ABG   iwl3945 - [phy0]

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo airmon-ng 
start
wlan0

Found 7 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!
-e 
PID     Name
5266    NetworkManager
5280    NetworkManagerD
5322    avahi-daemon
5323    avahi-daemon
6183    dhcdbd
7046    wpa_supplicant
7093    dhclient
Process with PID 5536 (vmnet-bridge) is running on interface wlan0
Process with PID 7093 (dhclient) is running on interface wlan0

Interface       Chipset         Driver

wlan0           Intel 3945ABG   iwl3945 - [phy0]
                                (monitor mode enabled on mon0)
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo perl 
wepbuster 

Detecting wireless interfaces...

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

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

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

MODE: crack     (using: wlan0/mon1 == )

Scanning channel 6 for WEP-enabled Access Points
............No existe el fichero ó directorio at wepbuster line 1220, 
<IFCONFIG> line 9.

Original comment by ulises2k on 5 Jun 2009 at 1:58

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Just ran the build from svn:

Detecting wireless interfaces...

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

Found wifi0...
Getting monitor interface...
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device ath1 ; No such device.
ath1: ERROR while getting interface flags: No such device
monitor interface --> wifi0

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

Found ath0...
Getting monitor interface...
monitor interface --> ath0

Found 2 useable wireless card(s)

Select which one to use [1] (You HAVE 3 seconds)
 1) wifi0/wifi0
 2) ath0/ath0

2
Error for wireless request "Set Mode" (8B06) :
    SET failed on device ath0 ; Invalid argument.

MODE: crack (using: ath0/ath0 == 
06-14-6C-E8-DD-14-E0-23-00-00-00-00-00-00-00-00)

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 hoopyfro...@gmail.com on 5 Jun 2009 at 2:00

GoogleCodeExporter commented 9 years ago
On comment #16:

you must have the old tarball.. that particular line should read "unless
($inject_iface ne $monitor_iface){

download the new tarball... On the project homepage, there's a link to the 
"Updates"
be sure to check it so you would know if something has changed....

Original comment by markjays...@gmail.com on 5 Jun 2009 at 2:01

GoogleCodeExporter commented 9 years ago
See my last comment (#25)
I'll start using the svn builds to avoid any confusion.

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 2:03

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
On comment #25:

which interfaces are you expecting that the program would detect?

you can set them manually.

$inject_iface
$monitor_iface
$macaddress  (of the inject interface)

Can you show me the output of ifconfig and airmon-ng so that we can match 
them..?

Original comment by markjays...@gmail.com on 5 Jun 2009 at 2:08

GoogleCodeExporter commented 9 years ago
I'm using an English version.

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 2:08

GoogleCodeExporter commented 9 years ago
Not you hoopy.. it's the other guy who's using non-english.. =)

Original comment by markjays...@gmail.com on 5 Jun 2009 at 2:10

GoogleCodeExporter commented 9 years ago
On Comment #23 =)

Seems like my regular expression is failing for your non-english linux 
version... try
setting the macaddress manually in the script

Original comment by markjays...@gmail.com on 5 Jun 2009 at 2:13

GoogleCodeExporter commented 9 years ago
The same here with Back Track 4 Beta and a zd1211 wireless card...

zd1211rw 1-1:1.0: phy0
usbcore: registered new interface driver zd1211rw

root@bt:~/Desktop/tarball_staging# ./wepbuster

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:02:72:6f:a2:f9)

Scanning channel 6 for WEP-enabled Access Points
............No such file or directory at ./wepbuster line 1220, <IFCONFIG> line 
7.

Original comment by nandelb...@gmail.com on 5 Jun 2009 at 2:19

GoogleCodeExporter commented 9 years ago
settind the wireless card and MAC address manually...

root@bt:~/Desktop/tarball_staging# perl wepbuster

MODE: crack     (using: wlan0/mon0 == 00:02:72:6f:a2:f9)

Scanning channel 6 for WEP-enabled Access Points
............No such file or directory at wepbuster line 1220.

Original comment by nandelb...@gmail.com on 5 Jun 2009 at 2:21

GoogleCodeExporter commented 9 years ago
Here's something odd I noticed.  Running airmon-ng on ath0:

ath0        Atheros     madwifi-ng VAP (parent: wifi0) (VAP cannot be put in monitor 
mode)

Yet, when I run iwconfig, notice that it indicates that ath0 *is* running in 
monitor
mode.

ath0      IEEE 802.11g  ESSID:""  Nickname:""
          Mode:Monitor  Frequency:2.412 GHz  Access Point: 06:14:6C:E8:DD:14   
          Bit Rate:0 kb/s   Tx-Power:18 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Original comment by hoopyfro...@gmail.com on 5 Jun 2009 at 3:50

GoogleCodeExporter commented 9 years ago
On Comment 34:

You did not change the sources as according to the instructions found on the 
wiki

Original comment by markjays...@gmail.com on 5 Jun 2009 at 4:16

GoogleCodeExporter commented 9 years ago
On comment #35:

Try setting your wireless cards manually and make sure you read Troubleshooting 
in the wiki.. Change the 
necessary sources of aircrack-ng and recompile your aircrack.

Original comment by markjays...@gmail.com on 5 Jun 2009 at 4:18

GoogleCodeExporter commented 9 years ago
On comment #35

Try the Troubleshooting in the wiki. If still nothing.. create a new issue and 
answer the questions I have newly 
created.

Original comment by markjays...@gmail.com on 5 Jun 2009 at 4:45

GoogleCodeExporter commented 9 years ago
On Comment 36:

Sorry, but I already have changed the sources...

grep "if( time( NULL ) - tt1"  /pentest/wireless/aircrack-ng/src/airodump-ng.c
        if( time( NULL ) - tt1 >= 2 )

grep PTW_TRY_STEP /pentest/wireless/aircrack-ng/src/aircrack-ng.h
        define PTW_TRY_STEP    100

Original comment by nandelb...@gmail.com on 5 Jun 2009 at 6:01

GoogleCodeExporter commented 9 years ago
On comment #39

Try the Troubleshooting page in wiki..

There are couple of things you can do to verify if the program can actually run 
aircrack-ng programs... if all else 
fails, submit a new issue and answer the questions i just newly created..

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

GoogleCodeExporter commented 9 years ago
I modified this parameter:

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ grep 'my
$macaddress' wepbuster 
my $macaddress = '00:18:de:03:f4:2e';

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ grep 'my
$inject_iface' wepbuster 
my $inject_iface = 'wlan0';
my $inject_iface = shift;

ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ grep 'my
$monitor_iface' wepbuster 
my $monitor_iface = 'mon1';

------------------------------------------------------------------------
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"OW-WiFi"  Nickname:""
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:14:BF:AD:A1:2F   
          Bit Rate=54 Mb/s   Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Power Management:off
          Link Quality=64/100  Signal level=-68 dBm  Noise level=-92 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

vmnet1    no wireless extensions.

vmnet8    no wireless extensions.

mon0      IEEE 802.11g  Nickname:""
          Mode:Monitor  Frequency:2.437 GHz  Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

mon1      IEEE 802.11g  Nickname:""
          Mode:Monitor  Frequency:2.437 GHz  Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

mon2      IEEE 802.11g  Nickname:""
          Mode:Monitor  Frequency:2.437 GHz  Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

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

wepbuster - svn revision: 31
------------------------------------------------------------------------
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo perl 
wepbuster 

MODE: crack     (using: wlan0/mon1 == 00:18:de:03:f4:2e)

Scanning channel 6 for WEP-enabled Access Points
............Cannot open airodump output.

------
Thank you for support

Original comment by ulises2k on 5 Jun 2009 at 7:17

GoogleCodeExporter commented 9 years ago
There is no .csv file being created on the initial scan...  Once the program 
starts running, can you do a "ps ax 
|grep air" and check if you can run the command manually? I'm suspecting that 
you are using the airodump-ng 
that has not been modified so it will take at least 20 seconds for it to write 
the csv files. Your $scan_duration 
was set only to 6 seconds if i'm not mistaken... either you make sure that you 
are using the modified airodump-
ng or set the scan_duration and airodumpwait accordingly.

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

GoogleCodeExporter commented 9 years ago
I found the error.
Don't exec airodump-ng

I modifie line 1206

------------------------------------------------------------------------
if ($pid == 0){
  print "\nScanning channel $channel for WEP-enabled Access Points\n";

  `airodump-ng $monitor_iface -t wep -c  $channel -n -w $filename 2>&1`;
}
------------------------------------------------------------------------
by 
------------------------------------------------------------------------
  exec "airodump-ng $monitor_iface -t wep -c  $channel -n -w $filename 2>&1";
------------------------------------------------------------------------
And the error is:
-n parameter, it no valid option

Said this:
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo perl 
wepbuster 

MODE: crack     (using: wlan0/mon1 == 00:18:de:03:f4:2e)

Scanning channel 6 for WEP-enabled Access Points
airodump-ng: invalid option -- n
"airodump-ng --help" for help.
......Cannot open airodump output.

So,
The line 1206 is:
`airodump-ng $monitor_iface -t wep -c  $channel -w $filename 2>&1`;
without -n parameter

I use aircrack-ng 1.0rc3 (svn version) (svn rev: 1558)

My standar ouput is:
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ sudo perl 
wepbuster 

MODE: crack     (using: wlan0/mon1 == 00:18:de:03:f4:2e)

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 this file created:
ulises2k@black2k:~/programas/wepbuster/wepbuster-1.0_beta/trunk$ ls
prueba.air-01.cap  prueba.air-01.csv  prueba.air-01.kismet.csv 
prueba.air-01.kismet.netxml  README.TXT  wepbuster

THANK YOU for your help

Please,  commit this change to svn (without -n parameter)

Original comment by ulises2k on 5 Jun 2009 at 8:04

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
yeah,, somebody has reported that -n error in the support thread..  He said he 
was using BackTrack 4. Which 
one are you using? Because it might be unlikely that aircrack-ng will remove 
that option. Maybe BackTrack 4 
was customized to have limited options only for airodump.

Original comment by markjays...@gmail.com on 5 Jun 2009 at 8:17

GoogleCodeExporter commented 9 years ago

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