Clarify 'ipsec' hosts file option

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1727 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-10-26 14:48:21 +00:00
parent 73915885a4
commit dce7281692
3 changed files with 16 additions and 4 deletions

View File

@ -117,4 +117,7 @@ Changes since 2.0.3
56) Fix typo in check_config() 56) Fix typo in check_config()
27) Allow outgoing NTP responses in action.AllowNTP. 57) Allow outgoing NTP responses in action.AllowNTP.
58) Clarification of the 'ipsec' hosts file option.

View File

@ -129,7 +129,11 @@
# NEWNOTSYN=Yes. # NEWNOTSYN=Yes.
# #
# ipsec - The zone is accessed via a # ipsec - The zone is accessed via a
# kernel 2.6 ipsec SA. # kernel 2.6 ipsec SA. Note that if the
# zone named in the ZONE column is
# specified as an IPSEC zone in the
# /etc/shorewall/ipsec file then you do NOT
# need to specify the 'ipsec' option here.
# #
#ZONE HOST(S) OPTIONS #ZONE HOST(S) OPTIONS
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS LINE -- DO NOT REMOVE #LAST LINE -- ADD YOUR ENTRIES BEFORE THIS LINE -- DO NOT REMOVE

View File

@ -1,4 +1,4 @@
Shorewall 2.2.0-Beta1 Shorewall 2.2.0-Beta2
---------------------------------------------------------------------- ----------------------------------------------------------------------
Problems Corrected since 2.0.3 Problems Corrected since 2.0.3
@ -105,6 +105,11 @@ Problems corrected since 2.2.0 Beta 1.
2) The AllowNTP standard action now allows outgoing responses to 2) The AllowNTP standard action now allows outgoing responses to
broadcasts. broadcasts.
3) A clarification has been added to the hosts file's description of
the 'ipsec' option pointing out that the option is redundent if the
zone named in the ZONE column has been designated an IPSEC zone in
the /etc/shorewall/ipsec file.
----------------------------------------------------------------------- -----------------------------------------------------------------------
Issues when migrating from Shorewall 2.0 to Shorewall 2.1: Issues when migrating from Shorewall 2.0 to Shorewall 2.1: