mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-07 16:24:01 +01:00
First cut at removing references to Documentation.htm
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@6774 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
aa991fcf45
commit
fe5af63b14
@ -85,6 +85,15 @@
|
||||
dashes (<quote>-</quote>) and are not required to start with a
|
||||
letter.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>COMMENT - (Shorewall-perl only) - The remainder of the line
|
||||
is treated as a comment which is <ulink
|
||||
url="configuration_file_basics.htm#COMMENT">attached to subsequent
|
||||
rules</ulink> until another COMMENT line is found or until the end
|
||||
of the file is reached. To stop adding comments to rules, use a
|
||||
line with only the word COMMENT.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
|
||||
|
@ -46,7 +46,7 @@
|
||||
<para>Shorewall actions allow a symbolic name to be associated with a
|
||||
series of one or more iptables rules. The symbolic name may appear in the
|
||||
ACTION column of an <filename><ulink
|
||||
url="Documentation.htm#Rules">/etc/shorewall/rules</ulink></filename> file
|
||||
url="manpages/shorewall-rules.html">/etc/shorewall/rules</ulink></filename> file
|
||||
entry, in which case the traffic matching that rules file entry will be
|
||||
passed to the series of iptables rules named by the action.</para>
|
||||
|
||||
@ -107,7 +107,7 @@ ACCEPT - - tcp 135,139,445
|
||||
They are listed in the file /etc/shorewall/actions and are defined in
|
||||
action.* files in /etc/shorewall or in another directory listed in
|
||||
your CONFIG_PATH (defined in <ulink
|
||||
url="Documentation.htm#Conf">/etc/shorewall/shorewall.conf</ulink>).</para>
|
||||
url="manpages/shorewall.conf.html">/etc/shorewall/shorewall.conf</ulink>).</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</section>
|
||||
@ -177,7 +177,7 @@ Reject:REJECT #Default Action for REJECT policy</programlisting>
|
||||
<para>In addition, the default specified in
|
||||
/etc/shorewall/shorewall.conf may be overridden by specifying a
|
||||
different default in the POLICY column of <ulink
|
||||
url="Documentation.htm#Policy">/etc/shorewall/policy</ulink>.</para>
|
||||
url="manpages/shorewall-policy.html">/etc/shorewall/policy</ulink>.</para>
|
||||
</blockquote>
|
||||
|
||||
<warning>
|
||||
@ -611,4 +611,4 @@ add_rule( $chainref, '-m pkttype --pkttype broadcast -j DROP' );
|
||||
<para>For a richer example, see <ulink url="PortKnocking.html">this
|
||||
article</ulink>.</para>
|
||||
</section>
|
||||
</article>
|
||||
</article>
|
||||
|
@ -41,9 +41,9 @@
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para><emphasis role="bold">Shorewall</emphasis>. This package must be
|
||||
installed on at least one system in your network. That system must
|
||||
also have Shorewall-shell and/or Shorewall-perl installed.</para>
|
||||
<para><emphasis role="bold">Shorewall-common</emphasis>. This package
|
||||
must be installed on at least one system in your network. That system
|
||||
must also have Shorewall-shell and/or Shorewall-perl installed.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
@ -74,10 +74,10 @@
|
||||
</section>
|
||||
|
||||
<section id="Shorewall">
|
||||
<title>Shorewall</title>
|
||||
<title>Shorewall-common</title>
|
||||
|
||||
<para>The Shorewall product includes a large number of files which are
|
||||
installed in /<filename class="directory">sbin</filename>, <filename
|
||||
<para>The Shorewall-common package includes a large number of files which
|
||||
are installed in /<filename class="directory">sbin</filename>, <filename
|
||||
class="directory">/usr/share/shorewall</filename>, <filename
|
||||
class="directory">/etc/shorewall</filename>,
|
||||
<filename>/etc/init.d</filename> and <filename
|
||||
|
@ -62,7 +62,9 @@
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>All extension scripts used are copied into the program. The
|
||||
<para>All extension scripts used are copied into the program (with
|
||||
the exception of <ulink url="shorewall_extension_scripts.htm">those
|
||||
executed a compile-time by Shorewall-perl</ulink>). The
|
||||
ramifications of this are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
@ -142,8 +144,8 @@
|
||||
command:</para>
|
||||
|
||||
<blockquote>
|
||||
<para><command>shorewall compile [ -e ] [ <directory name> ]
|
||||
<path name></command></para>
|
||||
<para><command>shorewall compile [ -e ] [ C {perl|shell} ] [
|
||||
<directory name> ] <path name></command></para>
|
||||
</blockquote>
|
||||
|
||||
<para>where</para>
|
||||
@ -168,6 +170,16 @@
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>-C {perl|shell}</term>
|
||||
|
||||
<listitem>
|
||||
<para>Specifies the compiler to use. Overrides the
|
||||
SHOREWALL_COMPILER setting in <ulink
|
||||
url="manpages/shorewall.conf.html">shorewall.conf</ulink>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><directory name></term>
|
||||
|
||||
@ -803,7 +815,7 @@ MANGLE_FORWARD # Mangle table has FORWARD chain</programlisting
|
||||
</blockquote>
|
||||
|
||||
<para>The IPTABLES and MODULESDIR options have their <ulink
|
||||
url="Documentation.htm#Conf">usual Shorewall default
|
||||
url="manpages/shorewall.conf.html">usual Shorewall default
|
||||
values</ulink>.</para>
|
||||
|
||||
<para>The <filename>capabilities</filename> file may then be copied to a
|
||||
@ -864,4 +876,4 @@ MANGLE_FORWARD # Mangle table has FORWARD chain</programlisting
|
||||
is the level specified in the shorewall.conf file used when then program
|
||||
was compiled.</para>
|
||||
</section>
|
||||
</article>
|
||||
</article>
|
||||
|
@ -83,20 +83,20 @@
|
||||
<listitem>
|
||||
<para>You specify whether you want packets from blacklisted hosts
|
||||
dropped or rejected using the BLACKLIST_DISPOSITION setting in <ulink
|
||||
url="Documentation.htm#Config"><filename>/etc/shorewall/shorewall.conf</filename>.</ulink></para>
|
||||
url="manpages/shorewall.conf.html"><filename>/etc/shorewall/shorewall.conf</filename>.</ulink></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>You specify whether you want packets from blacklisted hosts
|
||||
logged and at what syslog level using the BLACKLIST_LOGLEVEL setting
|
||||
in <ulink
|
||||
url="Documentation.htm#Config"><filename>/etc/shorewall/shorewall.conf</filename></ulink>.</para>
|
||||
url="manpages/shorewall.conf.html"><filename>/etc/shorewall/shorewall.conf</filename></ulink>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>You list the IP addresses/subnets that you wish to blacklist in
|
||||
<ulink
|
||||
url="Documentation.htm#Blacklist"><filename>/etc/shorewall/blacklist</filename></ulink>.
|
||||
url="manpages/shorewall-blacklist.html"><filename>/etc/shorewall/blacklist</filename></ulink>.
|
||||
You may also specify PROTOCOL and Port numbers/Service names in the
|
||||
blacklist file.</para>
|
||||
</listitem>
|
||||
@ -105,7 +105,7 @@
|
||||
<para>You specify the interfaces whose incoming packets you want
|
||||
checked against the blacklist using the <quote>blacklist</quote>
|
||||
option in <ulink
|
||||
url="Documentation.htm#Interfaces"><filename>/etc/shorewall/interfaces</filename></ulink>.</para>
|
||||
url="manpages/shorewall-interfaces.html"><filename>/etc/shorewall/interfaces</filename></ulink>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
@ -232,4 +232,4 @@ ipset -B Blacklist 206.124.146.177 -b SMTP</programlisting>
|
||||
<para>Re-enables traffic from 192.0.2.125.</para>
|
||||
</example>
|
||||
</section>
|
||||
</article>
|
||||
</article>
|
||||
|
Loading…
Reference in New Issue
Block a user