Great script - I'm learning a lot from it.
Use a consistent symbol for the "proceed" menu option (currently every number from 3 to 9 is used!).
Use airmon-zc. This will fix existing problems with airmon-ng for certain NICs, especially Intel. I don't think it introduces any new problems.
For "Blackhole", its useful to default to something tempting when no probes are received eg
With "Wireless Vacuum", I believe we will always enable kernel forwarding. Therefore this should be set automatically by the script, so the user doesn't need to navigate to a different menu.Code:xterm -bg black -fg grey -sb -rightbar -title "Blackhole AP" -e airbase-ng -v -e "Free Public WiFi" -c $sac -P -C 60 $pii &
With ARPSpoof, it would be handy to see the routing info before filling in the variables eg ip route show.
Ferret doesn't execute, needs the absolute path (/pentest/sniffers/hamster/ferret) adding to the script.
There's a lot of mess (processes, interfaces etc) left behind after exit. Both yamas and easy-creds clean up nicely.
I do not see segmentation faults with airbase BT5R1 gnome 32, although it very occasionally stops responding. I have even successfully run SSLStrip through at0!
Nmap 5.61-bt0 does not work:
Fortunately autoscan, netifera, p0f, metasploit scanners and nessus all work perfectly on at0.Code:rooroot@bt:~# nmap -T4 -F 192.168.10.100 Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-23 23:00 EST route_dst_netlink: can't find interface "at0" root@bt:~# nmap -T4 -F 192.168.10.100 -e at0 Starting Nmap 5.61TEST2 ( http://nmap.org ) at 2011-12-23 20:43 EST I cannot figure out what source address to use for device at0, does it even exist? QUITTING!
I'm a long way behind you on the Bash learning curve. You have probably already considered all the above, but it would be interesting to hear your thoughts.