From 02d988851300e0cd2a3b1b028c3c9639a5f1e8e1 Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Thu, 10 Sep 2009 14:56:39 -0700 Subject: [PATCH] Document ipsec4/6 --- manpages/shorewall-zones.xml | 4 ++-- manpages6/shorewall6-zones.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/manpages/shorewall-zones.xml b/manpages/shorewall-zones.xml index 17a7ef65c..c909fc6fe 100644 --- a/manpages/shorewall-zones.xml +++ b/manpages/shorewall-zones.xml @@ -112,7 +112,7 @@ c:a,b ipv4 Where an ipsec zone is explicitly included as a child of an ipv4 zone, the ruleset allows CONTINUE - policies (explicit or implicit) to work as expected. + policies (explicit or implicit) to work as expected. In the future, Shorewall may make additional use of nesting information. @@ -138,7 +138,7 @@ c:a,b ipv4 - ipsec + ipsec (or ipsec4) Communication with all zone hosts is encrypted. Your diff --git a/manpages6/shorewall6-zones.xml b/manpages6/shorewall6-zones.xml index 0fb8bd040..bc4a36372 100644 --- a/manpages6/shorewall6-zones.xml +++ b/manpages6/shorewall6-zones.xml @@ -138,7 +138,7 @@ c:a,b ipv6 - ipsec + ipsec (or ipsec6) Communication with all zone hosts is encrypted. Your @@ -160,7 +160,7 @@ c:a,b ipv6 - bport (or bport6) + bport (or bport6) The zone is associated with one or more ports on a