extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-24 23:28:59 +01:00
Code Issues Packages Projects Releases Wiki Activity

Remove noah from migration issues (it was implemented in 3.2.9); add /etc/shorewall/params change to migration issues

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5371 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-02-08 16:19:45 +00:00
parent 46c20dacfc
commit 5afa06ef74
1 changed files with 26 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
Shorewall/releasenotes.txt
View File

@ -39,9 +39,10 @@ Other Changes in 3.4.0 RC 1
1) In spite of my claim that I would not introduce any changes other
than bug fixes in a release candidate, I'm going to do so anyway.
Beginning with Shorewall 3.4.0, Shorewall will only process
Beginning with Shorewall 3.4.0 RC2, Shorewall will only process
/etc/shorewall/params during the compile phase. Any shell variables
needed at run-time must be set in /etc/shorewall/init.
needed at run-time by your extension scripts must be set in
/etc/shorewall/init.
In a Shorewall/Shorewall Lite environment, this allows
/etc/shorewall/params to be written to run exclusively
@ -146,10 +147,29 @@ http://www.shorewall.net/pub/shorewall/3.2/shorewall-3.2.8/releasenotes.txt
/etc/shorewall-lite/shorewall-lite.conf. When you upgrade,
your shorewall.conf file will be renamed shorewall-lite.conf.
6) Previously, 'ipsecnat' tunnels allowed AH traffic by default
(unless 'isecnat:noah' was given). Given that AH is incompatible
with nat-traversal, 'ipsecnat' now implies 'ipsecnat:noah' and the
latter is now redundant.
6) This issue only applies if you set shell variables in
/etc/shorewall/params.
Beginning with Shorewall 3.4.0, Shorewall will only process
/etc/shorewall/params during the compile phase. Any shell variables
needed at run-time by your extension scripts must be set in
/etc/shorewall/init.
In a Shorewall/Shorewall Lite environment, this allows
/etc/shorewall/params to be written to run exclusively
on the administrative system while /etc/shorewall/init runs
exclusively on the firewall system.
So shell variables required at compile time may be set in
/etc/shorewall/params and those required at run-time may be set in
/etc/shorewall/init.
As part of this change, extra white space is no longer removed from
/etc/shorewall/params as it was in RC1.
The /etc/shorewall/compile extension script introduced in Shorewall
3.2.9 will continue to be supported but its use is deprecated since
it now performs the same function as /etc/shorewall/params.
New Features in Shorewall 3.4: