diff --git a/Shorewall-docs2/Documentation.xml b/Shorewall-docs2/Documentation.xml index acf2198c0..4dede14af 100644 --- a/Shorewall-docs2/Documentation.xml +++ b/Shorewall-docs2/Documentation.xml @@ -3892,6 +3892,19 @@ all all tcp ftp-data - 8 + + + + + Prior to Shorewall version 2.2.3, the contents of the + /etc/shorewall/routestopped file did NOT affect + connection attempts occuring during the processing of the + shorewall start and shorewall + restart commands. Beginning with version 2.2.3, Shorewall + allows connections defined by the contents of + /etc/shorewall/routestopped during the potentially + lengthy processing of those commands. +
@@ -4020,6 +4033,17 @@ eth1 - Revision History + + 1.24 + + 2005-03-15 + + TE + + Update for use of /etc/shorewall/routestopped during + [re]start. + + 1.23 diff --git a/Shorewall-docs2/Shorewall_and_Aliased_Interfaces.xml b/Shorewall-docs2/Shorewall_and_Aliased_Interfaces.xml index 831c36b74..574768996 100644 --- a/Shorewall-docs2/Shorewall_and_Aliased_Interfaces.xml +++ b/Shorewall-docs2/Shorewall_and_Aliased_Interfaces.xml @@ -15,7 +15,7 @@ - 2002-02-07 + 2005-03-17 2001-2005 @@ -123,6 +123,17 @@ esac RedHat systems also allow adding such aliases from the network administration GUI (which only works well if you have a graphical environment on your firewall). + + On Debian and LEAF/Bering systems, it is as simple as adding the + command to the interface definition as follows: + + # Internet interface +auto eth0 +iface eth0 inet static + address 206.124.146.176 + netmask 255.255.255.0 + gateway 206.124.146.254 + up ip addr add 206.124.146.178/24 brd 206.124.146.255 dev eth0 label eth0:0