extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-22 23:53:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

fixed quotes

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@975 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
mhnoyes 2003-12-26 18:13:03 +00:00
parent a89596ffca
commit 3dbda162a9
2 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
Shorewall-docs/ping.xml
View File

@ -34,12 +34,12 @@
</articleinfo>
<note>
<para>Shorewall &#39;Ping&#39; management has evolved over time with the
latest change coming in Shorewall version 1.4.0. To find out which version
of Shorewall you are running, at a shell prompt type &#34;/sbin/shorewall
version&#34;. If that command gives you an error, it&#39;s time to upgrade
since you have a very old version of Shorewall installed (1.2.4 or
earlier).</para>
<para>Shorewall <quote>Ping</quote> management has evolved over time with
the latest change coming in Shorewall version 1.4.0. To find out which
version of Shorewall you are running, at a shell prompt type
<quote>/sbin/shorewall version</quote>. If that command gives you an
error, it&#39;s time to upgrade since you have a very old version of
Shorewall installed (1.2.4 or earlier).</para>
</note>
<section>
@ -138,14 +138,14 @@
</informaltable>
</example>
<para>If you would like to accept &#39;ping&#39; by default even when the
relevant policy is DROP or REJECT, create /etc/shorewall/icmpdef if it
<para>If you would like to accept <quote>ping</quote> by default even when
the relevant policy is DROP or REJECT, create /etc/shorewall/icmpdef if it
doesn&#39;t already exist and in that file place the following command:</para>
<programlisting> run_iptables -A icmpdef -p icmp --icmp-type 8 -j ACCEPT</programlisting>
<para>With that rule in place, if you want to ignore &#39;ping&#39; from
z1 to z2 then you need a rule of the form:</para>
<para>With that rule in place, if you want to ignore <quote>ping</quote>
from z1 to z2 then you need a rule of the form:</para>
<informaltable>
<tgroup cols="7">
@ -334,14 +334,14 @@
</informaltable>
</example>
<para>If you would like to accept &#39;ping&#39; by default even when the
relevant policy is DROP or REJECT, create /etc/shorewall/icmpdef if it
<para>If you would like to accept <quote>ping</quote> by default even when
the relevant policy is DROP or REJECT, create /etc/shorewall/icmpdef if it
doesn&#39;t already exist and in that file place the following command:</para>
<programlisting> run_iptables -A icmpdef -p icmp --icmp-type 8 -j ACCEPT</programlisting>
<para>With that rule in place, if you want to ignore &#39;ping&#39; from
z1 to z2 then you need a rule of the form:</para>
<para>With that rule in place, if you want to ignore <quote>ping</quote>
from z1 to z2 then you need a rule of the form:</para>
<informaltable>
<tgroup cols="7">
@ -437,7 +437,7 @@
<note>
<para>There is one exception to the above description. In 1.3.14 and
1.3.14a, ping from the firewall itself is enabled unconditionally. This
suprising &#34;feature&#34; was removed in version 1.4.0.</para>
suprising <quote>feature</quote> was removed in version 1.4.0.</para>
</note>
</section>

4
Shorewall-docs/ports.xml
View File

@ -154,7 +154,7 @@
<para>UDP ports 33434 through 33434+&#60;max number of hops&#62;-1</para>
<para>ICMP type 8 (&#39;ping&#39;)</para>
<para>ICMP type 8 (<quote>ping</quote>)</para>
</section>
<section>
@ -255,7 +255,7 @@
<section>
<title>VNC</title>
<para>TCP port 5900 + &#60;display number&#62;. </para>
<para>TCP port 5900 + &#60;display number&#62;.</para>
</section>
<section>