Fix regression regarding IPSET=<pathname>

Signed-off-by: Tom Eastep <teastep@shorewall.net>

Shorewall/changelog.txt

@@ -2,6 +2,8 @@ Changes in Shorewall 4.4.10.1
 
 1)  Apply patch from Gabriel.
 
+2)  Fix IPSET match detection when a pathname is specified for IPSET.
+
 Changes in Shorewall 4.4.10
 
 1)  Fix regression with scripts.

Shorewall/known_problems.txt

@@ -1,3 +1,21 @@
 1)  The IPv6 allowBcast built-in action generates an invalid ip6tables
     rule. This defect is present in all versions of Shorewall that 
     support IPv6.
+
+    Fixed in Shorewall 4.4.10.1.
+
+2)  If IPSET=<pathname> is specified in shorewall.conf, then when an
+    ipset is used in a configuration file entry, the following fatal
+    compilation error occurs:
+
+    ERROR: ipset names in Shorewall configuration files require Ipset
+    Match in your kernel and iptables : /etc/shorewall/rules (line nn)
+
+    You can work around this problem by executing the following at a
+    root shell prompt:
+
+    	 shorewall show -f capabilities > /etc/shorewall/capabilities
+
+    Fixed in Shorewall 4.4.10.1. After installing this fix, if you 
+    executed the above command to work around the problem, we recommend
+    that you remove /etc/shorewall/capabilities.

Shorewall/releasenotes.txt

@@ -222,6 +222,17 @@ I I I.  P R O B L E M S   C O R R E C T E D   I N   T H I S  R E L E A S E
 
 1)  The IPv6 allowBcast action generated an invalid rule.
 
+2)  If IPSET=<pathname> was specified in shorewall.conf, then when an
+    ipset was used in a configuration file entry, the following
+    fatal compilation error occurred:
+
+    ERROR: ipset names in Shorewall configuration files require Ipset
+    Match in your kernel and iptables : /etc/shorewall/rules (line nn)
+
+    If you applied the workaround given in the "Known Problems", then
+    you should remove /etc/shorewall/capabilities after installing
+    this fix.
+
 4.4.10
 
 1)  Startup Errors (those that are detected before the state of the