extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-22 06:10:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Mention policy logging in the QuickStart Guides

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8017 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-01-04 19:31:42 +00:00
parent f36c1ccd18
commit d9c50fc5fa
3 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/standalone.xml
View File

@ -309,6 +309,11 @@ all all REJECT info</programlisting>
</listitem>
</orderedlist>
<para>The word <firstterm>info</firstterm> in the LOG LEVEL column for the
last two policies indicates that packets droped or rejected under those
policies should be <ulink url="shorewall_logging.html">logged at that
leve</ulink>l.</para>
<para>At this point, edit your <filename>/etc/shorewall/policy</filename>
and make any changes that you wish.</para>
</section>

5
docs/three-interface.xml
View File

@ -345,6 +345,11 @@ $FW net ACCEPT</programlisting>
</listitem>
</orderedlist>
<para>The word <firstterm>info</firstterm> in the LOG LEVEL column for the
DROP and REJECT policies indicates that packets droped or rejected under
those policies should be <ulink url="shorewall_logging.html">logged at
that leve</ulink>l.</para>
<para>It is important to note that Shorewall policies (and rules) refer to
<emphasis role="bold">connections</emphasis> and not packet flow. With the
policies defined in the <filename

8
docs/two-interface.xml
View File

@ -318,8 +318,12 @@ $FW net ACCEPT</programlisting> The above policy will:
<listitem>
<para>reject all other connection requests.</para>
</listitem>
</itemizedlist> <inlinegraphic fileref="images/BD21298_.gif"
format="GIF" /></para>
</itemizedlist> The word <firstterm>info</firstterm> in the LOG LEVEL
column for the DROP and REJECT policies indicates that packets droped or
rejected under those policies should be <ulink
url="shorewall_logging.html">logged at that leve</ulink>l.</para>
<para><inlinegraphic fileref="images/BD21298_.gif" format="GIF" /></para>
<para>It is important to note that Shorewall policies (and rules) refer to
<emphasis role="bold">connections</emphasis> and not packet flow. With the