forked from extern/shorewall_code
Clarify physical naming rules and '+'
This commit is contained in:
parent
bf8c38e054
commit
bd9c651961
@ -247,10 +247,10 @@ None.
|
|||||||
p1023), you write it as y1023; Shorewall will translate that name
|
p1023), you write it as y1023; Shorewall will translate that name
|
||||||
to p1023 when needed.
|
to p1023 when needed.
|
||||||
|
|
||||||
As shown in the above example, It is allowed to have a physical
|
It is allowed to have a physical name ending in '+' with a logical
|
||||||
name ending in '+' with a logical name that does not end with '+'.
|
name that does not end with '+'. The reverse is not allowed; that
|
||||||
The reverse is not allowed; that is, if the logical name ends in
|
is, if the logical name ends in '+' then the physical name must
|
||||||
'+' then the physical name must also end in '+'.
|
also end in '+'.
|
||||||
|
|
||||||
4) Previously, Shorewall has used the character '2' to form the name
|
4) Previously, Shorewall has used the character '2' to form the name
|
||||||
of chains involving zones and/or the word 'all' (e.g., fw2net,
|
of chains involving zones and/or the word 'all' (e.g., fw2net,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user