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

Second batch of mindless ID changes

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@6694 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-06-28 15:40:13 +00:00
parent f96772989c
commit c41d3fee71
7 changed files with 49 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ECN.xml
View File

@ -46,7 +46,7 @@
to hosts defined in the /etc/shorewall/ecn file.</para>
</warning>
<section>
<section id="ecn">
<title>Explicit Congestion Notification (ECN)</title>
<para>Explicit Congestion Notification (ECN) is described in RFC 3168 and
@ -90,11 +90,11 @@
</varlistentry>
</variablelist>
<example>
<example id="Example1">
<title>Your external interface is eth0 and you want to disable ECN for
tcp connections to 192.0.2.0/24:</title>
<para><table>
<para><table id="Table1">
<title>/etc/shorewall/ecn</title>
<tgroup cols="2">

58
docs/FAQ.xml
View File

@ -43,10 +43,10 @@
release.</emphasis></para>
</caution>
<section>
<section id="Install">
<title>Installing Shorewall</title>
<section>
<section id="Howto">
<title>Where do I find Step by Step Installation and Configuration
Instructions?</title>
@ -347,7 +347,7 @@ DNAT net fw:192.168.1.1:22 tcp 4104</programlisting>
you use a REDIRECT rule.</para>
</section>
<section>
<section id="faq38">
<title>(FAQ 38) Where can I find more information about DNAT?</title>
<para><emphasis role="bold">Answer</emphasis>:Ian Allen has written a
@ -364,8 +364,8 @@ DNAT net fw:192.168.1.1:22 tcp 4104</programlisting>
</section>
</section>
<section>
<title>DNS and Port Forwarding/NAT</title>
<section id="DNS-DNAT">
<title id="DNS">DNS and Port Forwarding/NAT</title>
<section id="faq2">
<title>(FAQ 2) I port forward www requests to www.mydomain.com (IP
@ -492,7 +492,7 @@ DNAT loc loc:192.168.1.5 tcp www - $ETH0
</listitem>
</orderedlist>
<example>
<example id="Example1">
<title>Example:</title>
<literallayout>Zone: dmz, Interface: eth2, Subnet: 192.168.2.0/24, Address: 192.168.2.254</literallayout>
@ -577,7 +577,7 @@ DNAT loc dmz:192.168.2.4 tcp 80 - $ETH0
</section>
</section>
<section>
<section id="Blacklisting">
<title>Blacklisting</title>
<section id="faq63">
@ -594,7 +594,7 @@ DNAT loc dmz:192.168.2.4 tcp 80 - $ETH0
</section>
</section>
<section>
<section id="MSN">
<title>Netmeeting/MSN</title>
<section id="faq3">
@ -628,7 +628,7 @@ to debug/develop the newnat interface.</programlisting></para>
</section>
</section>
<section>
<section id="Openports">
<title>Open Ports</title>
<section id="faq51">
@ -736,7 +736,7 @@ to debug/develop the newnat interface.</programlisting></para>
nice integration of Shorewall and PortSentry.</para>
</section>
<section>
<section id="faq4d">
<title>(FAQ 4d) How do I use Shorewall with Snort-Inline?</title>
<para><emphasis role="bold">Answer:</emphasis> <ulink
@ -746,7 +746,7 @@ to debug/develop the newnat interface.</programlisting></para>
</section>
</section>
<section>
<section id="Connections">
<title>Connection Problems</title>
<section id="faq5">
@ -834,8 +834,8 @@ to debug/develop the newnat interface.</programlisting></para>
documentation</ulink>.</para>
</section>
<section>
<title>(FAQ 63) I just upgraded my kernel to 2.6.20 and my
<section id="faq64">
<title>(FAQ 64) I just upgraded my kernel to 2.6.20 and my
bridge/firewall stopped working. What is wrong?</title>
<para><emphasis role="bold">Answer:</emphasis> In kernel 2.6.20, the
@ -855,7 +855,7 @@ to debug/develop the newnat interface.</programlisting></para>
</section>
</section>
<section>
<section id="Logging">
<title>Logging</title>
<section id="faq6">
@ -974,8 +974,8 @@ DROP net fw udp 10619</programlisting>
</listitem>
</itemizedlist>
<para><example>
<title>Example</title>
<para><example id="Example5">
<title id="Example2">Example</title>
<para><programlisting>MAC=00:04:4c:dc:e2:28:00:b0:8e:cf:3c:4c:08:00</programlisting>
<itemizedlist>
@ -1272,7 +1272,7 @@ DROP net fw udp 10619</programlisting>
</varlistentry>
</variablelist>
<example>
<example id="Example3">
<title>Here is an example:</title>
<programlisting>Jun 27 15:37:56 gateway kernel:
@ -1460,7 +1460,7 @@ modprobe: Can't locate module iptable_raw</programlisting>
</section>
</section>
<section>
<section id="Routing">
<title>Routing</title>
<section id="faq32">
@ -1501,7 +1501,7 @@ modprobe: Can't locate module iptable_raw</programlisting>
</section>
</section>
<section>
<section id="Start-Stop">
<title>Starting and Stopping</title>
<section id="faq7">
@ -1709,7 +1709,7 @@ iptables: Invalid argument
</section>
</section>
<section>
<section id="MultiISP">
<title>Multiple ISPs</title>
<section id="faq57">
@ -1748,7 +1748,7 @@ iptables: Invalid argument
</section>
</section>
<section>
<section id="About">
<title>About Shorewall</title>
<section id="faq10">
@ -1804,7 +1804,7 @@ iptables: Invalid argument
<programlisting><command>/sbin/shorewall[-lite] version</command> </programlisting>
<section>
<section id="faq25a">
<title>(FAQ 25a) How do I tell which version of Shorewall-perl and
Shorewall-shell that I have intalled?</title>
@ -1879,8 +1879,8 @@ iptables: Invalid argument
</variablelist>
</section>
<section id="faq64">
<title>(FAQ 64) How do I accomplish failover with Shorewall?</title>
<section id="faq65">
<title>(FAQ 65) How do I accomplish failover with Shorewall?</title>
<para><emphasis role="bold">Answer</emphasis>: <ulink
url="http://linuxman.wikispaces.com/Clustering+Shorewall">This article
@ -1888,7 +1888,7 @@ iptables: Invalid argument
</section>
</section>
<section>
<section id="RFC1918">
<title>RFC 1918</title>
<section id="faq14">
@ -1999,7 +1999,7 @@ eth0 eth1 # eth1 = interface to local netwo
</section>
</section>
<section>
<section id="ALIASES">
<title>Alias IP Addresses/Virtual Interfaces</title>
<section id="faq18">
@ -2012,7 +2012,7 @@ eth0 eth1 # eth1 = interface to local netwo
</section>
</section>
<section>
<section id="Lite">
<title>Shorewall Lite</title>
<section id="faq53">
@ -2133,7 +2133,7 @@ eth0 eth1 # eth1 = interface to local netwo
</section>
</section>
<section>
<section id="Misc">
<title>Miscellaneous</title>
<section id="faq20">
@ -2156,7 +2156,7 @@ eth0 eth1 # eth1 = interface to local netwo
<programlisting>net:&lt;ip1&gt;,&lt;ip2&gt;,...</programlisting>
<example>
<example id="Example4">
<title>Example:</title>
<programlisting>ACCEPT net:192.0.2.16/28,192.0.2.44 fw tcp 22</programlisting>

14
docs/FTP.xml
View File

@ -47,7 +47,7 @@
release.</emphasis></para>
</caution>
<section>
<section id="Protocol">
<title>FTP Protocol</title>
<para>FTP transfers involve two TCP connections. The first <emphasis
@ -167,7 +167,7 @@ ftp&gt;</programlisting>
</orderedlist>
</section>
<section>
<section id="Conntrack">
<title>Linux FTP connection-tracking</title>
<para>Given the normal loc-&gt;net policy of ACCEPT, passive mode access
@ -205,7 +205,7 @@ ftp&gt;</programlisting>
to be loaded automatically by Shorewall.</para>
</important>
<example>
<example id="Example1">
<title>Example (Kernel 3.2.20)</title>
<programlisting>[root@lists etc]# lsmod
@ -290,7 +290,7 @@ xt_tcpudp 3328 0
/etc/shorewall/shorewall.conf to point to that directory.</para>
</section>
<section>
<section id="Ports">
<title>FTP on Non-standard Ports</title>
<note>
@ -313,7 +313,7 @@ xt_tcpudp 3328 0
order to use FTP on a non-standard port.</para>
</caution></para>
<example>
<example id="Example2">
<title>if you run an FTP server that listens on port 49 or you need to
access a server on the internet that listens on that port then you would
have:</title>
@ -391,7 +391,7 @@ DNAT ACTION =
the preferred way to generate the rules described above. Here are a couple
of examples.</para>
<para><example>
<para><example id="Example3">
<title>Server running behind a Masquerading Gateway</title>
<para>Suppose that you run an FTP server on 192.168.1.5 in your local
@ -400,7 +400,7 @@ DNAT ACTION =
<programlisting>#ACTION SOURCE DESTINATION PROTO PORT(S) SOURCE ORIGINAL
# PORT(S) DESTINATION
FTP/DNAT net loc:192.168.1.5</programlisting>
</example><example>
</example><example id="Example4">
<title>Allow your DMZ FTP access to the Internet</title>
<programlisting>#ACTION SOURCE DESTINATION PROTO PORT(S) SOURCE ORIGINAL

2
docs/GenericTunnels.xml
View File

@ -45,7 +45,7 @@
can generally describe the tunneling software using <quote>generic
tunnels</quote>.</para>
<section>
<section id="Bridged">
<title>Bridging two Masqueraded Networks</title>
<para>Suppose that we have the following situation:</para>

2
docs/GettingStarted.xml
View File

@ -34,7 +34,7 @@
</legalnotice>
</articleinfo>
<section>
<section id="GettingStarted">
<title>Getting Started</title>
<para>If you are new to Shorewall, please read these two articles

6
docs/Install.xml
View File

@ -272,7 +272,7 @@
described in the Bering (or Bering uClibc) documentation.</para>
</section>
<section>
<section id="Debian">
<title>Install the .deb</title>
<important>
@ -307,7 +307,7 @@ Pin-Priority: 700</programlisting><emphasis role="bold"><emphasis>Then
<filename>/etc/default/shorewall</filename>.</emphasis></emphasis></para>
</section>
<section>
<section id="Upgrade">
<title>General Notes about Upgrading Shorewall</title>
<para>Most problems associated with upgrades come from two causes:</para>
@ -594,7 +594,7 @@ tar -xzvf /mnt/package2.lrp
contain all of the information you need.</para>
</section>
<section>
<section id="Uninstall">
<title>Uninstall/Fallback</title>
<para>See <quote><ulink url="fallback.htm">Fallback and

10
docs/fallback.xml
View File

@ -34,7 +34,7 @@
</legalnotice>
</articleinfo>
<section>
<section id="Tarball">
<title>Falling Back to the Previous Version of Shorewall using the
Fallback Script</title>
@ -62,7 +62,7 @@
</caution>
</section>
<section>
<section id="RPM">
<title>Falling Back to the Previous Version of Shorewall using rpm</title>
<para>If your previous version of Shorewall was installed using RPM, you
@ -72,7 +72,7 @@
3.1.1-0 version of Shorewall).</para>
</section>
<section>
<section id="Uninstall">
<title>Uninstalling Shorewall</title>
<para>If you no longer wish to use Shorewall, you may remove it by:</para>
@ -92,13 +92,13 @@
<quote>rpm -e shorewall</quote>.</para>
</section>
<section>
<section id="Shell-Perl">
<title>Shorewall-shell and Shorewall-perl</title>
<para>Shorewall-shell and Shoreall-perl have no configuration files and
all of their released files are installed in a single directory. To
fallback to a prior release of one of these products using the tarballs,
simple re-install the older version. </para>
simple re-install the older version.</para>
<para>To uninstal these products when they have been installed using the
tarballs:</para>