While setting varribles "INJECTRATE="400"", why not a deauth and reauth varriable also?

Nice script. I like your approch.

Nice job. That is usefull for those who have problem with aireplay and are unsure of what the can do to investigate further.

Yes, if mac-filtering is in use.

If you still have your ISO just boot it and copy the original file back to your hardrive, over writing the altered file.

You could use a scipt for your rules. Just input your ip_table rules.
#!/bin/bash
# Control IPTABLE rules

# path to iptable
IPTABLE_PATH=/bin

# set interface
IFACE=eth0

I am no sure if this is relavent but, aircrack-ng has patched aimon.sh to enable monitor mode through the script.

You could try john -i:all -f=NT hashes.txt for an incremental attack.

I would start by makeing sure my kernel source is ready...
cd /usr/src/linux
make cloneconfig
make prepare
Then I would untar the driver in /usr/src and build them from there.

Did your make, make install finnish without errors?

Here is a nice tutorial on that exact subject posted by Irongeek. http://www.irongeek.com/i.php?page=CamStudioOSS/camstudio

Look to my previous post for an alternative. The hermes chipset does not support packet injection/deauth (ie aireplay). The broadcom driver project seems to be comming along in those areas though.

You may look over these links for help since you have already done the HD install...
http://www.linuxquestions.org/linux/answers/Networking/ORINOCO_MONITOR_and_KISMET_HOWTO
or ...

Does iwpriv eth1 list monitor mode? I think you should roll back your firmware for better support.

Did you add this hot fix to your iso? http://www.remote-exploit.org/orinoco-fix.mo

Can you post the cardctl ident output? Void 11 is only supported be prism 2.5 chipset cards. The alias wlan0 is seen when the hostap_cs drivers are loaded... I belive the drivers you are uesing...

Hermes based cards should be ethX. Check you dmesg and or lsmod to see which drives are loaded for yor wireless card.

Looks like it is the card bus that is giving you a problem. You could try what is mentioned in this link.

Post you lspci for us to look at please.

This may do for you. I do not think it will be much diffrent with HDD install... I wonder if you can get it back into a cdrw? http://slax.linux-live.org/forum/viewtopic.php?t=6158&highlight=remaster

Thses patches here maybe useful to get madwifi-ng working correctly. http://tinyshell.be/aircrackng/download/patches.tar.gz

Read the USER DOCS.

The madwifi-ng project use diffrent syntax/commands. You must first destroy the original int by wlanconfig ath0 destroy, then wlanconfig ath0 create wlandev wifi0 wlanmode monitor, and finnaly...

This maybe of some intrest to someone.If someone trys this please report back. ;)
source: http://www.netstumbler.org/showthread.php?t=19063

This version of kismet does not support madwifi-ng...It is only supported by going to the download page and building via subversion....