Update release notes for backported shorewall-init fixes.

Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-08-08 07:25:16 -07:00
parent 6f1cbe45c0
commit 00d0b20181
2 changed files with 13 additions and 8 deletions

View File

@ -3,6 +3,10 @@ Changes in Shorewall 4.4.11.2
1) Correct typo that caused hang after executing a stop, reset or
clear command in Shorewall6 lite.
2) Correct typo in Shorewall/install.sh
3) Backport Shorewall-init fixes from 4.4.12.
Changes in Shorewall 4.4.11.1
1) Fix IPv6 shorecap program.

View File

@ -228,6 +228,13 @@ 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
2) A typo in the Shorewall install.sh script prevented the Makefile from
being installed in /usr/share/shorewall/configfiles/Makefile.
3) A number of problems associated with Shorewall-init and Upstart
have been corrected.
If you use Shorewall-init, then when upgrading to this version, be
sure to recompile all firewall scripts before you take interfaces
down or reboot.
4.4.11.1
1) Previously, the Shoreall6-lite version of shorecap was using
@ -305,14 +312,8 @@ 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
I V. K N O W N P R O B L E M S R E M A I N I N G
----------------------------------------------------------------------------
1) On systems that use the Upstart init system (such as Ubuntu and
Fedora), Shorewall-init is not reliable at starting the firewall
during boot when normal firewall startup is disabled and UPDOWN=1
is specified in /etc/default/shorewall-init.
Suggested workaround is to not disable normal startup (e.g., do not
set startup=0 on Debian-based systems and do not 'checkconfig
--del...' on Fedora).
1) On systems running Upstart, Shorewall-init cannot reliably close
the firewall before interfaces come up.
----------------------------------------------------------------------------
V. N E W F E A T U R E S I N T H I S R E L E A S E