Set ADD_IP_ALIASES=No in all shorewall.conf files.

Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-02-02 08:16:41 -08:00
parent dd60f04a9f
commit ede17e2da0
6 changed files with 11 additions and 4 deletions

View File

@ -109,7 +109,7 @@ RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
IP_FORWARDING=Off
ADD_IP_ALIASES=Yes
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No

View File

@ -109,7 +109,7 @@ RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
IP_FORWARDING=On
ADD_IP_ALIASES=Yes
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No

View File

@ -116,7 +116,7 @@ RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
IP_FORWARDING=On
ADD_IP_ALIASES=Yes
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No

View File

@ -14,6 +14,8 @@ Changes in Shorewall 4.4.7
7) Fix case where MARK target is unavailable.
8) Change default to ADD_IP_ALIASES=No
Changes in Shorewall 4.4.6
1) Fix for rp_filter and kernel 2.6.31.

View File

@ -107,7 +107,7 @@ RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
IP_FORWARDING=On
ADD_IP_ALIASES=Yes
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No

View File

@ -178,6 +178,11 @@ Shorewall 4.4.7 RC 1
now, if the zone has <interface>:0.0.0.0/0 (even with exclusions),
then it may have no additional members in /etc/shorewall/hosts.
13) ADD_IP_ALIASES=No is now the setting in the released shorewall.conf
and in all of the samples. This will not affect you during upgrade
unless you choose to replace your current shorewall.conf with the
one from the release (not recommended).
----------------------------------------------------------------------------
P R O B L E M S C O R R E C T E D I N 4 . 4 . 7
----------------------------------------------------------------------------