Usage Options --
        -2 <2nd string used to fine-tune FILTER>
        -A Adds a new set of rules to the current rules; the default behavior (without -A) is to clear out all the old bam rules 
                - could be handy if the attack moves or covers multiple IPs
        -a <ip> - add an ip address to the badguys list
        -D Disable - this will turn the bam rules off without deleting them all
        -d <ip under attack> 
        -E (Re)Enable: If you've already disabled rules but they're still in place, this will re-enable them
        -e Execute - without this flag set you'll see the rules that would be created, but none are actually created
	-F Flush and clear all bam rules
        -p [port] (optional - default 80)
        -C Clear conntracks with conntrack -D -d 
        -L <accepts a number and will allow that number/sec hits to the badguys chain before blocking for good
	-N <connection limit> - limit the number of parallel connection by IP ; to prevent blocking valid traffic this has been hard set to 10
	-l Be less aggressive; this will limit badguys instead of outright blocking them
        -W Creates the whitelist in /proc/net/xt_recent/goodguys to prevent known bots/Guard/local ips/ HG from getting blocked, then exits. 
                (When using -e, -W is not necessary because it will create the whitelist as a normal part of creating rules).
        -w <ip> - remove an ip from the badguys list and whitelist it
        -R <new limit> Sets the number of ips the recent module can handle
        -S SYN flood protection (experimental-does not work-DO NOT USE)
        -s <content to filter> 
	-T <seconds> an IP will only be blocked when the address is in the badlist and was seen within the last given number of seconds. (default 600 = 10 min)

	    Example: ./bam.sh -d 123.123.123.123 -s asdf.com -e(This would block all traffic to 123123123 for the domain asdf.com)"
