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

Add Two ISP graphics

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2135 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-05-18 21:12:46 +00:00
parent 44231e92a0
commit 39a54f211e
7 changed files with 880 additions and 89 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

109
Shorewall-docs2/Multiple_Zones.xml
View File

@ -15,10 +15,10 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2004-03-15</pubdate> <pubdate>2005-05-15</pubdate>
<copyright> <copyright>
<year>2003</year> <year>2003-2005</year>
<holder>Thomas M. Eastep</holder> <holder>Thomas M. Eastep</holder>
</copyright> </copyright>
@ -29,17 +29,18 @@
1.2 or any later version published by the Free Software Foundation; with 1.2 or any later version published by the Free Software Foundation; with
no Invariant Sections, with no Front-Cover, and with no Back-Cover no Invariant Sections, with no Front-Cover, and with no Back-Cover
Texts. A copy of the license is included in the section entitled Texts. A copy of the license is included in the section entitled
<quote><ulink url="GnuCopyright.htm">GNU Free Documentation License</ulink></quote>.</para> <quote><ulink url="GnuCopyright.htm">GNU Free Documentation
License</ulink></quote>.</para>
</legalnotice> </legalnotice>
</articleinfo> </articleinfo>
<section> <section>
<title>Introduction</title> <title>Introduction</title>
<para>While most configurations can be handled with each of the <para>While most configurations can be handled with each of the firewall's
firewall&#39;s network interfaces assigned to a single zone, there are network interfaces assigned to a single zone, there are cases where you
cases where you will want to divide the hosts accessed through an will want to divide the hosts accessed through an interface between two or
interface between two or more zones.</para> more zones.</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -57,7 +58,8 @@
<listitem> <listitem>
<para>There are routers accessible through the interface and you want <para>There are routers accessible through the interface and you want
to treat the networks accessed through that router as a separate zone.</para> to treat the networks accessed through that router as a separate
zone.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -83,8 +85,8 @@
</itemizedlist> </itemizedlist>
<para><emphasis role="bold">These examples use the local zone but the same <para><emphasis role="bold">These examples use the local zone but the same
technique works for any zone.</emphasis> Remember that Shorewall technique works for any zone.</emphasis> Remember that Shorewall doesn't
doesn&#39;t have any conceptual knowledge of <quote>Internet</quote>, have any conceptual knowledge of <quote>Internet</quote>,
<quote>Local</quote>, or <quote>DMZ</quote> so all zones except the <quote>Local</quote>, or <quote>DMZ</quote> so all zones except the
firewall itself ($FW) are the same as far as Shorewall is concerned. Also, firewall itself ($FW) are the same as far as Shorewall is concerned. Also,
the examples use private (RFC 1918) addresses but public IP addresses can the examples use private (RFC 1918) addresses but public IP addresses can
@ -119,7 +121,8 @@
<listitem> <listitem>
<para>The hosts in 192.168.1.0/24 know that the route to <para>The hosts in 192.168.1.0/24 know that the route to
192.168.2.0/24 is through the <emphasis role="bold">router</emphasis>.</para> 192.168.2.0/24 is through the <emphasis
role="bold">router</emphasis>.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -132,11 +135,11 @@
<title>Will One Zone be Enough?</title> <title>Will One Zone be Enough?</title>
<para>If the firewalling requirements for the two local networks is the <para>If the firewalling requirements for the two local networks is the
same but the hosts in 192.168.1.0/24 don&#39;t know how to route to same but the hosts in 192.168.1.0/24 don't know how to route to
192.168.2.0/24 then you need to configure the firewall slightly 192.168.2.0/24 then you need to configure the firewall slightly
differently. This type of configuration is rather stupid from an IP differently. This type of configuration is rather stupid from an IP
networking point of view but it is sometimes necessary because you networking point of view but it is sometimes necessary because you
simply don&#39;t want to have to reconfigure all of the hosts in simply don't want to have to reconfigure all of the hosts in
192.168.1.0/24 to add a persistent route to 192.168.2.0/24. On the 192.168.1.0/24 to add a persistent route to 192.168.2.0/24. On the
firewall:</para> firewall:</para>
@ -156,13 +159,32 @@
<para>Restart Shorewall.</para> <para>Restart Shorewall.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
<para>If this still doesn't work at all or if it works for connections
in one direction but not for connections in the other direction
then:</para>
<orderedlist>
<listitem>
<para>You must be running Shorewall version 2.0.16 or later;
and</para>
</listitem>
<listitem>
<para>You need to set DROPINVALID=No in
<filename>/etc/shorewall/shorewall.conf</filename>.</para>
</listitem>
</orderedlist>
</section> </section>
<section> <section>
<title>I Need Separate Zones</title> <title>I Need Separate Zones</title>
<para>If you need to make 192.168.2.0/24 into it&#39;s own zone, you can <para>If you need to make 192.168.2.0/24 into it's own zone, you can do
do it one of two ways; Nested Zones or Parallel Zones.</para> it one of two ways; Nested Zones or Parallel Zones. Again, it is likely
that you will need to be running Shorewall 2.0.16 or later and that you
will have to set DROPINVALID=No in
<filename>/etc/shorewall/shorewall.conf</filename>.</para>
<section> <section>
<title>Nested Zones</title> <title>Nested Zones</title>
@ -173,13 +195,13 @@
<graphic fileref="images/MultiZone1A.png" /> <graphic fileref="images/MultiZone1A.png" />
<para>The advantage of this approach is that the zone <quote>loc1</quote> <para>The advantage of this approach is that the zone
can use CONTINUE policies such that if a connection request <quote>loc1</quote> can use CONTINUE policies such that if a
doesn&#39;t match a <quote>loc1</quote> rule, it will be matched connection request doesn't match a <quote>loc1</quote> rule, it will
against the <quote>loc</quote> rules. For example, if your be matched against the <quote>loc</quote> rules. For example, if your
loc1-&#62;net policy is CONTINUE then if a connection request from loc1-&gt;net policy is CONTINUE then if a connection request from loc1
loc1 to the internet doesn&#39;t match any rules for loc1-&#62;net to the internet doesn't match any rules for loc1-&gt;net then it will
then it will be checked against the loc-&#62;net rules.</para> be checked against the loc-&gt;net rules.</para>
<para><filename>/etc/shorewall/zones</filename></para> <para><filename>/etc/shorewall/zones</filename></para>
@ -201,9 +223,9 @@ loc eth1 192.168.1.255</programlisting>
<programlisting>#ZONE HOSTS <programlisting>#ZONE HOSTS
loc1 eth1:192.168.2.0/24</programlisting> loc1 eth1:192.168.2.0/24</programlisting>
<para>If you don&#39;t need Shorewall to set up infrastructure to <para>If you don't need Shorewall to set up infrastructure to route
route traffic between <quote>loc</quote> and <quote>loc1</quote>, add traffic between <quote>loc</quote> and <quote>loc1</quote>, add these
these two policies.</para> two policies.</para>
<para>/etc/shorewall/policy</para> <para>/etc/shorewall/policy</para>
@ -227,7 +249,7 @@ loc1 Local1 Hosts accessed Directly from Firewall
loc2 Local2 Hosts accessed via the internal Router</programlisting> loc2 Local2 Hosts accessed via the internal Router</programlisting>
<note> <note>
<para>Here it doesn&#39;t matter which zone is defined first.</para> <para>Here it doesn't matter which zone is defined first.</para>
</note> </note>
<para><filename>/etc/shorewall/interfaces</filename></para> <para><filename>/etc/shorewall/interfaces</filename></para>
@ -241,7 +263,7 @@ loc2 Local2 Hosts accessed via the internal Router</
loc1 eth1:192.168.1.0/24 loc1 eth1:192.168.1.0/24
loc2 eth1:192.168.2.0/24</programlisting> loc2 eth1:192.168.2.0/24</programlisting>
<para>You don&#39;t need Shorewall to set up infrastructure to route <para>You don't need Shorewall to set up infrastructure to route
traffic between <quote>loc</quote> and <quote>loc1</quote>, so add traffic between <quote>loc</quote> and <quote>loc1</quote>, so add
these two policies:</para> these two policies:</para>
@ -256,7 +278,7 @@ loc2 loc1 NONE</programlisting>
<title>Some Hosts have Special Firewalling Requirements</title> <title>Some Hosts have Special Firewalling Requirements</title>
<para>There are cases where a subset of the addresses associated with an <para>There are cases where a subset of the addresses associated with an
interface need special handling. Here&#39;s an example.</para> interface need special handling. Here's an example.</para>
<graphic fileref="images/MultiZone2.png" /> <graphic fileref="images/MultiZone2.png" />
@ -281,9 +303,9 @@ loc eth1 192.168.1.255</programlisting>
<para><filename>/etc/shorewall/hosts</filename><programlisting>#ZONE HOSTS <para><filename>/etc/shorewall/hosts</filename><programlisting>#ZONE HOSTS
loc1 eth1:192.168.1.8/29</programlisting></para> loc1 eth1:192.168.1.8/29</programlisting></para>
<para>You probably don&#39;t want Shorewall to set up infrastructure to <para>You probably don't want Shorewall to set up infrastructure to route
route traffic between <quote>loc</quote> and <quote>loc1</quote> so you traffic between <quote>loc</quote> and <quote>loc1</quote> so you should
should add these two policies.</para> add these two policies.</para>
<para><filename>/etc/shorewall/policy</filename></para> <para><filename>/etc/shorewall/policy</filename></para>
@ -295,16 +317,16 @@ loc1 loc NONE</programlisting>
<section id="OneArmed"> <section id="OneArmed">
<title>One-armed Router</title> <title>One-armed Router</title>
<para>Nested zones may also be used to configure a <quote>one-armed</quote> <para>Nested zones may also be used to configure a
router (I don&#39;t call it a <quote>firewall</quote> because it is very <quote>one-armed</quote> router (I don't call it a <quote>firewall</quote>
insecure. For example, if you connect to the internet via cable modem, because it is very insecure. For example, if you connect to the internet
your next door neighbor has full access to your local systems as does via cable modem, your next door neighbor has full access to your local
everyone else connected to the same cable modem head-end controller). Here systems as does everyone else connected to the same cable modem head-end
eth0 is configured with both a public IP address and an RFC 1918 address controller). Here eth0 is configured with both a public IP address and an
(More on that topic may be found <ulink RFC 1918 address (More on that topic may be found <ulink
url="Shorewall_and_Aliased_Interfaces.html">here</ulink>). Hosts in the url="Shorewall_and_Aliased_Interfaces.html">here</ulink>). Hosts in the
<quote>loc</quote> zone are configured with their default gateway set to <quote>loc</quote> zone are configured with their default gateway set to
the Shorewall router&#39;s RFC1918 address.</para> the Shorewall router's RFC1918 address.</para>
<para><graphic fileref="images/MultiZone3.png" /></para> <para><graphic fileref="images/MultiZone3.png" /></para>
@ -333,10 +355,11 @@ loc eth0:192.168.1.0/24 maclist</programlisting>
<programlisting>#INTERFACE SUBNET ADDRESS <programlisting>#INTERFACE SUBNET ADDRESS
eth0:!192.168.1.0/24 192.168.1.0/24</programlisting> eth0:!192.168.1.0/24 192.168.1.0/24</programlisting>
<para>Note that the maclist option is specified in <filename>/etc/shorewall/interfaces</filename>. <para>Note that the maclist option is specified in
This is to help protect your router from unauthorized access by your <filename>/etc/shorewall/interfaces</filename>. This is to help protect
friends and neighbors. Start without maclist then add it and configure your router from unauthorized access by your friends and neighbors. Start
your <ulink url="MAC_Validation.html"><filename>/etc/shorewall/maclist</filename></ulink> without maclist then add it and configure your <ulink
url="MAC_Validation.html"><filename>/etc/shorewall/maclist</filename></ulink>
file when everything else is working.</para> file when everything else is working.</para>
</section> </section>
</article> </article>

30
Shorewall-docs2/Shorewall_Squid_Usage.xml
View File

@ -15,7 +15,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2005-03-01</pubdate> <pubdate>2005-05-16</pubdate>
<copyright> <copyright>
<year>2003-2005</year> <year>2003-2005</year>
@ -174,7 +174,9 @@ REDIRECT loc 3128 tcp www - !206.124.146.
already enabled from the local zone to the internet.</para> already enabled from the local zone to the internet.</para>
<para>If you are running a Shorewall version earlier than 2.3.3 OR your <para>If you are running a Shorewall version earlier than 2.3.3 OR your
kernel and/or iptables do not have ROUTE target support then:</para> kernel and/or iptables do not have <ulink
url="Shorewall_and_Routing.html#RouteTarget">ROUTE target
support</ulink> then:</para>
<orderedlist> <orderedlist>
<listitem> <listitem>
@ -218,17 +220,19 @@ fi</command></programlisting>
</orderedlist> </orderedlist>
<para>If you are running Shorewall 2.3.3 or later and your kernel and <para>If you are running Shorewall 2.3.3 or later and your kernel and
iptables have ROUTE target support then add this entry to iptables have <ulink url="Shorewall_and_Routing.html#RouteTarget">ROUTE
target support</ulink> then add this entry to
/etc/shorewall/routes:</para> /etc/shorewall/routes:</para>
<blockquote> <blockquote>
<programlisting>#SOURCE DEST PROTO PORT(S) SOURCE INTERFACE GATEWAY <programlisting>#SOURCE DEST PROTO PORT(S) SOURCE TEST INTERFACE GATEWAY
# PORT(S) # PORT(S)
eth1 0.0.0.0/0 tcp 80 - eth1 192.168.1.3</programlisting> eth1 0.0.0.0/0 tcp 80 - - eth1 192.168.1.3</programlisting>
</blockquote> </blockquote>
<para>Regardless of your Shorewall version or your kernel and iptables <para>Regardless of your Shorewall version or your kernel and iptables
ROUTE target support, you need the following:</para> <ulink url="Shorewall_and_Routing.html#RouteTarget">ROUTE target
support</ulink>, you need the following:</para>
<orderedlist> <orderedlist>
<listitem> <listitem>
@ -282,7 +286,9 @@ chkconfig --level 35 iptables on</command></programlisting>
Your DMZ interface is eth1 and your local interface is eth2.</para> Your DMZ interface is eth1 and your local interface is eth2.</para>
<para>If you are running a Shorewall version earlier than 2.3.3 OR your <para>If you are running a Shorewall version earlier than 2.3.3 OR your
kernel and/or iptables do not have ROUTE target support then:</para> kernel and/or iptables do not have <ulink
url="Shorewall_and_Routing.html#RouteTarget">ROUTE target
support</ulink> then:</para>
<orderedlist> <orderedlist>
<listitem> <listitem>
@ -351,17 +357,19 @@ fi</command></programlisting>
</orderedlist> </orderedlist>
<para>If you are running Shorewall 2.3.3 or later and your kernel and <para>If you are running Shorewall 2.3.3 or later and your kernel and
iptables have ROUTE target support then add this entry to iptables have <ulink url="Shorewall_and_Routing.html#RouteTarget">ROUTE
target support</ulink> then add this entry to
/etc/shorewall/routes:</para> /etc/shorewall/routes:</para>
<blockquote> <blockquote>
<programlisting>#SOURCE DEST PROTO PORT(S) SOURCE INTERFACE GATEWAY <programlisting>#SOURCE DEST PROTO PORT(S) SOURCE TEST INTERFACE GATEWAY
# PORT(S) # PORT(S)
eth2 0.0.0.0/0 tcp 80 - eth1 192.0.2.177</programlisting> eth2 0.0.0.0/0 tcp 80 - - eth1 192.0.2.177</programlisting>
</blockquote> </blockquote>
<para>Regardless of your Shorewall version or your kernel and iptables <para>Regardless of your Shorewall version or your kernel and iptables
ROUTE target support, you need the following:</para> <ulink url="Shorewall_and_Routing.html#RouteTarget">ROUTE target
support</ulink>, you need the following:</para>
<orderedlist> <orderedlist>
<listitem> <listitem>

