diff --git a/docs/upgrade_issues.xml b/docs/upgrade_issues.xml index be0b3f66d..4216dc37d 100644 --- a/docs/upgrade_issues.xml +++ b/docs/upgrade_issues.xml @@ -35,7 +35,7 @@ Thomas M. Eastep - + @@ -111,6 +111,89 @@ /var/lib/shorewall[6][-lite]/interface.status files used by SWPING and by LSM. + + + Beginning with Shorewall 4.5.2, using /etc/shorewall-lite/vardir + and /etc/shorewall6-lite/vardir to specify VARDIR is deprecated in + favor of the VARDIR setting in shorewallrc. + + NOTE: While the name of the variable remains VARDIR, the meaning + is slightly different. When set in shorewallrc, each product + (shorewall-lite, and shorewall6-lite) will create a directory under + the specified path name to hold state information. + + Example: + +
+ VARDIR=/opt/var/ + + The state directory for shorewall-lite will be + /opt/var/shorewall-lite/ and the directory for shorewall6-lite will + be /opt/var/shorewall6-lite. +
+ + When VARDIR is set in /etc/shorewall[6]/vardir, the product will + save its state directly in the specified directory. +
+ + + Begining with Shorewall 4.5.6, the tcrules file is processed if + MANGLE_ENABLED=Yes, independent of the setting of TC_ENABLED. This + allows actions like TTL and TPROXY to be used without enabling traffic + shaping. If you have rules in your tcrules file that you only want + processed when TC_ENABLED is other than 'No', then enclose them + in + +
+ ?IF $TC_ENABLED + + ... + + ?ENDIF +
+ + If they are to be processed only if TC_ENABLED=Internal, then + enclose them in + +
+ ?IF TC_ENABLED eq 'Internal' + + ... + + ?ENDIF. +
+ + +
+ + + Beginning with Shorewall 4.5.7, the deprecated + /etc/shorewall[6]/blacklist files are no longer installed. Existing + files are still processed by the compiler. + + Note that blacklist files may be converted to equivalent blrules + files using shorewall[6] update -b. + + + + In Shorewall 4.5.7, the + /etc/shorewall[6]/notrack file was renamed + /etc/shorewall[6]/conntrack. When upgrading to a + release >= 4.5.7, the conntrack file will be + installed along side of an existing notrack file. + When both files exist, a compiler warning is generated: + +
+ WARNING: Both /etc/shorewall/notrack and + /etc/shorewall/conntrack exist; /etc/shorewall/conntrack is + ignored +
+ + This warning may be eliminated by moving any entries in the + notrack file to the + conntrack file and removing the + notrack file. +