holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Clean up release notes

Browse Source
This commit is contained in:
Tom Eastep 2009-11-16 15:21:11 -08:00
parent 9d5dd2ad3a
commit c4bfab29a5
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
Shorewall/releasenotes.txt
View File

@ -230,8 +230,8 @@ None.
z1 br0:p+ z1 br0:p+
z2 br1:p+ z2 br1:p+
That is because the Shorewall implementation requires each bridge This error occurs because the Shorewall implementation requires
port to have a unique name. that each bridge port must have a unique name.
To work around this problem, a new 'physical' interface option has To work around this problem, a new 'physical' interface option has
been created. The above configuration may be defined using the been created. The above configuration may be defined using the
@ -252,13 +252,13 @@ None.
to p1023 when needed. to p1023 when needed.
It is allowed to have a physical name ending in '+' with a logical It is allowed to have a physical name ending in '+' with a logical
name that does not end with '+'. The reverse is not allowed; that name that does not end with '+'. The reverse is not allowed; if the
is, if the logical name ends in '+' then the physical name must logical name ends in '+' then the physical name must also end in
also end in '+'. '+'.
This feature is not restricted to bridge ports. Beginning with this This feature is not restricted to bridge ports. Beginning with this
release, the interface name in the INTERFACE column can be release, the interface name in the INTERFACE column can be
considered a logical name for the interface where the actual considered a logical name for the interface, and the actual
interface name is specified using the 'physical' option. If no interface name is specified using the 'physical' option. If no
'physical' option is present, then the physical name is assumed to 'physical' option is present, then the physical name is assumed to
be the same as the logical name. As before, the logical interface be the same as the logical name. As before, the logical interface
@ -275,9 +275,9 @@ None.
value "-" (e.g., ZONE2ZONE="-") which causes Shorewall to separate value "-" (e.g., ZONE2ZONE="-") which causes Shorewall to separate
the two parts of the name with a hyphen (e.g., foo123-bar). the two parts of the name with a hyphen (e.g., foo123-bar).
5) Only one instance of this warning is now generated; previously, one 5) Only one instance of the following warning is now generated;
instance of a similar warning was generated for each COMMENT previously, one instance of a similar warning was generated for
encountered. each COMMENT encountered.
COMMENTs ignored -- require comment support in iptables/Netfilter COMMENTs ignored -- require comment support in iptables/Netfilter
@ -290,7 +290,7 @@ None.
Example: Example:
net => loc DROP using chain net2loc net => loc DROP using chain net2all
Note that implicit intrazone ACCEPT policies are not displayed for Note that implicit intrazone ACCEPT policies are not displayed for
zones associated with a single network where that network zones associated with a single network where that network
@ -311,7 +311,7 @@ None.
The new packages are: The new packages are:
- Shorewall. Includes the former Shorewall-common and - Shorewall. Includes the former Shorewall-common and
Shorewall-perl packages. Has everything needed Shorewall-perl packages. Includes everything needed
to create an IPv4 firewall. to create an IPv4 firewall.
Shorewall-shell is no longer available. Shorewall-shell is no longer available.