extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-02 19:49:08 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update to IPv6 doc

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9389 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2009-02-01 18:35:06 +00:00
parent 0e49b9ced8
commit 555636bff8
2 changed files with 35 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/IPv6Support.xml
View File

@ -48,7 +48,8 @@
<orderedlist> <orderedlist>
<listitem> <listitem>
<para>Kernel 2.6.25 or later.</para> <para><ulink url="FAQ.htm#faq80a">Kernel 2.6.25 or
later</ulink>.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -493,15 +494,15 @@ ACCEPT net:wlan0:&lt;2002:ce7c:92b4::3&gt; tcp
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Shorewall-common 4.3.4 or later.</para> <para>Shorewall-common 4.2.4 or later.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Shorewall-perl 4.3.4 or later.</para> <para>Shorewall-perl 4.2.4 or later.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Shorewall6 4.3.4 or later.</para> <para>Shorewall6 4.2.4 or later.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>

39
docs/MultiISP.xml
View File

@ -1082,8 +1082,10 @@ shorewall 2 2 - eth0 192.168.1.254 track,balance=2,optional<
monitoring script <filename>swping</filename>. The monitoring script <filename>swping</filename>. The
<filename>swping</filename> file is available in the main directory <filename>swping</filename> file is available in the main directory
contained in the Shorewall-common tarball and is included in the contained in the Shorewall-common tarball and is included in the
Shorewall-common documentation directory on the Shorewall-common Shorewall-common documentation directory on the Shorewall-common RPM.
RPM.</para> The script is inspired by Angsuman Chakraborty's <ulink
url="http://blog.taragana.com/index.php/archive/how-to-load-balancing-failover-with-dual-multi-wan-adsl-cable-connections-on-linux/">gwping</ulink>
script.</para>
<para>For those not on 4.2.6 yet, the script may be downloaded from <para>For those not on 4.2.6 yet, the script may be downloaded from
<ulink <ulink
@ -1097,7 +1099,19 @@ shorewall 2 2 - eth0 192.168.1.254 track,balance=2,optional<
</important> </important>
<para>The script should be copied to a directory on root's PATH such as <para>The script should be copied to a directory on root's PATH such as
<filename>/usr/local/sbin/.</filename></para> <filename>/usr/local/sbin/</filename>.</para>
<para>The script works by sending pings to <emphasis>target</emphasis>
IP addresses through each external interface. These targets must not
depend on any routes other than those that are present in the main
routing table. That ensures that a route is available to the target even
when the target's interface is not working and Shorewall has omitted it
from the routing configuration. An interface is assumed to be
<firstterm>up</firstterm> when a specified number (UP_COUNT) of
consecutive ping operations succeed. Similarly, an interface is assumed
to be <firstterm>down</firstterm> when a specified number (DOWN_COUNT)
of consecutive ping operations fail. You can specify the interval
between pings (PING_INTERVAL).</para>
<para>The script monitors two interfaces but it is a trivial exercise to <para>The script monitors two interfaces but it is a trivial exercise to
extend it to more than two. At the top are a number of variables to extend it to more than two. At the top are a number of variables to
@ -1108,10 +1122,11 @@ shorewall 2 2 - eth0 192.168.1.254 track,balance=2,optional<
# #
FAMILY=4 FAMILY=4
# #
# The commands to run when the status of a line changes. Both commands will be executed. # The commands to run when the status of a line changes. Multiple commands may be specified
# when separated by semicolons (";")
# #
COMMANDA= COMMAND=
COMMANDB="ip -$FAMILY route ls"
... ...
# #
# Interfaces to monitor -- you may use shell variables from your params file # Interfaces to monitor -- you may use shell variables from your params file
@ -1142,7 +1157,7 @@ UP_COUNT=5
# #
DOWN_COUNT=2</programlisting> DOWN_COUNT=2</programlisting>
<para>If you leave COMMANDA empty, the script sets its value <para>If you leave COMMAND empty, the script sets its value
automatically depending on whether Shorewall-lite is installed.</para> automatically depending on whether Shorewall-lite is installed.</para>
<para>When the status of an interface changes:</para> <para>When the status of an interface changes:</para>
@ -1151,8 +1166,9 @@ DOWN_COUNT=2</programlisting>
<listitem> <listitem>
<para>For each interface, a file is placed in /etc/shorewall to <para>For each interface, a file is placed in /etc/shorewall to
record the status of the interface: either 0 (UP) or 1 (DOWN). The record the status of the interface: either 0 (UP) or 1 (DOWN). The
name of the file is<emphasis> interface</emphasis>.status where name of the file is
<emphasis>interface</emphasis> is the interface (e.g., <filename><replaceable>interface</replaceable>.status</filename>
where <replaceable>interface</replaceable> is the interface (e.g.,
<filename>eth0.status</filename>).</para> <filename>eth0.status</filename>).</para>
</listitem> </listitem>
@ -1212,6 +1228,11 @@ fi</programlisting></para>
run two copies; one for IPv4 and one for IPv6.</para> run two copies; one for IPv4 and one for IPv6.</para>
</listitem> </listitem>
<listitem>
<para>It can only detect the gateway for interfaces managed by
dhcpcd.</para>
</listitem>
<listitem> <listitem>
<para>It's method of determining whether an interface is up or down <para>It's method of determining whether an interface is up or down
is crude. You will normally specify the default gateway for each is crude. You will normally specify the default gateway for each