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

Clarify physical naming rules and '+'

Browse Source
This commit is contained in:
Tom Eastep 2009-11-10 15:25:25 -08:00
parent bf8c38e054
commit bd9c651961
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Shorewall/releasenotes.txt
View File

@ -247,10 +247,10 @@ None.
p1023), you write it as y1023; Shorewall will translate that name
to p1023 when needed.
As shown in the above example, 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 is, if the logical name ends in
'+' then the physical name must also end in '+'.
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
is, if the logical name ends in '+' then the physical name must
also end in '+'.
4) Previously, Shorewall has used the character '2' to form the name
of chains involving zones and/or the word 'all' (e.g., fw2net,
@ -261,7 +261,7 @@ None.
ZONE2ZONE has a default value of "2" but can also be given the
value "-" (e.g., ZONE2ZONE="-") which causes Shorewall to separate
the two parts of the name with a hyphen (e.g., foo123-bar).
----------------------------------------------------------------------------
N E W F E A T U R E S I N 4 . 4 . 0
----------------------------------------------------------------------------