line 707: kill (<PID>) - No such process

[GoogleCodeExporter]

What steps will reproduce the problem?
1. ./autocrack4.0.sh
2.
3.

What is the expected output? What do you see instead?
First time trying it out, every time I try to run it I get the following:

root@bt:~# ./autocrack4.0.sh
It looks like you have festival installed, have you tried the tts option?
Using WiFi card:  eth1 Broadcom wl
scanning for wifi networks: %100
./autocrack4.0.sh: line 707: kill: (14142) - No such process
cat: temp-01.*: No such file or directory

Shutting down wifi cards, Please wait

What version of the product are you using? On what operating system?
Autocrack4.0 on BT4 R2

Please provide any additional information below.
Doesn't seem to make any difference which directory I place the script in 
either, have tried a few places and they all give the same output.

Original issue reported on code.google.com by OtisDrif...@gmail.com on 20 Sep 2011 at 1:57

[GoogleCodeExporter]

Please type in the following and post the output here for me.: 

sudo airmon-ng start eth1

Original comment by esmith2...@gmail.com on 20 Sep 2011 at 5:41

[GoogleCodeExporter]

Sorry, i didnt offer an explanation as to what is going on. The line that sais 
"kill: (14142) - No such process" is supose to kill airodump-ng, but that error 
suggests that it never opened. which suggest that it never put your wifi card 
in to moniter mode or was not able to get the name of your wifi card. I suspect 
that has to do with the way im trying to get the wifi card's name. I would 
still like the output of your manully placing your wifi card in to monitor 
mode. But id also like it if you could try to start my script like this: 
"./autocrack4.0.sh eth1" and tell me what happends

Original comment by esmith2...@gmail.com on 20 Sep 2011 at 5:48

[GoogleCodeExporter]

I have the same issue, backtrack 5.  Mine errors out on line 712 but it is the 
same thing, no such process / no such directory. putting my wlan0 into 
monitormode with airmon-ng first told me I had two processes named "dhclient3" 
running that could interfere so I killed them and put the wlan into monitormode 
manually with 'sudo airmon-ng start wlan0', which it then responded with:

interface     chipset     driver
wlan0         Zydas       zd1211rw - [phy0]SIOCSIFFLAGS: No such file or 
directory
                           (monitor mode enabled on mon0)

Tried running it again with "./autocrack4.0.sh wlan0" and "./autocrack4.0.sh 
mon0" but got the same error as esmith2 stated

Original comment by tomjenki...@gmail.com on 20 Sep 2011 at 9:35

[GoogleCodeExporter]

ok finally fixed it.  it had to do with the firmware not being installed.  
running "dmesg" gave some insight to that and then it was a googlefest to learn 
how to do that since linux is not my first language.  for anyone else with a 
zd1211rw based wireless, I got the firmware from: 
"http://sourceforge.net/projects/zd1211/files/latest"
Then extract it to a folder called "\lib\firmware\zd1211" (will have to create 
folder with that exact name).  Happily pentesting my home network without any 
of the tedious remembering of command line switches, thanks

Original comment by tomjenki...@gmail.com on 20 Sep 2011 at 11:17

[GoogleCodeExporter]

OKay so i was wrong about why it was happening. But i still fixed the a 
potential problem with the wifi card detection code in 4.1. I ran across this 
problem in kubuntu on the same laptop i used to code this script, i dismissed 
the error as having something to do with running off a live CD.

Im still waiting on the OP to give me the requested information before i close 
this problem out. 

Original comment by esmith2...@gmail.com on 20 Sep 2011 at 11:57

[GoogleCodeExporter]

I apologize for the delay in getting back to you, here is the output from 
airmon.:

root@bt:~/scripts/autocrack# airmon-ng start eth1

Interface       Chipset         Driver

eth1            Broadcom                wl (monitor mode enabled)

And here is the output from running ./autocrack4.0.sh eth1

root@bt:~/scripts/autocrack# ./autocrack4.0.sh eth1
It looks like you have festival installed, have you tried the tts option?
eth1
scanning for wifi networks: %100
./autocrack4.0.sh: line 707: kill: (10155) - No such process
cat: temp-01.*: No such file or directory

Shutting down wifi cards, Please wait

