holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Fix regression regarding IPSET=<pathname>

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-06-17 09:21:31 -07:00
parent 30f4e98fce
commit e61cf043eb
3 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

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

18
Shorewall/known_problems.txt
View File

@ -1,3 +1,21 @@
1) The IPv6 allowBcast built-in action generates an invalid ip6tables 1) The IPv6 allowBcast built-in action generates an invalid ip6tables
rule. This defect is present in all versions of Shorewall that rule. This defect is present in all versions of Shorewall that
support IPv6. 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.

11
Shorewall/releasenotes.txt
View File

@ -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. 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 4.4.10
1) Startup Errors (those that are detected before the state of the 1) Startup Errors (those that are detected before the state of the