269
Shorewall-docs2/Shorewall_and_Routing.xml
View File

@ -15,7 +15,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2005-05-15</pubdate> <pubdate>2005-05-18</pubdate>
<copyright> <copyright>
<year>2005</year> <year>2005</year>
@ -206,7 +206,194 @@
</section> </section>
<section> <section>
<title>Routing with Shorewall 2.3.3 and Later</title> <title>Multiple Internet Connection Support in Shorewall 2.3.3 and
Later</title>
<para>Beginning with Shorewall 2.3.3, support is included for multiple
internet connections.</para>
<section>
<title>Overview</title>
<para>Let's assume that a firewall is connected via two separate
ethernet interfaces to two different ISP as in the following
diagram.</para>
<itemizedlist>
<listitem>
<para>eth0 connects to ISP1. The IP address of eth0 is
206.124.146.176 and the ISP's gateway router has IP address
206.124.146.254.</para>
</listitem>
<listitem>
<para>eth1 connects to ISP 2. The IP address of eth1 is
130.252.99.27 and the ISP's gateway router has IP address
130.252.99.254.</para>
</listitem>
</itemizedlist>
<para>Each of these <firstterm>providers</firstterm> is described in an
entry in the file <filename>/etc/shorewall/providers</filename>.</para>
<para>Entries in <filename>/etc/shorewall/providers</filename> can
specify that outgoing connections are to be load-balanced between the
two ISPs. Entries in <filename>/etc/shorewall/tcrules</filename> can be
used to direct particular outgoing connections to one ISP or the
other.</para>
<para>Connections from the internet are automatically routed back out of
the correct interface and through the correct ISP gateway. This works
whether the connection is handled by the firewall itself or if it is
routed or port-forwarded to a system behind the firewall.</para>
<para>Shorewall will set up the routing and will update the
/etc/iproute2/rt_tables to include the table names and number of the
tables that it adds.</para>
<caution>
<para>This feature uses <ulink url="traffic_shaping.htm">packet
marking</ulink> to control the routing. As a consequence, there are
some restrictions concerning entries in /etc/shorewall/tcrules:</para>
<itemizedlist>
<listitem>
<para>Packet marking for traffic control purposes must be done in
the FORWARD table.</para>
</listitem>
<listitem>
<para>You may not use the SAVE or RESTORE options.</para>
</listitem>
<listitem>
<para>You man not use connection marking.</para>
</listitem>
</itemizedlist>
</caution>
<para>The <filename>/etc/shorewall/providers</filename> file can also be
used in other routing senarios. See the Squid documentation for an
example.</para>
</section>
<section>
<title>/etc/shorewall/providers File</title>
<para>Entries in this file have the following columns. As in all
Shorewall configuration files, enter "-" in a column if you don't want
to enter any value.</para>
<glossary>
<glossdiv>
<title>/etc/shorewall/providers:</title>
<glossentry>
<glossterm>NAME</glossterm>
<glossdef>
<para>The provider name. Must begin with a letter and consist of
letters and digits. The provider name becomes the name of the
generated routing table for this provider.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>NUMBER</glossterm>
<glossdef>
<para>A number between 1 and 252. This becomes the routing table
number for the generated table for this provider.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>MARK</glossterm>
<glossdef>
<para>A mark value used in your /etc/shorewall/tcrules file to
direct packets to this provider. Shorewall will also mark
connections that have seen input from this provider with this
value and will restore the packet mark in the PREROUTING
CHAIN.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>DUPLICATE</glossterm>
<glossdef>
<para>Gives the name and number of a routing table to duplicate.
May be 'main' or the name of a previously declared provider. For
most applications, you want to specify 'main' here.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>INTERFACE</glossterm>
<glossdef>
<para>The name of the interface to the provider.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>GATEWAY</glossterm>
<glossdef>
<para>The IP address of the provider's Gateway router.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>OPTIONS</glossterm>
<glossdef>
<para>A comma-separated list from the following:</para>
<glosslist>
<glossentry>
<glossterm>track</glossterm>
<glossdef>
<para>If specified, connections FROM this interface are to
be tracked so that responses may be routed back out this
same interface. </para>
<para>You want specify 'track' if internet hosts will be
connecting to local servers through this provider.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>balance</glossterm>
<glossdef>
<para>The providers that have 'default' specified will get
outbound traffic load-balanced among them.</para>
</glossdef>
</glossentry>
</glosslist>
</glossdef>
</glossentry>
</glossdiv>
</glossary>
</section>
<section>
<title>Example</title>
<para>The configuration in the figure at the top of this section would
be specified as follows:</para>
<programlisting>#NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS
ISP1 1 1 main eth0 206.124.146.254 track,balance
ISP2 2 2 main eth1 130.252.99.254 track,balance</programlisting>
</section>
</section>
<section id="RouteTarget">
<title>Experimental Routing with Shorewall 2.3.3 and Later</title>
<para>Beginning with Shorewall 2.2.3, Shorewall is integrated with the <para>Beginning with Shorewall 2.2.3, Shorewall is integrated with the
ROUTE target extension available from Netfilter Patch-O-Matic-NG (<ulink ROUTE target extension available from Netfilter Patch-O-Matic-NG (<ulink
@ -215,7 +402,11 @@
<warning> <warning>
<para>As of this writing, I know of no distribution that is shipping a <para>As of this writing, I know of no distribution that is shipping a
kernel or iptables with the ROUTE target patch included. This means that kernel or iptables with the ROUTE target patch included. This means that
you must patch and build your own kernel and iptables. </para> you must patch and build your own kernel and iptables in order to be
able to use the feature described in this section. <emphasis
role="bold">This code remains experimental</emphasis> since there is no
intent by the Netfilter team to ever submit the ROUTE target patch for
inclusion in the official kernels from kernel.org.</para>
</warning> </warning>
<para>See <ulink url="FAQ.htm#faq42">Shorewall FAQ 42</ulink> for <para>See <ulink url="FAQ.htm#faq42">Shorewall FAQ 42</ulink> for
@ -224,7 +415,13 @@
determination.</para> determination.</para>
<para>Routing with Shorewall is specified through entries in <para>Routing with Shorewall is specified through entries in
/etc/shorewall/routes. Columns in this file are as follows:</para> /etc/shorewall/routes. Note that entries in the /etc/shorewall/routes file
override the routing specified in your routing tables. These rules
generate Netfilter rules in the mangle tables FORWARD chain or OUTPUT
chain depending whether the packets are being routed through the firewall
or originate on the firewall itself (see figure above).</para>
<para>Columns in this file are as follows:</para>
<glosslist> <glosslist>
<glossentry> <glossentry>
@ -334,6 +531,57 @@
</glossdef> </glossdef>
</glossentry> </glossentry>
<glossentry>
<glossterm>TEST</glossterm>
<glossdef>
<para>Defines a test on the existing packet or connection mark. The
rule will match only if the test returns true. Tests have the
format</para>
<blockquote>
<para>[!]&lt;value&gt;[/&lt;mask&gt;][:C]</para>
</blockquote>
<para>where:</para>
<glosslist>
<glossentry>
<glossterm>!</glossterm>
<glossdef>
<para>Inverts the test (not equal)</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>&lt;value&gt;</glossterm>
<glossdef>
<para>Value of the packet or connection mark.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>&lt;mask&gt;</glossterm>
<glossdef>
<para>A mask to be applied to the mark before testing</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>:C</glossterm>
<glossdef>
<para>Designates a connection mark. If omitted, the packet
mark's value is tested</para>
</glossdef>
</glossentry>
</glosslist>
</glossdef>
</glossentry>
<glossentry> <glossentry>
<glossterm>INTERFACE</glossterm> <glossterm>INTERFACE</glossterm>
@ -355,8 +603,8 @@
</glosslist> </glosslist>
<para>The idea here is that traffic that matches the SOURCE, DEST, PROTO, <para>The idea here is that traffic that matches the SOURCE, DEST, PROTO,
PORT(S) and SOURCE PORT(S) columns is routed out of the INTERFACE through PORT(S), SOURCE PORT(S) and TEST columns is routed out of the INTERFACE
the optional GATEWAY.</para> through the optional GATEWAY.</para>
<blockquote> <blockquote>
<para>Example:</para> <para>Example:</para>
@ -366,17 +614,12 @@
your DMZ. You would use the following entry in your DMZ. You would use the following entry in
/etc/shorewall/routes:</para> /etc/shorewall/routes:</para>
<programlisting>#SOURCE DEST PROTO PORT(S) SOURCE INTERFACE GATEWAY <programlisting>#SOURCE DEST PROTO PORT(S) SOURCE TEST INTERFACE GATEWAY
# PORT(S) # PORT(S)
eth1 0.0.0.0/0 tcp 80 - eth1 192.168.3.22</programlisting> eth1 0.0.0.0/0 tcp 80 - - eth1 192.168.3.22</programlisting>
<para>This entry specifies that "traffic coming in through eth1 to TCP <para>This entry specifies that "traffic coming in through eth1 to TCP
port 80 is to be routed out of eth1 to gateway 192.168.3.22".</para> port 80 is to be routed out of eth1 to gateway 192.168.3.22".</para>
</blockquote> </blockquote>
<para>Note that entries in the /etc/shorewall/routes file override the
routing specified in your routing tables. These rules generate Netfilter
rules in the mangle tables FORWARD chain or OUTPUT chain (see figure
above).</para>
</section> </section>
</article> </article>

8
Shorewall-docs2/UPnP.xml
View File

@ -15,7 +15,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2005-05-07</pubdate> <pubdate>2005-05-16</pubdate>
<copyright> <copyright>
<year>2005</year> <year>2005</year>
@ -39,7 +39,7 @@
<para>In Shorewall 2.2.4, support was added for UPnP (Universal Plug and <para>In Shorewall 2.2.4, support was added for UPnP (Universal Plug and
Play) using linux-igd (<ulink Play) using linux-igd (<ulink
url="http://linux-idg.sourceforge.net">http://linux-idg.sourceforge.net</ulink>). url="http://linux-igd.sourceforge.net">http://linux-igd.sourceforge.net</ulink>).
UPnP is required by a number of popular applications including MSN UPnP is required by a number of popular applications including MSN
IM.</para> IM.</para>
@ -83,7 +83,7 @@
</section> </section>
<section> <section>
<title>linux-idg Configuration</title> <title>linux-igd Configuration</title>
<para>In /etc/upnpd.conf, you will want:</para> <para>In /etc/upnpd.conf, you will want:</para>
@ -128,7 +128,7 @@ allowinUPnP loc fw</programlisting>
forwardUPnP net loc</programlisting> forwardUPnP net loc</programlisting>
<para>You must also ensure that you have a route to 224.0.0.0/4 on your <para>You must also ensure that you have a route to 224.0.0.0/4 on your
internal (local) interface as described in the linux-idg internal (local) interface as described in the linux-igd
documentation.</para> documentation.</para>
</section> </section>
</article> </article>

BIN
Shorewall-docs2/images/TwoISPs.png Executable file
View File

Binary file not shown.

442
Shorewall-docs2/images/TwoISPs.vdx Executable file
View File

File diff suppressed because one or more lines are too long

107
Shorewall-docs2/starting_and_stopping_shorewall.xml
View File

@ -15,7 +15,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2005-04-13</pubdate> <pubdate>2005-05-15</pubdate>
<copyright> <copyright>
<year>2004</year> <year>2004</year>
@ -48,7 +48,45 @@
to interact with Shorewall. Normally the root user's PATH includes to interact with Shorewall. Normally the root user's PATH includes
<filename>/sbin</filename> and the program can be run from a shell <filename>/sbin</filename> and the program can be run from a shell
prompt by simply typing <command>shorewall</command> followed by a prompt by simply typing <command>shorewall</command> followed by a
command. To see a list of supported commands, use the command.</para>
<warning>
<para>In some releases of KDE, the default configuration of the
<emphasis role="bold">konsole</emphasis> program is brain dead with
respect to the "Root Console". It executes the command "su" where it
should execute "su -"; the latter will cause a login shell to be
created which will in turn set PATH properly. You can correct this
problem as follows:</para>
<orderedlist>
<listitem>
<para>Click on "Settings" on the toolbar and select "Configure
Konsole"</para>
</listitem>
<listitem>
<para>Select the "Session" tab.</para>
</listitem>
<listitem>
<para>Click on "Root Console"</para>
</listitem>
<listitem>
<para>Change the Execute command from "su" to "su -"</para>
</listitem>
<listitem>
<para>Click on "Save Session"</para>
</listitem>
<listitem>
<para>Click on "Ok"</para>
</listitem>
</orderedlist>
</warning>
<para>To see a list of supported commands, use the
<command>help</command> command:</para> <command>help</command> command:</para>
<programlisting><command>shorewall help</command></programlisting> <programlisting><command>shorewall help</command></programlisting>
@ -61,10 +99,11 @@
<listitem> <listitem>
<para><filename>/etc/shorewall</filename> — The default directory <para><filename>/etc/shorewall</filename> — The default directory
where Shorewall looks for configuration files. See the section where Shorewall looks for configuration files. See the sections
entitled <link linkend="AltConfig">Alternate Configuration entitled <link linkend="AddDirectories">Additional Configuration
Directories</link> for information about how you can direct Shorewall Directories</link> and <link linkend="AltConfig">Alternate
to look in other directories.</para> Configuration Directories</link> for information about how you can
direct Shorewall to look in other directories.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -237,7 +276,7 @@
is much faster than starting Shorewall using the normal mechanism of is much faster than starting Shorewall using the normal mechanism of
reading the configuration files and running reading the configuration files and running
<command>iptables</command> dozens or even hundreds of times. <command>iptables</command> dozens or even hundreds of times.
<filename>/etc/init.d/shorewall</filename> <filename>By default, /etc/init.d/shorewall</filename>
(<filename>/etc/rc.d/firewall.rc</filename>) uses the -f option when (<filename>/etc/rc.d/firewall.rc</filename>) uses the -f option when
it is processing a request to start Shorewall.</para> it is processing a request to start Shorewall.</para>
</listitem> </listitem>
@ -271,16 +310,52 @@
shell prompt to remove these files).</para> shell prompt to remove these files).</para>
</section> </section>
<section> <section id="AddDirectories">
<title id="AltConfig">Alternate Configuration Directories</title> <title>Additional Configuration Directories</title>
<para>As explained above, Shorewall normally looks for configuration files <para>The CONFIG_PATH setting in
in the directory <filename class="directory">/etc/shorewall</filename>. <filename>/etc/shorewall/shorewall.conf</filename> determines where
The <command>shorewall start</command>, <command>shorewall Shorewall looks for configuration files. The default setting is
restart</command>, <command>shorewall check</command>, and CONFIG_PATH=<filename
<command>shorewall try </command>commands allow you to specify a different class="directory">/etc/shorewall</filename>:<filename
directory for Shorewall to check before looking in <filename class="directory">/usr/share/shorewall</filename> which means that
class="directory">/etc/shorewall</filename>.</para> <filename class="directory">/etc/shorewall</filename> is searched first
and if the file is not found then <filename
class="directory">/usr/share/shorewall</filename> is searched. You can
change the value of CONFIG_PATH to cause additional directories to be
searched but CONFIG_PATH should <emphasis>always</emphasis> include both
<filename class="directory">/etc/shorewall</filename> and <filename
class="directory">/usr/share/shorewall</filename>.</para>
<para>When an alternate configuration directory is specified as described
in the <link linkend="AddDirectories">next section</link>, that directory
is searched <emphasis>before</emphasis> those directories listed in
CONFIG_PATH.</para>
<para>Example - Search <filename
class="directory">/etc/shorewall</filename>, <filename
class="directory">/etc/shorewall/actiondir</filename> and <filename
class="directory">/usr/share/shorewall</filename> in that order:</para>
<programlisting>CONFIG_PATH=/etc/shorewall:/etc/shorewall/actiondir:/usr/share/shorewall</programlisting>
<para>The above is the setting that I use and it allows me to place all of
my user-defined 'action.' files in <filename
class="directory">/etc/shorewall/actiondir</filename>.</para>
</section>
<section id="AltConfig">
<title>Alternate Configuration Directories</title>
<para>As explained <link linkend="AddDirectories">above</link>, Shorewall
normally looks for configuration files in the directories specified by the
CONFIG_PATH option in <filename
class="directory">/etc/shorewall/shorewall.conf</filename>. The
<command>shorewall start</command>, <command>shorewall restart</command>,
<command>shorewall check</command>, and <command>shorewall try
</command>commands allow you to specify an additional directory for
Shorewall to check before looking in the directories listed in
CONFIG_PATH.</para>
<para>Shorewall versions before Shorewall 2.2.0:</para> <para>Shorewall versions before Shorewall 2.2.0:</para>