Tried newest version 4.3 with the following output:
root@bt:~/scripts/autocrack# ./autocrack4.3.sh
It looks like you have festival installed, have you tried the tts option?
Using WiFi card:  eth1 Broadcom wl
scanning for wifi networks: %100
./autocrack4.3.sh: line 718: kill: (11071) - No such process
cat: temp-01.*: No such file or directory

Shutting down wifi cards, Please wait
root@bt:~/scripts/autocrack# ./autocrack4.3.sh eth1
It looks like you have festival installed, have you tried the tts option?
eth1
scanning for wifi networks: %100
./autocrack4.3.sh: line 718: kill: (11596) - No such process
cat: temp-01.*: No such file or directory

Shutting down wifi cards, Please wait

Appears to have made no difference on my hardware. This could be an issue on my 
end as I know these broadcom cards have been notoriously a pain in the ass when 
it comes to monitor and injection. I will try to do some deeper digging on my 
end to see if I can correct any issues here. It may or may not matter but I 
will mention as well that I am running my BT4 R2 from a persistent live boot 
usb. Not sure if that is relevant or not but it may be. Thanks.

Original comment by OtisDrif...@gmail.com on 21 Sep 2011 at 1:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Running airodump by itself may be point me in the right direction:

root@bt:~/scripts/autocrack# airodump-ng -w temp eth1
ioctl(SIOCSIWMODE) failed: Invalid argument

ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead.  Make
sure RFMON is enabled: run 'airmon-ng start eth1 <#>'
Sysfs injection support was not found either.

It seems that because my system sees my wireless card as "eth1" and not 
something like "wlan1" it is seeing it as an ethernet connection and not an 
actual wireless connection which is making airodump fail to load it. Not 100% 
sure this is the case though because iwconfig definitely shows eth1 as an 
802.11 connection:

root@bt:~/scripts/autocrack# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Bit Rate:72 Mb/s   Tx-Power:24 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Managementmode:All packets received
          Link Quality=5/5  Signal level=0 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

Interestingly enough though ifconfig shows it as Ethernet:

root@bt:~/scripts/autocrack# ifconfig
eth0      Link encap:Ethernet  HWaddr f0:**:**:**:**:**
          inet addr:192.168.200.155  Bcast:192.168.200.255  Mask:255.255.255.0
          inet6 addr: fe80::f24d:a2ff:fead:2c12/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11997 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2146 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2894790 (2.8 MB)  TX bytes:471352 (471.3 KB)
          Interrupt:17

eth1      Link encap:Ethernet  HWaddr 1c:**:**:**:**:**
          inet6 addr: fe80::1e65:9dff:fe8b:b9dd/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2100 (2.1 KB)  TX bytes:2100 (2.1 KB)

Original comment by OtisDrif...@gmail.com on 21 Sep 2011 at 1:43

[GoogleCodeExporter]

More digging looks like the problem is indeed with my computer and not with 
your script. I was misled about exactly which card my laptop had installed and 
it now seems that my card may not be capable of doing anything more than 
connecting to a network. I had originally thought I had a Broadcom BCM4313 chip 
(which has nice drivers and support) by the output from an lspci:

root@bt:/usr/bin# lspci | grep -i net
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 
01)

However dmesg tells a different story. It shows a Broadcom BCM4727 which is 
really only capable of connecting to networks and nothing more. 

root@bt:/usr/bin# dmesg | grep -e wl -e eth
eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.38

So at this point I am not 100% certain which chip I actually have but I am 
going to assume the worst until I am certain. I apologize if I have 
unnecessarily taken up any of your time on this. I have a wireless dongle I 
will try later this week and see if it works. Thank you for all of your work 
and keep up the good work!

Original comment by OtisDrif...@gmail.com on 21 Sep 2011 at 2:27

[GoogleCodeExporter]

Thanks for the reply. And yes i agree that it might be your wifi card - or your 
drivers installed as i have seen this problem before on the laptop i use in 
programming this script - when i tried installing kubuntu. Try either a 
different distribution or a different wifi card. If your using KDE version of 
backtrack try the gnome version.  

And you don't need to apologize for anything - my favorite part of programming 
is debugging :)  

Status updated to Done. 

Original comment by esmith2...@gmail.com on 22 Sep 2011 at 8:30

• Changed state: Done
• Added labels: Type-Task
• Removed labels: Type-Defect