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

Update my shorewall version in 'myfiles' and update location of actions in FAQ

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1848 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-12-23 22:28:58 +00:00
parent 0f7c148b89
commit 91145626ef
2 changed files with 17 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Shorewall-docs2/FAQ.xml
View File

@ -17,7 +17,7 @@
</author>
</authorgroup>
<pubdate>2004-12-12</pubdate>
<pubdate>2004-12-22</pubdate>
<copyright>
<year>2001-2004</year>
@ -484,10 +484,10 @@ to debug/develop the newnat interface.</programlisting></para>
and later). The default Shorewall setup invokes the <emphasis
role="bold">Drop</emphasis> action prior to enforcing a DROP policy and
the default policy to all zone from the internet is DROP. The Drop
action is defined in <filename>/etc/shorewall/action.Drop</filename>
which in turn invokes the <emphasis role="bold">RejectAuth</emphasis>
action (defined in
<filename>/etc/shorewall/action.RejectAuth</filename>). This is
action is defined in
<filename>/usr/share/shorewall/action.Drop</filename> which in turn
invokes the <emphasis role="bold">RejectAuth</emphasis> action (defined
in <filename>/usr/share/shorewall/action.RejectAuth</filename>). This is
necessary to prevent outgoing connection problems to services that use
the <quote>Auth</quote> mechanism for identifying requesting users. That
is the only service which the default setup rejects.</para>
@ -2013,6 +2013,16 @@ Verifying Configuration...
<title>Revision History</title>
<para><revhistory>
<revision>
<revnumber>1.39</revnumber>
<date>2004-12-22</date>
<authorinitials>TE</authorinitials>
<revremark>Correct action directory name if FAQ 4.</revremark>
</revision>
<revision>
<revnumber>1.39</revnumber>

4
Shorewall-docs2/myfiles.xml
View File

@ -43,12 +43,12 @@
address. If you have just a single public IP address, most of what you
see here won't apply to your setup so beware of copying parts of this
configuration and expecting them to work for you. What you copy may or
may not work for you.</para>
may not work in your environment.</para>
</caution>
<caution>
<para>The configuration shown here corresponds to Shorewall version
2.1.12. My configuration uses features not available in earlier
2.2.0 RC2. My configuration uses features not available in earlier
Shorewall releases.</para>
</caution>