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

Update release docs with shorewall-init start priority

Browse Source
This commit is contained in:
Tom Eastep 2010-06-21 13:41:37 -07:00
parent 31e95f0667
commit f4fb099047
3 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Shorewall/changelog.txt
View File

@ -1,5 +1,9 @@
Changes in Shorewall 4.4.10.1
1) Fix start priority of shorewall-init on Debian
Changes in Shorewall 4.4.10.1
1) Apply patch from Gabriel.
2) Fix IPSET match detection when a pathname is specified for IPSET.

7
Shorewall/known_problems.txt
View File

@ -19,3 +19,10 @@
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.
3) On Debian and derivatives, shorewall-init is starting too late.
To work around this issue, at a root prompt:
cd /etc/rcS.d
mv S38shorewall-init S08shorewall-init

7
Shorewall/releasenotes.txt
View File

@ -1,5 +1,5 @@
----------------------------------------------------------------------------
S H O R E W A L L 4 . 4 . 1 0
S H O R E W A L L 4 . 4 . 1 0 . 2
----------------------------------------------------------------------------
I. RELEASE 4.4 HIGHLIGHTS
@ -220,6 +220,11 @@ 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
4.4.10.1
1) The start priority of shorewall-init on Debian and Debian-based
distributions was previously too low, making it start too late.
4.4.10.1
1) The IPv6 allowBcast action generated an invalid rule.
2) If IPSET=<pathname> was specified in shorewall.conf, then when an