DOC: Changelog for shorewall-ipset-proto6.conf + adjusted its description

ChangeLog

@@ -37,7 +37,10 @@ ver. 0.9.3 (2015/XX/XXX) - wanna-be-released
      opening a closed port by swapping blocktype and returntype
    * New filters:
      - froxlor-auth  Thanks Joern Muehlencord
-     - apache-pass - filter Apache access log for successfull authentication
+     - apache-pass - filter Apache access log for successful authentication
+   * New actions:
+     - shorewall-ipset-proto6 - using proto feature of the Shorewall. Still requires
+	   manual pre-configuration of the shorewall. See the action file for detail.
    * New jails:
      - pass2allow-ftp - allows FTP traffic after successful HTTP authentication
 

config/action.d/shorewall-ipset-proto6.conf

@@ -5,33 +5,35 @@
 # This is for ipset protocol 6 (and hopefully later) (ipset v6.14).
 # for shorewall
 #
-# Use this setting in jail.conf to modify the name and the max time in every jain
+# Use this setting in jail.conf to modify use this action instead of a
-# action   = shorewall-ipset-proto6[name=SSH, bantime=10000]
+# default one
+#
+# banaction   = shorewall-ipset-proto6
 #
 # This requires the program ipset which is normally in package called ipset.
 #
-# IPset was a feature introduced in the linux kernel 2.6.39 and 3.0.0 kernels.
+# IPset was a feature introduced in the linux kernel 2.6.39 and 3.0.0
+# kernels, and you need Shorewall >= 4.5.5 to use this action.
 #
 # The default Shorewall configuration is with "BLACKLISTNEWONLY=Yes" (see
 # file /etc/shorewall/shorewall.conf). This means that when Fail2ban adds a
 # new shorewall rule to ban an IP address, that rule will affect only new
-# connections. So if the attempter goes on trying using the same connection
+# connections. So if the attacker goes on trying using the same connection
 # he could even log in. In order to get the same behavior of the iptable
 # action (so that the ban is immediate) the /etc/shorewall/shorewall.conf
 # file should me modified with "BLACKLISTNEWONLY=No".
 #
-# The use in IPset in shorewall depends of the version you must have at least 4.5.5< version
-# of shorewall
 #
-# Enable shorewall to use a blacklist using iptables creating a file /etc/shorewall/blrules
+# Enable shorewall to use a blacklist using iptables creating a file
-# and adding "DROP     net:+f2b-ssh    all" one for every jail details in shorewall documentation blacklist.
+# /etc/shorewall/blrules and adding "DROP net:+f2b-ssh all" and
-# To enable restore you ipset You must set SAVE_IPSETS=Yes in shorewall.conf
+# similar lines for every jail.  To enable restoring you ipset you
-# Is importan to read this documentation from shorewall http://shorewall.net/ipsets.html
+# must set SAVE_IPSETS=Yes in shorewall.conf .  You can read more
+# about ipsets handling in Shorewall at http://shorewall.net/ipsets.html
 #
-# To force create the ipset in the case that somebody delete the ipset create a file
+# To force creation of the ipset in the case that somebody deletes the
-# /etc/shorewall/initdone and add one line for every ipset (this files are in Perl)
+# ipset create a file /etc/shorewall/initdone and add one line for
-# take care of add 1; at the end of the file
+# every ipset (this files are in Perl) and add 1 at the end of the file.
-# the example is:
+# The example:
 # system("/usr/sbin/ipset -quiet -exist create f2b-ssh hash:ip timeout 600 ");
 # 1;
 #
@@ -40,7 +42,6 @@
 # system("/usr/sbin/ipset -quiet destroy f2b-ssh ");
 # 1; # This must go to the end of the file if not shorewall compilation fails
 #
-#
 
 
 [Definition]