LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Modified Files: 

Linux+IPv6-HOWTO.sgml : broken URLs and spelling fixes
This commit is contained in:
pbldp 2002-12-20 15:00:51 +00:00
parent 2f7a33a2c9
commit 2a59e5972f
1 changed files with 33 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
LDP/howto/docbook/Linux+IPv6-HOWTO.sgml
View File

@ -8,12 +8,12 @@
<firstname>Peter </firstname><surname>Bieringer</surname><affiliation><address> <email>pb at bieringer.de</email> </address> </affiliation>
</author>
<revhistory>
<revision> <revnumber>Release 0.35</revnumber> <date>2002-12-15</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
<revision> <revnumber>Release 0.36</revnumber> <date>2002-12-16</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
<revision> <revnumber>Release 0.35</revnumber> <date>2002-12-11</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
<revision> <revnumber>Release 0.34</revnumber> <date>2002-11-19</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
<revision> <revnumber>Release 0.33</revnumber> <date>2002-11-18</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
</revhistory>
<abstract><para>The goal of the Linux IPv6 HOWTO is to answer both basic and advanced questions about IPv6 on the Linux operating system. This HOWTO will provide the reader with enough information to install, configure, and use IPv6 applications on Linux machines.</para></abstract></bookinfo>
<chapter id="chapter-general"><title>General</title><remark>CVS-ID: &dollar;Id: Linux+IPv6-HOWTO.lyx,v 1.41 2002/11/25 22:34:37 pbldp Exp &dollar;</remark><para>Information about available translations you will find in section <link linkend="general-translations">Translations</link>.</para><sect1 id="general-copright"><title>Copyright, license and others</title><sect2><title>Copyright</title><para>Written and Copyright (C) 2001-2002 by Peter Bieringer</para></sect2>
<chapter id="chapter-general"><title>General</title><remark>CVS-ID: &dollar;Id: Linux+IPv6-HOWTO.lyx,v 1.43 2002/12/11 22:02:03 pbldp Exp &dollar;</remark><para>Information about available translations you will find in section <link linkend="general-translations">Translations</link>.</para><sect1 id="general-copright"><title>Copyright, license and others</title><sect2><title>Copyright</title><para>Written and Copyright (C) 2001-2002 by Peter Bieringer</para></sect2>
<sect2><title>License</title><para>This Linux IPv6 HOWTO is published under GNU GPL version 2:
@ -130,7 +130,7 @@
]]><![CDATA[Itu&-ZQ82s>J%s99FJXT
]]></programlisting><blockquote><para>Info: <emphasis>ipv6calc</emphasis> is an IPv6 address format calculator and converter program and can be found here: <ulink url="http://www.bieringer.de/linux/IPv6/ipv6calc/">ipv6calc</ulink></para></blockquote></sect1>
<sect1><title>FAQ (Basics)</title><sect2><title>Why is the name IPv6 and not IPv5 as successor for IPv4?</title><para>On any IP header, the first 4 bits are reserved for protocol version. So theoretically a protocol number between 0 and 15 is possible:</para><itemizedlist><listitem><para>4: is already used for IPv4</para></listitem><listitem><para>5: is reserved for the Stream Protocol (STP, <ulink url="http://www.faqs.org/rfcs/rfc1819.html">RFC 1819 / Internet Stream Protocol Version 2</ulink>) (which never really made it to the public)</para></listitem></itemizedlist><para>The next free number was 6. Hence IPv6 was born!</para></sect2>
<sect2><title>IPv6 addresses: why such a high number of bits?</title><para>During the design of IPv4, people thought that 32 bits were enough for the world. Looking back into the past, 32 bits were enough until now and will perhaps be enough for another few years. However, 32 bits are not enough to provide each network device with a global address in the future. Think about mobile phones, cars (including electronic devices on its CAN-bus), toasters, refrigerators, light switches, and so on...</para><para>So designers have chosen 128 bits, 4 times more in length and 2^96 greater in size than in IPv4 today.</para><para>The usable size is smaller than it may appear however. This is because in the currently defined address schema, 64 bits are used for interface identifiers. The other 64 bits are used for routing. Assuming the current strict levels of aggregation (/48, /35, ...), it is still possible to &quot;run out&quot; of space, but hopefully not in the near future.</para><para>See also for more information <ulink url="http://www.faqs.org/rfcs/rfc1715.html">RFC 1715 / The H Ratio for Address Assignment Efficiency</ulink> and <ulink url="http://www.faqs.org/rfcs/rfc1715.html">RFC 3194 / The Host-Density Ratio for Address Assignment Efficiency</ulink>.</para></sect2>
<sect2><title>IPv6 addresses: why such a high number of bits?</title><para>During the design of IPv4, people thought that 32 bits were enough for the world. Looking back into the past, 32 bits were enough until now and will perhaps be enough for another few years. However, 32 bits are not enough to provide each network device with a global address in the future. Think about mobile phones, cars (including electronic devices on its CAN-bus), toasters, refrigerators, light switches, and so on...</para><para>So designers have chosen 128 bits, 4 times more in length and 2^96 greater in size than in IPv4 today.</para><para>The usable size is smaller than it may appear however. This is because in the currently defined address schema, 64 bits are used for interface identifiers. The other 64 bits are used for routing. Assuming the current strict levels of aggregation (/48, /35, ...), it is still possible to &quot;run out&quot; of space, but hopefully not in the near future.</para><para>See also for more information <ulink url="http://www.faqs.org/rfcs/rfc1715.html">RFC 1715 / The H Ratio for Address Assignment Efficiency</ulink> and <ulink url="http://www.faqs.org/rfcs/rfc3194.html">RFC 3194 / The Host-Density Ratio for Address Assignment Efficiency</ulink>.</para></sect2>
<sect2><title>IPv6 addresses: why so small a number of bits on a new design?</title><para>While, there are (possibly) some people (only know about Jim Fleming...) on the Internet who are thinking about IPv8 and IPv16, their design is far away from acceptance and implementation. In the meantime 128 bits was the best choice regarding header overhead and data transport. Consider the minimum Maximum Transfer Unit (MTU) in IPv4 (576 octets) and in IPv6 (1280 octets), the header length in IPv4 is 20 octets (minimum, can increase to 60 octets with IPv4 options) and in IPv6 is 48 octets (fixed). This is 3.4 &percnt; of MTU in IPv4 and 3.8 &percnt; of MTU in IPv6. This means the header overhead is almost equal. More bits for addresses would require bigger headers and therefore more overhead. Also, consider the maximum MTU on normal links (like Ethernet today): it's 1500 octets (in special cases: 9k octets using Jumbo frames). Ultimately, it wouldn't be a proper design if 10 &percnt; or 20 &percnt; of transported data in a Layer-3 packet were used for addresses and not for payload.</para></sect2>
</sect1>
</chapter>
@ -622,7 +622,7 @@ You can still apply for one of these prefixes, see here <ulink url="http://www.6
]]></programlisting><para>Note: Don't use spaces around the &quot;=&quot; on setting values. Also on multiple values per line, quote them like e.g.</para><programlisting><![CDATA[# sysctl -w net.ipv4.ip_local_port_range="32768 61000"
]]><![CDATA[net.ipv4.ip_local_port_range = 32768 61000
]]></programlisting></sect3>
<sect3><title>Additionals</title><para>Note: There are sysctl versions in the wild which displaying &quot;/&quot; instead of the &quot;.&quot;</para><para>For more details take a look into sysctl's manpage.</para><para>Hint: for digging fast into the settings, use the option &quot;-a&quot; (display all entries) in conjunction with &quot;grep&quot;</para></sect3>
<sect3><title>Additionals</title><para>Note: There are sysctl versions in the wild which displaying &quot;/&quot; instead of the &quot;.&quot;</para><para>For more details take a look into sysctl's manpage.</para><para>Hint: for digging fast into the settings, use the option &quot;-a&quot; (display all entries) in conjunction with &quot;grep&quot;.</para></sect3>
</sect2>
<sect2><title>Values found in /proc-filesystems</title><para>There are several formats seen in /proc-filesystem:</para><itemizedlist><listitem><para>BOOLEAN: simple a &quot;0&quot; (false) or a &quot;1&quot; (true)</para></listitem><listitem><para>INTEGER: an integer value, can be unsigned, too</para></listitem><listitem><para>more sophisticated lines with several values: sometimes a header line is displayed also, if not, have a look into the kernel source to retrieve information about the meaning of each value...</para></listitem></itemizedlist></sect2>
</sect1>
@ -659,7 +659,7 @@ You can still apply for one of these prefixes, see here <ulink url="http://www.6
<sect3><title>delay_first_probe_time</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 5</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
<sect3><title>proxy_delay</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 80</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
</sect2>
<sect2><title>route/*</title><para>Change global settings for routing</para><sect3><title>flush</title><para>Removed in newer kernel releases - more to be filled.</para></sect3>
<sect2><title>route/*</title><para>Change global settings for routing.</para><sect3><title>flush</title><para>Removed in newer kernel releases - more to be filled.</para></sect3>
<sect3><title>gc_interval</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 30</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
<sect3><title>gc_thresh</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 1024</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
<sect3><title>mtu_expires</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 600</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
@ -668,7 +668,6 @@ You can still apply for one of these prefixes, see here <ulink url="http://www.6
<sect3><title>gc_timeout</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 60</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
<sect3><title>min_adv_mss</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 12</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
<sect3><title>max_size</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 4096</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
<sect3><title>max_size</title><itemizedlist><listitem><para>Type: INTEGER</para></listitem><listitem><para>Default: 4096</para></listitem></itemizedlist><para>More to be filled.</para></sect3>
</sect2>
</sect1>
<sect1 id="proc-sys-net-ipv4"><title>IPv6-related entries in /proc/sys/net/ipv4/</title><para>At the moment (and this will be until IPv4 is completly converted to an independend kernel module) some switches are also used here for IPv6.</para><sect2><title>ip_*</title><sect3><title>ip_local_port_range</title><para>This control setting is used by IPv6 also.</para></sect3>
@ -677,13 +676,13 @@ You can still apply for one of these prefixes, see here <ulink url="http://www.6
<sect2><title>icmp_*</title><para>This control settings are not used by IPv6. To enable ICMPv6 rate limting (which is very recommended because of the capability of ICMPv6 storms) netfilter-v6 rules must be used.</para></sect2>
<sect2><title>others</title><para>Unknown, but probably not used by IPv6.</para></sect2>
</sect1>
<sect1 id="proc-net"><title>IPv6-related entries in /proc/net/</title><para>In /proc/net there are several read-only entries available. You cannot retrieve information using &quot;sysctl&quot; here, so use e.g. &quot;cat&quot;.</para><sect2><title>if_inet6</title><itemizedlist><listitem><para>Type: One line per addresss containing multiple values</para></listitem></itemizedlist><para>Here all configured IPv6 addresses are shown in a special format. The example displays for loopback interface only. The meaning is shown below (see &quot;net/ipv6/addrconf.c&quot; for more)</para><programlisting><![CDATA[# cat /proc/net/if_inet6
<sect1 id="proc-net"><title>IPv6-related entries in /proc/net/</title><para>In /proc/net there are several read-only entries available. You cannot retrieve information using &quot;sysctl&quot; here, so use e.g. &quot;cat&quot;.</para><sect2><title>if_inet6</title><itemizedlist><listitem><para>Type: One line per addresss containing multiple values</para></listitem></itemizedlist><para>Here all configured IPv6 addresses are shown in a special format. The example displays for loopback interface only. The meaning is shown below (see &quot;net/ipv6/addrconf.c&quot; for more).</para><programlisting><![CDATA[# cat /proc/net/if_inet6
]]><![CDATA[00000000000000000000000000000001 01 80 10 80 lo
]]><![CDATA[+------------------------------+ ++ ++ ++ ++ ++
]]><![CDATA[| | | | | |
]]><![CDATA[1 2 3 4 5 6
]]></programlisting><orderedlist><listitem><para>IPv6 address displayed in 32 hexadecimal chars without colons as separator</para></listitem><listitem><para>Netlink device number (interface index) in hexadecimal (see &quot;ip addr&quot; , too)</para></listitem><listitem><para>Prefix length in hexadecimal</para></listitem><listitem><para>Scope value (see kernel source &quot; include/net/ipv6.h&quot; and &quot;net/ipv6/addrconf.c&quot; for more)</para></listitem><listitem><para>Interface flags (see &quot;include/linux/rtnetlink.h&quot; and &quot;net/ipv6/addrconf.c&quot; for more)</para></listitem><listitem><para>Device name</para></listitem></orderedlist></sect2>
<sect2><title>ipv6_route</title><itemizedlist><listitem><para>Type: One line per route containing multiple values</para></listitem></itemizedlist><para>Here all configured IPv6 routes are shown in a special format. The example displays for loopback interface only. The meaning is shown below (see &quot;net/ipv6/route.c&quot; for more)</para><programlisting><![CDATA[# cat /proc/net/ipv6_route
<sect2><title>ipv6_route</title><itemizedlist><listitem><para>Type: One line per route containing multiple values</para></listitem></itemizedlist><para>Here all configured IPv6 routes are shown in a special format. The example displays for loopback interface only. The meaning is shown below (see &quot;net/ipv6/route.c&quot; for more).</para><programlisting><![CDATA[# cat /proc/net/ipv6_route
]]><![CDATA[00000000000000000000000000000000 00 00000000000000000000000000000000 00
]]><![CDATA[+------------------------------+ ++ +------------------------------+ ++
]]><![CDATA[| | | |
@ -787,12 +786,12 @@ You can still apply for one of these prefixes, see here <ulink url="http://www.6
]]><![CDATA[¬ prefix=2002:0102:0304:1::/64)(prefix info: LAR valid_ltime=2592000,
]]><![CDATA[¬ preffered_ltime=604800, prefix=3ffe:ffff:0:1::/64)(src lladdr:
]]><![CDATA[¬ 0:12:34:12:34:50) (len 88, hlim 255)
]]></programlisting><para>Router with link-local address &quot;fe80::212:34ff:fe12:3450&quot; send an advertisement to the all-node-on-link multicast address &quot;ff02::1&quot; containing two prefixes &quot;2002:0102:0304:1::/64&quot; (lifetime 30 s) and &quot;3ffe:ffff:0:1::/64&quot; (lifetime 2592000 s) including its own layer 2 MAC address &quot;0:12:34:12:34:50&quot;</para></sect3>
]]></programlisting><para>Router with link-local address &quot;fe80::212:34ff:fe12:3450&quot; send an advertisement to the all-node-on-link multicast address &quot;ff02::1&quot; containing two prefixes &quot;2002:0102:0304:1::/64&quot; (lifetime 30 s) and &quot;3ffe:ffff:0:1::/64&quot; (lifetime 2592000 s) including its own layer 2 MAC address &quot;0:12:34:12:34:50&quot;.</para></sect3>
<sect3><title>Router solicitation</title><programlisting><![CDATA[15:44:21.152646 fe80::212:34ff:fe12:3456 > ff02::2: icmp6: router solicitation
]]><![CDATA[¬ (src lladdr: 0:12:34:12:34:56) (len 16, hlim 255)
]]></programlisting><para>Node with link-local address &quot;fe80::212:34ff:fe12:3456&quot; and layer 2 MAC address &quot;0:12:34:12:34:56&quot; is looking for a router on-link, therefore sending this solicitation to the all-router-on-link multicast address &quot;ff02::2&quot;.</para></sect3>
</sect2>
<sect2><title>Neighbor discovery</title><sect3><title>Neighbor discovery solicitation for duplicate address detection</title><para>Following packets are sent by a node with layer 2 MAC address &quot;0:12:34:12:34:56&quot; during autoconfiguration to check whether a potential address is already used by another node on the link sending this to the solicited-node link-local multicast address</para><itemizedlist><listitem><para>Node wants to configure its link-local address &quot;fe80::212:34ff:fe12:3456&quot;, checks for duplicate now</para></listitem></itemizedlist><programlisting><![CDATA[15:44:17.712338 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has
<sect2><title>Neighbor discovery</title><sect3><title>Neighbor discovery solicitation for duplicate address detection</title><para>Following packets are sent by a node with layer 2 MAC address &quot;0:12:34:12:34:56&quot; during autoconfiguration to check whether a potential address is already used by another node on the link sending this to the solicited-node link-local multicast address.</para><itemizedlist><listitem><para>Node wants to configure its link-local address &quot;fe80::212:34ff:fe12:3456&quot;, checks for duplicate now</para></listitem></itemizedlist><programlisting><![CDATA[15:44:17.712338 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has
]]><![CDATA[¬ fe80::212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim 255)
]]></programlisting><itemizedlist><listitem><para>Node wants to configure its global address &quot;2002:0102:0304:1:212:34ff:fe12:3456&quot; (after receiving advertisement shown above), checks for duplicate now</para></listitem></itemizedlist><programlisting><![CDATA[15:44:21.905596 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has
]]><![CDATA[¬ 2002:0102:0304:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32,
@ -810,7 +809,7 @@ You can still apply for one of these prefixes, see here <ulink url="http://www.6
</sect2>
</sect1>
</chapter>
<chapter id="chapter-support-persistent-configuration"><title>Support for persistent IPv6 configuration in Linux distributions</title><para>Some Linux distribution contain already support of a persistent IPv6 configuration using existing or new configuration and script files and some hook in the IPv4 script files.</para><sect1><title>Red Hat Linux and &quot;clones&quot;</title><para>Since starting writing the <ulink url="http://www.bieringer.de/linux/IPv6/">IPv6 & Linux - HowTo</ulink> it was my intention to enable a persistent IPv6 configuration which catch most of the wished cases like host-only, router-only, dual-homed-host, router with second stub network, normal tunnels, 6to4 tunnels, and so on. Nowadays there exists a set of configuration and script files which do the job very well (never heard about real problems, but I don't know how many use the set. Because this configuration and scrips files are extended from time to time, they got their own HOWTO page: <ulink url="http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/scripts/current/">IPv6-HOWTO/scripts/current</ulink>. Because I began my IPv6 experience using a Red Hat Linux 5.0 clone, my IPv6 development systems are mostly Red Hat Linux based now, it's kind a logic that the scripts are developed for this kind of distribution (so called <emphasis>historic issue</emphasis>). Also it was very easy to extend some configuration files, create new ones and create some simple hook for calling IPv6 setup during IPv4 setup.</para><para>Fortunately, in Red Hat Linux since 7.1 a snapshot of my IPv6 scripts is included, this was and is still further on assisted by Pekka Savola.</para><para>Mandrake since version 8.0 also includes an IPv6-enabled initscript package, but a minor bug still prevents usage (&quot;ifconfig&quot; misses &quot;inet6&quot; before &quot;add&quot;).</para><sect2><title>Test for IPv6 support of network configuration scripts</title><para>You can test, whether your Linux distribution contain support for persistent IPv6 configuration using my set. Following script library should exist:</para><programlisting><![CDATA[/etc/sysconfig/network-scripts/network-functions-ipv6
<chapter id="chapter-support-persistent-configuration"><title>Support for persistent IPv6 configuration in Linux distributions</title><para>Some Linux distribution contain already support of a persistent IPv6 configuration using existing or new configuration and script files and some hook in the IPv4 script files.</para><sect1><title>Red Hat Linux and &quot;clones&quot;</title><para>Since starting writing the <ulink url="http://www.bieringer.de/linux/IPv6/">IPv6 & Linux - HowTo</ulink> it was my intention to enable a persistent IPv6 configuration which catch most of the wished cases like host-only, router-only, dual-homed-host, router with second stub network, normal tunnels, 6to4 tunnels, and so on. Nowadays there exists a set of configuration and script files which do the job very well (never heard about real problems, but I don't know how many use the set). Because this configuration and scrips files are extended from time to time, they got their own HOWTO page: <ulink url="http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/scripts/current/">IPv6-HOWTO/scripts/current</ulink>. Because I began my IPv6 experience using a Red Hat Linux 5.0 clone, my IPv6 development systems are mostly Red Hat Linux based now, it's kind a logic that the scripts are developed for this kind of distribution (so called <emphasis>historic issue</emphasis>). Also it was very easy to extend some configuration files, create new ones and create some simple hook for calling IPv6 setup during IPv4 setup.</para><para>Fortunately, in Red Hat Linux since 7.1 a snapshot of my IPv6 scripts is included, this was and is still further on assisted by Pekka Savola.</para><para>Mandrake since version 8.0 also includes an IPv6-enabled initscript package, but a minor bug still prevents usage (&quot;ifconfig&quot; misses &quot;inet6&quot; before &quot;add&quot;).</para><sect2><title>Test for IPv6 support of network configuration scripts</title><para>You can test, whether your Linux distribution contain support for persistent IPv6 configuration using my set. Following script library should exist:</para><programlisting><![CDATA[/etc/sysconfig/network-scripts/network-functions-ipv6
]]></programlisting><para>Auto-magically test:</para><programlisting><![CDATA[# test -f /etc/sysconfig/network-scripts/network-functions-ipv6 && echo "Main
]]><![CDATA[¬ IPv6 script library exists"
]]></programlisting><para>The version of the library is important if you miss some features. You can get it executing following (or easier look at the top of the file):</para><programlisting><![CDATA[# source /etc/sysconfig/network-scripts/network-functions-ipv6 &&
@ -834,9 +833,9 @@ In versions 8.x they completly change their configuration setup. </para><sect2><
<chapter id="chapter-autoconfiguration"><title>Auto-configuration and mobility</title><sect1><title>Stateless auto-configuration</title><para>Is supported and seen on the assigned link-local address after an IPv6-enabled interface is up.</para></sect1>
<sect1><title>Stateful auto-configuration using Router Advertisement Daemon (radvd)</title><para>to be filled. See <link linkend="hints-daemons-radvd">radvd daemon autoconfiguration</link> below.</para></sect1>
<sect1><title>Dynamic Host Configuration Protocol v6 (DHCPv6)</title><para>to be filled.</para></sect1>
<sect1><title>Mobility</title><para>to be filled.</para><para>For the moment, see <ulink url="http://www.mipl.mediapoli.com/">Mobile IPv6 for Linux(MIPL) homepage</ulink> for more details</para></sect1>
<sect1><title>Mobility</title><para>to be filled.</para><para>For the moment, see <ulink url="http://www.mipl.mediapoli.com/">Mobile IPv6 for Linux(MIPL) homepage</ulink> for more details.</para></sect1>
</chapter>
<chapter id="chapter-firewalling-security"><title>Firewalling</title><para>IPv6 firewalling is important, especially if using IPv6 on internal networks with global IPv6 addresses. Because unlike at IPv4 networks where in common internal hosts are protected automatically using private IPv4 addresses like <ulink url="http://www.faqs.org/rfcs/rfc1918.html">RFC 1918 / Address Allocation for Private Internets</ulink> or <ulink url="http://www.glossary-tech.com/apipa.htm">APIPA / Automatic Private IP Addressing</ulink>, in IPv6 normally global addresses are used and someone with IPv6 connectivity can reach all internal IPv6 enabled nodes.</para><sect1 id="firewalling-netfilter6"><title>Firewalling using netfilter6 </title><para>Native IPv6 firewalling is only supported in kernel versions 2.4+. In older 2.2- you can only filter IPv6-in-IPv4 by protocol 41. </para><para>Attention: no warranty that described rules or examples are really protect your system! </para><para>Audit your ruleset after installation, see <xref linkend="IPv6-security-auditing"> for more.</para><sect2><title>More information</title><itemizedlist><listitem><para><ulink url="http://www.netfilter.org/">Netfilter project</ulink></para></listitem><listitem><para><ulink url="http://lists.samba.org/pipermail/netfilter/">maillist archive of netfilter users</ulink></para></listitem><listitem><para><ulink url="http://lists.samba.org/pipermail/netfilter-devel/">maillist archive of netfilter developers</ulink></para></listitem><listitem><para><ulink url="http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#netfilter6 ">Unofficial status informations</ulink></para></listitem></itemizedlist></sect2>
<chapter id="chapter-firewalling-security"><title>Firewalling</title><para>IPv6 firewalling is important, especially if using IPv6 on internal networks with global IPv6 addresses. Because unlike at IPv4 networks where in common internal hosts are protected automatically using private IPv4 addresses like <ulink url="http://www.faqs.org/rfcs/rfc1918.html">RFC 1918 / Address Allocation for Private Internets</ulink> or Automatic Private IP Addressing (APIPA)<ulink url="http://www.google.com/search?q=apipa+microsoft">Google search for Microsoft + APIPA</ulink>, in IPv6 normally global addresses are used and someone with IPv6 connectivity can reach all internal IPv6 enabled nodes.</para><sect1 id="firewalling-netfilter6"><title>Firewalling using netfilter6 </title><para>Native IPv6 firewalling is only supported in kernel versions 2.4+. In older 2.2- you can only filter IPv6-in-IPv4 by protocol 41. </para><para>Attention: no warranty that described rules or examples can really protect your system! </para><para>Audit your ruleset after installation, see <xref linkend="IPv6-security-auditing"> for more.</para><sect2><title>More information</title><itemizedlist><listitem><para><ulink url="http://www.netfilter.org/">Netfilter project</ulink></para></listitem><listitem><para><ulink url="http://lists.samba.org/pipermail/netfilter/">maillist archive of netfilter users</ulink></para></listitem><listitem><para><ulink url="http://lists.samba.org/pipermail/netfilter-devel/">maillist archive of netfilter developers</ulink></para></listitem><listitem><para><ulink url="http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#netfilter6 ">Unofficial status informations</ulink></para></listitem></itemizedlist></sect2>
</sect1>
<sect1><title>Preparation</title><sect2><title>Get sources</title><para>Get the latest kernel source: <ulink url="http://www.kernel.org/">http://www.kernel.org/</ulink></para><para>Get the latest iptables package: </para><itemizedlist><listitem><para>Source tarball (for kernel patches): <ulink url="http://www.netfilter.org/">http://www.netfilter.org/</ulink></para></listitem><listitem><para>Source RPM for rebuild of binary (for RedHat systems): <ulink url="ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/">ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/</ulink> or perhaps also at <ulink url="http://www.netcore.fi/pekkas/linux/ipv6/ ">http://www.netcore.fi/pekkas/linux/ipv6/ </ulink></para></listitem></itemizedlist></sect2>
<sect2><title>Extract sources</title><para>Change to source directory: </para><programlisting><![CDATA[# cd /path/to/src
@ -874,7 +873,7 @@ In versions 8.x they completly change their configuration setup. </para><sect2><
]]><![CDATA[ MARK target support: module
]]></programlisting><para>Configure other related to your system, too </para><para>Compilation and installing: see the kernel section here and other HOWTOs </para></sect2>
<sect2><title>Rebuild and install binaries of iptables</title><para>Make sure, that upper kernel source tree is also available at /usr/src/linux/ </para><para>Rename older directory </para><programlisting><![CDATA[# mv /usr/src/linux /usr/src/linux.old
]]></programlisting><para>Create a new softlink </para><programlisting><![CDATA[# ln /path/to/src/linux-version-iptables-version /usr/src/linux
]]></programlisting><para>Create a new softlink </para><programlisting><![CDATA[# ln -s /path/to/src/linux-version-iptables-version /usr/src/linux
]]></programlisting><para>Rebuild SRPMS </para><programlisting><![CDATA[# rpm --rebuild /path/to/SRPMS/iptables-version-release.src.rpm
]]></programlisting><para>Install new iptables packages (iptables + iptables-ipv6) </para><itemizedlist><listitem><para>On RH 7.1 systems, normally, already an older version is installed, therefore use &quot;freshen&quot; </para></listitem></itemizedlist><programlisting><![CDATA[# rpm -Fhv /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm
]]></programlisting><itemizedlist><listitem><para>If not already installed, use &quot;install&quot; </para></listitem></itemizedlist><programlisting><![CDATA[# rpm -ihv /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm
@ -902,14 +901,15 @@ In versions 8.x they completly change their configuration setup. </para><sect2><
]]></programlisting><itemizedlist><listitem><para>Allow outgoing ICMPv6 through tunnels </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -A OUTPUT -o sit+ -p icmpv6 -j ACCEPT
]]></programlisting><para>Newer kernels allow specifying of ICMPv6 types:</para><programlisting><![CDATA[# ip6tables -A INPUT -p icmpv6 --icmpv6-type echo-request -j ACCEPT
]]></programlisting></sect3>
<sect3><title>Rate-limiting</title><para>Because it can happen (author already saw it to times) that an ICMPv6 storm will raise up, you should use available rate limiting for at least ICMPv6 ruleset. In addition logging rules should also get rate limiting to prevent DoS attacks against syslog and storage of log file partition. An example for a rate limited ICMPv6 looks like:</para><programlisting><![CDATA[# ip6tables -A INPUT --protocol icmpv6 --icmpv6-type echo-request -j ACCEPT --match limit --limit 30/minute
<sect3><title>Rate-limiting</title><para>Because it can happen (author already saw it to times) that an ICMPv6 storm will raise up, you should use available rate limiting for at least ICMPv6 ruleset. In addition logging rules should also get rate limiting to prevent DoS attacks against syslog and storage of log file partition. An example for a rate limited ICMPv6 looks like:</para><programlisting><![CDATA[# ip6tables -A INPUT --protocol icmpv6 --icmpv6-type echo-request -j ACCEPT
]]><![CDATA[¬ --match limit --limit 30/minute
]]></programlisting></sect3>
<sect3><title>Allow incoming SSH</title><para>Here an example is shown for a ruleset which allows incoming SSH connection from a specified IPv6 address </para><itemizedlist><listitem><para>Allow incoming SSH from 3ffe:ffff:100::1/128 </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -A INPUT -i sit+ -p tcp -s 3ffe:ffff:100::1/128 --sport 512:65535
]]><![CDATA[¬ --dport 22 -j ACCEPT
]]></programlisting><itemizedlist><listitem><para>Allow response packets (at the moment IPv6 connection tracking isn't in mainstream netfilter6 implemented) </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -A OUTPUT -o sit+ -p tcp -d 3ffe:ffff:100::1/128 --dport 512:65535
]]><![CDATA[¬ --sport 22 ! --syn j ACCEPT
]]></programlisting></sect3>
<sect3><title>Enable tunneled IPv6-in-IPv4</title><para>Tto accept tunneled IPv6-in-IPv4 packets, you have to insert rules in your IPv4 firewall setup relating to such packets, for example </para><itemizedlist><listitem><para>Accept incoming IPv6-in-IPv4 on interface ppp0 </para></listitem></itemizedlist><programlisting><![CDATA[# iptables -A INPUT -i ppp0 -p ipv6 -j ACCEPT
<sect3><title>Enable tunneled IPv6-in-IPv4</title><para>To accept tunneled IPv6-in-IPv4 packets, you have to insert rules in your IPv4 firewall setup relating to such packets, for example </para><itemizedlist><listitem><para>Accept incoming IPv6-in-IPv4 on interface ppp0 </para></listitem></itemizedlist><programlisting><![CDATA[# iptables -A INPUT -i ppp0 -p ipv6 -j ACCEPT
]]></programlisting><itemizedlist><listitem><para>Allow outgoing IPv6-in-IPv4 to interface ppp0 </para></listitem></itemizedlist><programlisting><![CDATA[# iptables -A OUTPUT -o ppp0 -p ipv6 -j ACCEPT
]]></programlisting><para>If you have only a static tunnel, you can specify the IPv4 addresses, too, like </para><itemizedlist><listitem><para>Accept incoming IPv6-in-IPv4 on interface ppp0 from tunnel endpoint 1.2.3.4 </para></listitem></itemizedlist><programlisting><![CDATA[# iptables -A INPUT -i ppp0 -p ipv6 -s 1.2.3.4 -j ACCEPT
]]></programlisting><itemizedlist><listitem><para>Allow outgoing IPv6-in-IPv4 to interface ppp0 to tunnel endpoint 1.2.3.4 </para></listitem></itemizedlist><programlisting><![CDATA[# iptables -A OUTPUT -o ppp0 -p ipv6 -d 1.2.3.4 -j ACCEPT
@ -917,7 +917,7 @@ In versions 8.x they completly change their configuration setup. </para><sect2><
<sect3><title>Protection against incoming TCP connection requests</title><para>VERY RECOMMENDED! For security issues you should really insert a rule which blocks incoming TCP connection requests. Adapt &quot;-i&quot; option, if other interface names are in use! </para><itemizedlist><listitem><para>Block incoming TCP connection requests to this host </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -I INPUT -i sit+ -p tcp --syn -j DROP
]]></programlisting><itemizedlist><listitem><para>Block incoming TCP connection requests to hosts behind this router </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -I FORWARD -i sit+ -p tcp --syn -j DROP
]]></programlisting><para>Perhaps the rules have to be placed below others, but that is work you have to think about it. Best way is to create a script and execute rules in a specified way. </para></sect3>
<sect3><title>Protection against incoming UDP connection requests</title><para>ALSO RECOMMENDED! Like mentioned on my firewall information it's possible to control the ports on outgoing UDP/TCP sessions. So if all of your local IPv6 systems are use local ports e.g. from 32768 to 60999 you are able to filter UDP connections also (until connection tracking works) like: </para><itemizedlist><listitem><para>Block incoming UDP packets which cannot be responses of outgoing requests of this host </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -I INPUT -i sit+ -p udp ! --dport 32768:60999 -j DROP
<sect3><title>Protection against incoming UDP connection requests</title><para>ALSO RECOMMENDED! Like mentioned on my firewall information it's possible to control the ports on outgoing UDP/TCP sessions. So if all of your local IPv6 systems are using local ports e.g. from 32768 to 60999 you are able to filter UDP connections also (until connection tracking works) like: </para><itemizedlist><listitem><para>Block incoming UDP packets which cannot be responses of outgoing requests of this host </para></listitem></itemizedlist><programlisting><![CDATA[# ip6tables -I INPUT -i sit+ -p udp ! --dport 32768:60999 -j DROP
]]></programlisting><itemizedlist><listitem><para>Block incoming UDP packets which cannot be responses of forwarded requests of hosts behind this router </para></listitem></itemizedlist><programlisting><![CDATA[ip6tables -I FORWARD -i sit+ -p udp ! --dport 32768:60999 -j DROP
]]></programlisting></sect3>
</sect2>
@ -1110,7 +1110,7 @@ CHECK destination IPv6 addresses TWICE before starting a scan.</para></sect2>
]]></programlisting></sect3>
</sect2>
<sect2><title>IPv6 DNS zone files examples</title><para>Some information can be also found at <ulink url="http://www.isi.edu/~bmanning/v6DNS.html">IPv6 DNS Setup Information (article)</ulink>. Perhaps also helpful is the <ulink url="http://tools.fpsn.net/ipv6-inaddr/">IPv6 Reverse DNS zone builder for BIND 8/9 (webtool)</ulink>.</para></sect2>
<sect2><title>Serving IPv6 related DNS data</title><para>For IPv6 new types and root zones for reverse lookups are defined:</para><itemizedlist><listitem><para>AAAA and reverse IP6.INT: specified in <ulink url="http://www.faqs.org/rfcs/rfc1886.html">RFC 1886 / DNS Extensions to support IP version 6</ulink>, usable since BIND version 4.9.6</para></listitem><listitem><para>A6, DNAME (DEPRICATED NOW!) and reverse IP6.ARPA: specified in <ulink url="http://www.faqs.org/rfcs/rfc2874.html">RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering</ulink>, usable since BIND 9, but see also an information about the current state at <ulink url="http://www.ietf.org/internet-drafts/">draft-ietf-dnsext-ipv6-addresses-00.txt</ulink></para></listitem></itemizedlist><para>Perhaps filled later more content, for the meantime take a look at given RFCs and</para><itemizedlist><listitem><para>AAAA and reverse IP6.INT: <ulink url="http://www.isi.edu/~bmanning/v6DNS.html">IPv6 DNS Setup Information</ulink></para></listitem><listitem><para>A6, DNAME (DEPRICATED NOW!) and reverse IP6.ARPA: take a look into chapter 4 and 6 of the BIND 9 Administrator Reference Manual (ARM) distributed which the bind-package or get this here: <ulink url="http://www.nominum.com/resources/documentation/Bv9ARM.pdf">BIND version 9 ARM (PDF)</ulink></para></listitem></itemizedlist><para>Because IP6.INT is deprecated (but still in use), a DNS server which will support IPv6 information has to serve both reverse zones.</para><sect3><title>Current best practice</title><para>Because there are some troubles around using the new formats, current best practice is:</para><para>Forward lookup support:</para><itemizedlist><listitem><para>AAAA</para></listitem></itemizedlist><para>Reverse lookup support:</para><itemizedlist><listitem><para>Reverse nibble format for zone ip6.int (FOR BACKWARD COMPATIBILITY)</para></listitem><listitem><para>Reverse nibble format for zone ip6.arpa (RECOMMENDED)</para></listitem></itemizedlist></sect3>
<sect2><title>Serving IPv6 related DNS data</title><para>For IPv6 new types and root zones for reverse lookups are defined:</para><itemizedlist><listitem><para>AAAA and reverse IP6.INT: specified in <ulink url="http://www.faqs.org/rfcs/rfc1886.html">RFC 1886 / DNS Extensions to support IP version 6</ulink>, usable since BIND version 4.9.6</para></listitem><listitem><para>A6, DNAME (DEPRECATED NOW!) and reverse IP6.ARPA: specified in <ulink url="http://www.faqs.org/rfcs/rfc2874.html">RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering</ulink>, usable since BIND 9, but see also an information about the current state at <ulink url="http://www.ietf.org/internet-drafts/">draft-ietf-dnsext-ipv6-addresses-00.txt</ulink></para></listitem></itemizedlist><para>Perhaps filled later more content, for the meantime take a look at given RFCs and</para><itemizedlist><listitem><para>AAAA and reverse IP6.INT: <ulink url="http://www.isi.edu/~bmanning/v6DNS.html">IPv6 DNS Setup Information</ulink></para></listitem><listitem><para>A6, DNAME (DEPRECATED NOW!) and reverse IP6.ARPA: take a look into chapter 4 and 6 of the BIND 9 Administrator Reference Manual (ARM) distributed which the bind-package or get this here: <ulink url="http://www.nominum.com/content/documents/bind9arm.pdf">BIND version 9 ARM (PDF)</ulink></para></listitem></itemizedlist><para>Because IP6.INT is deprecated (but still in use), a DNS server which will support IPv6 information has to serve both reverse zones.</para><sect3><title>Current best practice</title><para>Because there are some troubles around using the new formats, current best practice is:</para><para>Forward lookup support:</para><itemizedlist><listitem><para>AAAA</para></listitem></itemizedlist><para>Reverse lookup support:</para><itemizedlist><listitem><para>Reverse nibble format for zone ip6.int (FOR BACKWARD COMPATIBILITY)</para></listitem><listitem><para>Reverse nibble format for zone ip6.arpa (RECOMMENDED)</para></listitem></itemizedlist></sect3>
</sect2>
<sect2><title>Checking IPv6-enabled connect</title><para>To check, whether BIND is listening on an IPv6 socket and serving data see following examples.</para><sect3><title>IPv6 connect, but denied by ACL</title><para>Specifying a dedicated server for the query, an IPv6 connect can be forced:</para><programlisting><![CDATA[$ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1
]]><![CDATA[Using domain server:
@ -1169,7 +1169,7 @@ CHECK destination IPv6 addresses TWICE before starting a scan.</para></sect2>
]]></programlisting><para>For simple tests use the telnet example already shown.</para></sect3>
</sect2>
</sect1>
<sect1 id="hints-daemons-radvd"><title>Router Advertisement Daemon (radvd)</title><para>The router advertisement daemon is very useful on a LAN, if clients should be auto-configured. The daemon itself should run a Linux router (not necessary the default IPv4 gateway). </para><para>You can specify some information and flags which should be contained in the advertisement. Common used are</para><itemizedlist><listitem><para>Prefix (needed)</para></listitem><listitem><para>Lifetime of the prefix</para></listitem><listitem><para>Frequency of sending advertisements (optional)</para></listitem></itemizedlist><para>After a proper configuration, the daemon sends advertisements through specified interfaces and clients are hopefully receive them and auto-magically configure addresses with received prefix and the default route.</para><sect2><title>Configuring radvd</title><sect3><title>Simple configuration</title><para>Radvd's config file is normally /etc/radvd.conf. An simple example looks like following:</para><programlisting><![CDATA[interface eth0 {
<sect1 id="hints-daemons-radvd"><title>Router Advertisement Daemon (radvd)</title><para>The router advertisement daemon is very useful on a LAN, if clients should be auto-configured. The daemon itself should run on the Linux default IPv6 gateway router (it's not required that this is also the default IPv4 gateway, so pay attention who on your LAN is sending router advertisements). </para><para>You can specify some information and flags which should be contained in the advertisement. Common used are</para><itemizedlist><listitem><para>Prefix (needed)</para></listitem><listitem><para>Lifetime of the prefix</para></listitem><listitem><para>Frequency of sending advertisements (optional)</para></listitem></itemizedlist><para>After a proper configuration, the daemon sends advertisements through specified interfaces and clients are hopefully receive them and auto-magically configure addresses with received prefix and the default route.</para><sect2><title>Configuring radvd</title><sect3><title>Simple configuration</title><para>Radvd's config file is normally /etc/radvd.conf. An simple example looks like following:</para><programlisting><![CDATA[interface eth0 {
]]><![CDATA[ AdvSendAdvert on;
]]><![CDATA[ MinRtrAdvInterval 3;
]]><![CDATA[ MaxRtrAdvInterval 10;
@ -1281,12 +1281,12 @@ Hans Peter Dittler
2. akt. und erweiterte Auflage 2002 dpunkt.verlag, ISBN 3-89864-149-X</para></listitem><listitem><para>Das neue Internetprotokoll IPv6 <ulink url="http://www.amazon.de/exec/obidos/ASIN/3446216855">bei Amazon</ulink>
Herbert Wiese
2002 Carl Hanser Verlag, ISBN 3446216855</para></listitem></itemizedlist></sect2>
<sect2><title>Articles, Books, Online Reviews (mixed)</title><itemizedlist><listitem><para><ulink url="http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html">Getting Connected with 6to4</ulink> by Huber Feyrer, 06/01/2001</para></listitem><listitem><para><ulink url="http://researchcenter.zdnet.com/data/detail?id=1001711171_237&amp;type=RES&amp;x=120054357">How Long the Aversion to IP Version 6</ulink> - Review of META Group, Inc., full access needs (free) registration at META Group, Inc.</para></listitem><listitem><para><ulink url="http://www.oreillynet.com/search/index.ncsp?sp-q=IPv6">O'reilly Network search for keyword IPv6</ulink> results in 29 hits (28. January 2002)</para></listitem><listitem><para><ulink url="http://www.nwfusion.com/news/2000/1023ipv6.html">Wireless boosting IPv6</ulink> by Carolyn Duffy Marsan, 10/23/2000</para></listitem><listitem><para><ulink url="http://www.oreilly.fr/catalogue/ipv6.html">IPv6, théorie et pratique</ulink> (french) 2e édition, mars 1999, O'Reilly (??? no newer one available ???) ISBN: 2-84177-085-0</para></listitem><listitem><para><ulink url="http://www.ip6.com/index.html">Internetworking IPv6 with Cisco Routers</ulink> by Silvano Gai, McGrawHill Italia, 1997 13 chapters and appendix A-D are downloadable as PDF-documents.</para></listitem><listitem><para><ulink url="http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/">Secure and Dynamic Tunnel Broker</ulink> by Vegar Skaerven Wang, Master of Engineering Thesis in Computer Science, 2.June 2000, Faculty of Science, Dep.of Computer Science, University of Tromso, Norway.</para></listitem><listitem><para><ulink url="http://www.netobjectdays.org/pdf/99/stja/doering.pdf">Aufbruch in die neue Welt - IPv6 in IPv4 Netzen</ulink> von Dipl.Ing. Ralf Döring, TU Illmenau, 1999</para></listitem><listitem><para><ulink url="http://www.csc.fi/~psavola/residential.html">Migration and Co-existence of IPv4 and IPv6 in Residential Networks</ulink> by Pekka Savola, CSC/FUNET, 2002</para></listitem><listitem><para><ulink url="http://www.sunny.ch/publications/f_ipv6.htm">IPv6 Essentials</ulink> written by Silvia Hagen, July 2002, O'Reilly <ulink url="http://www.oreilly.com/catalog/ipv6ess/">Order Number: 1258</ulink>, ISBN 0-5960-0125-8</para></listitem></itemizedlist></sect2>
<sect2><title>Articles, Books, Online Reviews (mixed)</title><itemizedlist><listitem><para><ulink url="http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html">Getting Connected with 6to4</ulink> by Huber Feyrer, 06/01/2001</para></listitem><listitem><para><ulink url="http://researchcenter.zdnet.com/data/detail?id=1001711171_237&amp;type=RES&amp;x=120054357">How Long the Aversion to IP Version 6</ulink> - Review of META Group, Inc., full access needs (free) registration at META Group, Inc.</para></listitem><listitem><para><ulink url="http://www.oreillynet.com/search/index.ncsp?sp-q=IPv6">O'reilly Network search for keyword IPv6</ulink> results in 29 hits (28. January 2002)</para></listitem><listitem><para><ulink url="http://www.nwfusion.com/news/2000/1023ipv6.html">Wireless boosting IPv6</ulink> by Carolyn Duffy Marsan, 10/23/2000</para></listitem><listitem><para><ulink url="http://www.oreilly.fr/catalogue/ipv6-3ed.html">IPv6, théorie et pratique</ulink> (french) 3e édition, mars 2002, O'Reilly, ISBN 2-84177-139-3</para></listitem><listitem><para><ulink url="http://www.ip6.com/index.html">Internetworking IPv6 with Cisco Routers</ulink> by Silvano Gai, McGrawHill Italia, 1997 13 chapters and appendix A-D are downloadable as PDF-documents.</para></listitem><listitem><para><ulink url="http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/">Secure and Dynamic Tunnel Broker</ulink> by Vegar Skaerven Wang, Master of Engineering Thesis in Computer Science, 2.June 2000, Faculty of Science, Dep.of Computer Science, University of Tromso, Norway.</para></listitem><listitem><para><ulink url="http://www.netobjectdays.org/pdf/99/stja/doering.pdf">Aufbruch in die neue Welt - IPv6 in IPv4 Netzen</ulink> von Dipl.Ing. Ralf Döring, TU Illmenau, 1999</para></listitem><listitem><para><ulink url="http://www.csc.fi/~psavola/residential.html">Migration and Co-existence of IPv4 and IPv6 in Residential Networks</ulink> by Pekka Savola, CSC/FUNET, 2002</para></listitem><listitem><para><ulink url="http://www.sunny.ch/publications/f_ipv6.htm">IPv6 Essentials</ulink> written by Silvia Hagen, July 2002, O'Reilly <ulink url="http://www.oreilly.com/catalog/ipv6ess/">Order Number: 1258</ulink>, ISBN 0-5960-0125-8</para></listitem></itemizedlist></sect2>
<sect2><title>Others</title><para>See following URL for more: <ulink url="http://www.switch.ch/lan/ipv6/references.html">SWITCH IPv6 Pilot / References</ulink></para></sect2>
</sect1>
<sect1 id="information-onlineinformation"><title>Online information</title><sect2 id="information-joinipv6"><title>Join the IPv6 backbone</title><para>More to be filled later...suggestions are welcome!</para><sect3 id="information-globalregistries"><title>Global registries</title><itemizedlist><listitem><para>IPv6 test backbone: <ulink url="http://www.6bone.net/6bone_hookup.html">6bone</ulink>, <ulink url="http://www.6bone.net/6bone_hookup.html">How to join 6bone</ulink></para></listitem></itemizedlist></sect3>
<sect3 id="information-majorregionregistries"><title>Major regional registries</title><itemizedlist><listitem><para>America: <ulink url="http://www.arin.net/">ARIN</ulink>, <ulink url="http://www.arin.net/regserv.html">ARIN / registration page</ulink>, <ulink url="http://www.arin.net/regserv/ipv6/ipv6guidelines.html">ARIN / IPv6 guidelines</ulink></para></listitem><listitem><para>EMEA: <ulink url="http://www.ripe.net/">Ripe NCC</ulink>, <ulink url="http://www.ripe.net/ripencc/mem-services/registration/">Ripe NCC / registration page</ulink>, <ulink url="http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6.html">Ripe NCC / IPv6 registration</ulink></para></listitem><listitem><para>Asia/Pacific: <ulink url="http://www.apnic.net/">APNIC</ulink>, <ulink url="http://www.apnic.net/drafts/ipv6/">APNIC / IPv6 information</ulink></para></listitem><listitem><para>Latin America and Caribbea: <ulink url="http://lacnic.org/">LACNIC</ulink></para></listitem><listitem><para>Africa: <ulink url="http://www.afrinic.org/">AfriNIC</ulink></para></listitem></itemizedlist><para>Also a list of major (prefix length 35) allocations per local registry is available here: <ulink url="http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html">Ripe NCC / IPv6 allocations</ulink>.</para></sect3>
<sect3 id="information-joinipv6-tunnelbrokers"><title>Tunnel brokers</title><itemizedlist><listitem><para><ulink url="http://www.freenet6.net/">Freenet6</ulink>, Canada</para></listitem><listitem><para><ulink url="http://ipv6tb.he.net/">Hurricane Electric</ulink>, US backbone</para></listitem><listitem><para><ulink url="https://carmen.cselt.it/ipv6tb/">Centro Studi e Laboratory Telecomunicazioni</ulink>, Italy</para></listitem><listitem><para><ulink url="http://tunnel.be.wanadoo.com/">Wanadoo</ulink>, Belgium</para></listitem><listitem><para><ulink url="http://tb.6test.edu.cn/">CERTNET-Nokia</ulink>, China</para></listitem><listitem><para><ulink url="http://joshua.informatik.uni-leipzig.de/">Tunnelbroker Leipzig</ulink>, Germany - DialupUsers with dynamic IP's can get a fix IPv6 IP...</para></listitem><listitem><para><ulink url="http://www.iij.ad.jp/IPv6/index-e.html">Internet Initiative Japan</ulink>, Japan - with IPv6 native line service and IPv6 tunneling Service</para></listitem><listitem><para><ulink url="http://www.xs26.net/">XS26 - "Access to Six"</ulink>, Netherland - with POPs in Slovak Republic, Czech Republic, Netherlands, Germany and Hungary.</para></listitem><listitem><para><ulink url="http://www.ipng.nl/">IPng Netherland</ulink>, Netherland - Intouch, SurfNet, AMS-IX, UUNet, Cistron, RIPE NCC and AT&amp;T are connected at the AMS-IX. It is possible (there are requirements...) to get an static tunnel.</para></listitem><listitem><para><ulink url="http://www.uninett.no/testnett/index.en.html">UNINETT</ulink>, Norway - Pilot IPv6 Service (for Customers): tunnelbroker &amp; address allocation</para></listitem><listitem><para><ulink url="http://www.uk.v6.ntt.net/">NTT Europe</ulink>, <ulink url="http://www.nttv6.net/">NTT Euroope</ulink>, United Kingdom - IPv6 Trial. IPv4 Tunnel and native IPv6 leased Line connections. POPs are located in London, UK Dusseldorf, Germany New Jersey, USA (East Coast) Cupertino, USA (West Coast) Tokyo, Japan</para></listitem><listitem><para><ulink url="http://www.es.net/hypertext/welcome/pr/ipv6.html">ESnet</ulink>, USA - Energy Sciences Network: Tunnel Registry &amp; Address Delegation for directly connected ESnet sites and ESnet collaborators.</para></listitem><listitem><para><ulink url="http://www.6ren.net/">6REN</ulink>, USA - The 6ren initiative is being coordinated by the Energy Sciences Network (ESnet), the network for the Energy Research program of the US Dept. of Energy, located at the University of California's Lawrence Berkeley National Laboratory</para></listitem></itemizedlist><para>See also here for more information and URLs: <ulink url="http://www.ipv6-net.de/">ipv6-net.org</ulink>.</para></sect3>
<sect1 id="information-onlineinformation"><title>Online information</title><sect2 id="information-joinipv6"><title>Join the IPv6 backbone</title><para>More to be filled later...suggestions are welcome!</para><sect3 id="information-globalregistries"><title>Global registries</title><itemizedlist><listitem><para>IPv6 test backbone: <ulink url="http://www.6bone.net/">6bone</ulink>, <ulink url="http://www.6bone.net/6bone_hookup.html">How to join 6bone</ulink></para></listitem></itemizedlist></sect3>
<sect3 id="information-majorregionregistries"><title>Major regional registries</title><itemizedlist><listitem><para>America: <ulink url="http://www.arin.net/">ARIN</ulink>, <ulink url="http://www.arin.net/library/index.htm#templates">ARIN / registration page</ulink>, <ulink url="http://www.arin.net/library/index.htm">ARIN / IPv6 guidelines</ulink></para></listitem><listitem><para>EMEA: <ulink url="http://www.ripe.net/">Ripe NCC</ulink>, <ulink url="http://www.ripe.net/ripencc/mem-services/registration/">Ripe NCC / registration page</ulink>, <ulink url="http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6.html">Ripe NCC / IPv6 registration</ulink></para></listitem><listitem><para>Asia/Pacific: <ulink url="http://www.apnic.net/">APNIC</ulink>, <ulink url="http://www.apnic.net/services/ipv6_guide.html">APNIC / IPv6 ressource guide</ulink></para></listitem><listitem><para>Latin America and Caribbea: <ulink url="http://lacnic.org/">LACNIC</ulink>, <ulink url="http://lacnic.net/en/bt-IPv6.html">IPv6 Registration Services</ulink>, <ulink url="http://lacnic.net/en/chapter-4-en.pdf">IPv6 Allocation Policy</ulink></para></listitem><listitem><para>Africa: <ulink url="http://www.afrinic.org/">AfriNIC</ulink></para></listitem></itemizedlist><para>Also a list of major (prefix length 35) allocations per local registry is available here: <ulink url="http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html">Ripe NCC / IPv6 allocations</ulink>.</para></sect3>
<sect3 id="information-joinipv6-tunnelbrokers"><title>Tunnel brokers</title><itemizedlist><listitem><para><ulink url="http://www.freenet6.net/">Freenet6</ulink>, Canada</para></listitem><listitem><para><ulink url="http://ipv6tb.he.net/">Hurricane Electric</ulink>, US backbone</para></listitem><listitem><para><ulink url="https://carmen.cselt.it/ipv6tb/">Centro Studi e Laboratory Telecomunicazioni</ulink>, Italy</para></listitem><listitem><para><ulink url="http://tunnel.be.wanadoo.com/">Wanadoo</ulink>, Belgium</para></listitem><listitem><para><ulink url="http://tb.6test.edu.cn/">CERTNET-Nokia</ulink>, China</para></listitem><listitem><para><ulink url="http://joshua.informatik.uni-leipzig.de/">Tunnelbroker Leipzig</ulink>, Germany - DialupUsers with dynamic IP's can get a fix IPv6 IP...</para></listitem><listitem><para><ulink url="http://www.iij.ad.jp/IPv6/index-e.html">Internet Initiative Japan</ulink>, Japan - with IPv6 native line service and IPv6 tunneling Service</para></listitem><listitem><para><ulink url="http://www.xs26.net/">XS26 - "Access to Six"</ulink>, Netherland - with POPs in Slovak Republic, Czech Republic, Netherlands, Germany and Hungary.</para></listitem><listitem><para><ulink url="http://www.ipng.nl/">IPng Netherland</ulink>, Netherland - Intouch, SurfNet, AMS-IX, UUNet, Cistron, RIPE NCC and AT&amp;T are connected at the AMS-IX. It is possible (there are requirements...) to get an static tunnel.</para></listitem><listitem><para><ulink url="http://www.uninett.no/testnett/index.en.html">UNINETT</ulink>, Norway - Pilot IPv6 Service (for Customers): tunnelbroker &amp; address allocation</para></listitem><listitem><para><ulink url="http://www.uk.v6.ntt.net/">NTT Europe</ulink>, <ulink url="http://www.nttv6.net/">NTT</ulink>, United Kingdom - IPv6 Trial. IPv4 Tunnel and native IPv6 leased Line connections. POPs are located in London, UK Dusseldorf, Germany New Jersey, USA (East Coast) Cupertino, USA (West Coast) Tokyo, Japan</para></listitem><listitem><para><ulink url="http://www.es.net/hypertext/welcome/pr/ipv6.html">ESnet</ulink>, USA - Energy Sciences Network: Tunnel Registry &amp; Address Delegation for directly connected ESnet sites and ESnet collaborators.</para></listitem><listitem><para><ulink url="http://www.6ren.net/">6REN</ulink>, USA - The 6ren initiative is being coordinated by the Energy Sciences Network (ESnet), the network for the Energy Research program of the US Dept. of Energy, located at the University of California's Lawrence Berkeley National Laboratory</para></listitem></itemizedlist><para>See also here for more information and URLs: <ulink url="http://www.ipv6-net.de/">ipv6-net.org</ulink>.</para></sect3>
<sect3 id="information-joinipv6-6to4-tunneling"><title>6to4</title><itemizedlist><listitem><para><ulink url="http://www.kfu.com/~nsayer/6to4/">NSayer's 6to4 information</ulink></para></listitem><listitem><para><ulink url="http://www.faqs.org/rfcs/rfc3068.html">RFC 3068 / An Anycast Prefix for 6to4 Relay Routers</ulink></para></listitem></itemizedlist></sect3>
</sect2>
<sect2><title>Latest news</title><para>More to be filled later...suggestions are welcome!</para><itemizedlist><listitem><para><ulink url="http://hs247.com/">hs247 / IPv6 news and information</ulink>, also homepage for &num;ipv6 channel on EFnet</para></listitem><listitem><para><ulink url="http://bofh.st/ipv6/">bofh.st / latest IPv6 news</ulink> (but currently &lsqb;Jan 2002&rsqb; outdated...), also homepage for &num;IPv6 channel on IRCnet</para></listitem><listitem><para><ulink url="http://www.ipv6-net.de/">ipv6-net.org</ulink>, German forum</para></listitem></itemizedlist></sect2>
@ -1303,7 +1303,7 @@ Herbert Wiese
</term><listitem><para><ulink url="http://www.suse.com/">SuSE Linux</ulink></para></listitem></varlistentry><varlistentry><term>Mandrake
</term><listitem><para><ulink url="http://www.linux-mandrake.com/">Linux Mandrake</ulink></para></listitem></varlistentry></variablelist><para>For more see the <ulink url="http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html">IPv6+Linux Status Distributions</ulink> page.</para></sect3>
<sect3><title>General</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.org/">IPv6.org</ulink></para></listitem><listitem><para><ulink url="http://www.6bone.net/6bone_hookup.html">6bone</ulink></para></listitem><listitem><para><ulink url="http://www.cs-ipv6.lancs.ac.uk/">UK IPv6 Resource Centre</ulink> - UK</para></listitem><listitem><para><ulink url="http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/informationsquellen.html">JOIN: IPv6 information</ulink> - Germany, by the JOIN project team maintaining also <ulink url="http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/www.html">Links to external WWW pages comprising IPv6/IPng</ulink></para></listitem><listitem><para><ulink url="http://tipster6.ik.bme.hu/tipster6_en.html">TIPSTER6 project</ulink> - Hungary, &quot;Testing Experimental IPv6 Technology and Services in Hungary&quot;</para></listitem><listitem><para><ulink url="http://www.v6.wide.ad.jp/">WIDE project</ulink> - Japan</para></listitem><listitem><para><ulink url="http://www.switch.ch/lan/ipv6/">SWITCH IPv6 Pilot</ulink> - Switzerland</para></listitem><listitem><para><ulink url="http://www.feyrer.de/IPv6/">IPv6 Corner of Hubert Feyrer</ulink> - Germany</para></listitem><listitem><para><ulink url="http://www.vermicelli.pasta.cs.uit.no/ipv6/">Vermicelli Project</ulink> - Norway</para></listitem><listitem><para><ulink url="http://www.ipv6forum.com/">IPv6 Forum</ulink> - a world-wide consortium of leading Internet vendors, Research &amp; Education Networks...</para></listitem><listitem><para><ulink url="http://playground.sun.com/pub/ipng/html/ipng-main.html">Playground.sun.com / IPv6 Info Page</ulink> - maintained by Robert Hinden, Nokia</para></listitem><listitem><para><ulink url="http://www.nas.nasa.gov/Groups/LAN/IPv6/">NASA Ames Research Center</ulink> (old content)</para></listitem><listitem><para><ulink url="http://www.6init.com/">6INIT</ulink> - IPv6 Internet Initiative - an EU Fifth Framework Project under the IST Programme</para></listitem><listitem><para><ulink url="http://www.ipv6tf.org/">IPv6 Task Force (European Union)</ulink></para></listitem></itemizedlist><para>Something missing? Suggestions are welcome!</para></sect3>
<sect3><title>In Portuguese </title><itemizedlist><listitem><para><ulink url="http://ipng.ip6.fc.ul.pt/">IPv6 pages of Miguel Rosa</ulink> </para></listitem><listitem><para><ulink url="http://www.rcts.pt/ipv6/ipb6.htm">FCCN (National Foundation for the Scientific Computation)</ulink></para></listitem><listitem><para><ulink url="http://linuxgo.persogo.com.br/ipv6/">Grupo de Pesquisa em IPv6 do Brasil</ulink> </para></listitem><listitem><para><ulink url="http://www.ipv6.ualg.pt/">University of Algarve, Portugal</ulink> </para></listitem><listitem><para><ulink url="http://www.ipv6.mfa.eti.br/">IPv6 - MFA</ulink></para></listitem></itemizedlist></sect3>
<sect3><title>In Portuguese </title><itemizedlist><listitem><para><ulink url="http://ipng.ip6.fc.ul.pt/">IPv6 pages of Miguel Rosa</ulink> (broken?)</para></listitem><listitem><para><ulink url="http://www.fccn.pt/projectos/ipv6/index_html">FCCN (National Foundation for the Scientific Computation)</ulink></para></listitem><listitem><para><ulink url="http://www.ipv6.ualg.pt/">University of Algarve, Portugal</ulink> </para></listitem><listitem><para><ulink url="http://www.ipv6.mfa.eti.br/">IPv6 - MFA</ulink></para></listitem></itemizedlist></sect3>
</sect2>
<sect2><title>By countries</title><sect3><title>Australia</title><itemizedlist><listitem><para><ulink url="http://oversteer.bl.echidna.id.au/IPv6/">Carl's Australian IPv6 Pages</ulink> (old content)</para></listitem></itemizedlist></sect3>
<sect3><title>Belgium</title><itemizedlist><listitem><para><ulink url="http://vivaldi.belnet.be/ipv6/">BELNET</ulink> - the Belgian Research Network</para></listitem><listitem><para><ulink url="http://www.ipv6.euronet.be/">Euronet</ulink> - one of the biggest ISP's of Belgium...</para></listitem></itemizedlist></sect3>
@ -1313,7 +1313,7 @@ Herbert Wiese
<sect3><title>Japan</title><itemizedlist><listitem><para><ulink url="http://www.rtpro.yamaha.co.jp/RT/ipv6/">Yamaha IPv6</ulink> (sorry, all in japanese native ...)</para></listitem></itemizedlist></sect3>
<sect3><title>Korea</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.or.kr/english/index.new.htm">IPv6 Forum Korea</ulink> - Korean IPv6 Deployment Project</para></listitem></itemizedlist></sect3>
<sect3><title>Mexico</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.unam.mx/">IPv6 Mexico</ulink> (spain &amp; english version) - IPv6 Project Hompeage of The National Autonomous University of Mexico (UNAM)</para></listitem></itemizedlist></sect3>
<sect3><title>Netherland</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.surfnet.nl/">SURFnet</ulink> - SURFnet IPv6 Backbone</para></listitem><listitem><para><ulink url="http://www.stack.nl/">STACK</ulink>, <ulink url="http://www.ipv6.stack.nl/ipv6/">STACK (IPv6)</ulink> - Students' computer association of the Eindhoven University of Technology, Netherland.</para></listitem><listitem><para><ulink url="http://www.ipng.nl/">IPng.nl</ulink>, collaboration between WiseGuys and Intouch.</para></listitem></itemizedlist></sect3>
<sect3><title>Netherland</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.surfnet.nl/">SURFnet</ulink> - SURFnet IPv6 Backbone</para></listitem><listitem><para><ulink url="http://www.stack.nl/">STACK</ulink>, <ulink url="http://www.stack.nl/ipv6/">STACK (IPv6)</ulink> - Students' computer association of the Eindhoven University of Technology, Netherland.</para></listitem><listitem><para><ulink url="http://www.ipng.nl/">IPng.nl</ulink>, collaboration between WiseGuys and Intouch.</para></listitem></itemizedlist></sect3>
<sect3><title>United Kingdom</title><itemizedlist><listitem><para><ulink url="http://www.bt.com/ipv6/">British Telecom IPv6 Home</ulink> - BT's ISP IPv6 Trial, UK's first IPv6 Internet Exchange etc.</para></listitem></itemizedlist></sect3>
</sect2>
<sect2><title>By operating systems</title><sect3><title>Cisco IOS</title><itemizedlist><listitem><para><ulink url="http://www.cisco.com/warp/public/732/Tech/ipv6/">Cisco IOS IPv6 Entry Page</ulink></para></listitem></itemizedlist></sect3>
@ -1321,9 +1321,9 @@ Herbert Wiese
<sect3><title>Microsoft</title><itemizedlist><listitem><para><ulink url="http://www.microsoft.com/windows2000/technologies/communications/ipv6/default.asp">Microsoft Windows 2000 IPv6</ulink> </para></listitem><listitem><para><ulink url="http://www.research.microsoft.com/msripv6">MSRIPv6</ulink> - Microsoft Research Network - IPv6 Homepage </para></listitem><listitem><para><ulink url="http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp">Getting Started with the Microsoft IPv6 Technology Preview for Windows 2000</ulink></para></listitem></itemizedlist></sect3>
<sect3><title>*BSD</title><itemizedlist><listitem><para><ulink url="http://www.kame.net/">KAME project</ulink> - Japan, (*BSD)</para></listitem><listitem><para><ulink url="http://www.netbsd.org/Documentation/network/ipv6/">NetBSD's IPv6 Networking FAQ</ulink></para></listitem></itemizedlist></sect3>
<sect3><title>Solaris</title><itemizedlist><listitem><para><ulink url="http://www.sun.com/solaris/ipv6/">Sun Microsystems IPv6 Page for Solaris 8</ulink></para></listitem></itemizedlist></sect3>
<sect3><title>Sumitoma </title><itemizedlist><listitem><para><ulink url="http://www.sumitomo.com/htmls/randd/ipv6/ipv6.html">Sumitomo Electric has implemented IPv6 on Suminet 3700 family routers</ulink></para></listitem></itemizedlist></sect3>
<sect3><title>Sumitoma </title><itemizedlist><listitem><para><ulink url="http://playground.sun.com/pub/ipng/html/ipng-implementations.html#Sumitomo">Sumitomo Electric has implemented IPv6 on Suminet 3700 family routers</ulink></para></listitem></itemizedlist></sect3>
</sect2>
<sect2><title>Application lists</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.org/v6-apps.html">IPv6.org / IPv6 enabled applications</ulink></para></listitem><listitem><para><ulink url="http://freshmeat.net/search/?q=IPv6">Freshmeat / IPv6 search</ulink>, currently (02. May 2002) 51 projects</para></listitem></itemizedlist><sect3><title>Analyzer tools</title><itemizedlist><listitem><para><ulink url="http://ethereal.planetmirror.com/">Ethereal</ulink> - Ethereal is a free network protocol analyzer for Unix and Windows</para></listitem><listitem><para><ulink url="http://www.ip6.com/us/analyzer.htm">Radcom RC100-WL</ulink> - Download Radcom RC100-WL protocol analyzer version 3.20</para></listitem></itemizedlist></sect3>
<sect2><title>Application lists</title><itemizedlist><listitem><para><ulink url="http://www.ipv6.org/v6-apps.html">IPv6.org / IPv6 enabled applications</ulink></para></listitem><listitem><para><ulink url="http://freshmeat.net/search/?q=IPv6">Freshmeat / IPv6 search</ulink>, currently (14 Dec 2002) 62 projects</para></listitem></itemizedlist><sect3><title>Analyzer tools</title><itemizedlist><listitem><para><ulink url="http://ethereal.planetmirror.com/">Ethereal</ulink> - Ethereal is a free network protocol analyzer for Unix and Windows</para></listitem><listitem><para><ulink url="http://www.ip6.com/us/analyzer.htm">Radcom RC100-WL</ulink> - Download Radcom RC100-WL protocol analyzer version 3.20</para></listitem></itemizedlist></sect3>
</sect2>
</sect1>
<sect1 id="information-onlinetesttools"><title>Online test tools</title><para>More to be filled later...suggestions are welcome!</para><itemizedlist><listitem><para>finger, nslookup, ping, traceroute, whois: <ulink url="http://www.cs-ipv6.lancs.ac.uk/ipv6/testing/">UK IPv6 Resource Centre / The test page</ulink></para></listitem><listitem><para>ping, traceroute, tracepath, 6bone registry, DNS: <ulink url="http://www.join.uni-muenster.de/lab/testtools.html">JOIN / Testtools</ulink> (German language only, but should be no problem for non German speakers)</para></listitem><listitem><para>traceroute6, whois: <ulink url="http://www.ipng.nl/">IPng.nl</ulink></para></listitem></itemizedlist></sect1>
@ -1406,7 +1406,7 @@ Herbert Wiese
<entry align="center" valign="top"><para>6bone</para></entry>
<entry align="center" valign="top"><para>6bone (at) isi.edu</para></entry>
<entry align="center" valign="top"><para>English</para></entry>
<entry align="center" valign="top"><para><ulink url="http://www.6bone.net/6bone_email.html">Info</ulink>, <ulink url="http://ryouko.dgim.crc.ca/ipv6/">Threaded archive</ulink>, <ulink url="http://www.wcug.wwu.edu/lists/6bone/">Mirror of archive</ulink></para></entry>
<entry align="center" valign="top"><para><ulink url="http://www.6bone.net/6bone_email.html">Info</ulink>, <ulink url="http://mailman.isi.edu/pipermail/6bone/">Archive</ulink></para></entry>
</row>
<row>
<entry align="center" valign="top"><para>IPv6 discussions</para></entry>
@ -1446,13 +1446,14 @@ Herbert Wiese
<entry align="center" valign="top"><para>ipv6</para></entry>
<entry align="center" valign="top"><para>ipv6 (at) mfa.eti.br</para></entry>
<entry align="center" valign="top"><para>Portuguese</para></entry>
<entry align="center" valign="top"><para><ulink url="http://www.mfa.eti.br/listas.html">Info</ulink></para></entry>
<entry align="center" valign="top"><para><ulink url="http://www.marcelo.pro.br/mailman/listinfo/ipv6">Info</ulink></para></entry>
</row>
</tbody>
</tgroup></informaltable>
</para><para>(1) recommended for common Linux &amp; IPv6 issues.</para><para>(2) very recommended if you provide server applications.</para><para>Something missing? Suggestions are welcome!</para><para>Another list of maillists is available at <ulink url="http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/ipv6.infoquellen.html">JOIN Project / List of IPv6-related maillists</ulink>.</para></sect1>
</chapter>
<chapter><title>Revision history / Credits / The End</title><sect1 id="revision-history"><title>Revision history</title><para>Versions x.y are published on the Internet.</para><para>Versions x.y.z are work-in-progress and only published as LyX file on CVS.</para><sect2><title>Releases 0.x</title><variablelist><varlistentry><term>0.35
<chapter><title>Revision history / Credits / The End</title><sect1 id="revision-history"><title>Revision history</title><para>Versions x.y are published on the Internet.</para><para>Versions x.y.z are work-in-progress and only published as LyX file on CVS.</para><sect2><title>Releases 0.x</title><variablelist><varlistentry><term>0.36
</term><listitem><para>2002-12-16/PB: Check of and fix broken links (credits to Georg Käfer), some spelling fixes</para></listitem></varlistentry><varlistentry><term>0.35
</term><listitem><para>2002-12-11/PB: Some fixes and extensions</para></listitem></varlistentry><varlistentry><term>0.34.1
</term><listitem><para>2002-11-25/PB: Some fixes (e.g. broken linuxdoc URLs)</para></listitem></varlistentry><varlistentry><term>0.34
</term><listitem><para>2002-11-19/PB: Add information about German translation (work in progress), some fixes, create a small shortcut explanation list, extend &quot;used terms&quot; and add two German books</para></listitem></varlistentry><varlistentry><term>0.33
@ -1499,7 +1500,7 @@ Herbert Wiese
</sect1>
<sect1 id="credits"><title>Credits</title><para>The quickest way to be added to this nice list is to send bug fixes, corrections, and/or updates to me ;-).</para><para>If you want to do a major review, you can use the native LyX file (see <link linkend="general-original-source">original source</link>) and send diffs against it, because diffs against SGML don't help too much.</para><sect2 id="major-credits"><title>Major credits</title><itemizedlist><listitem><para>David Ranch &lt;dranch at trinnet dot net&gt;: For encouraging me to write this HOWTO, his editorial comments on the first few revisions, and his contributions to various IPv6 testing results on my IPv6 web site. Also for his major reviews and suggestions.</para></listitem><listitem><para>Pekka Savola &lt;pekkas at netcore dot fi&gt;: For major reviews, input and suggestions.</para></listitem><listitem><para>Martin F. Krafft &lt;madduck at madduck dot net&gt;: For grammar checks and general reviewing of the document.</para></listitem><listitem><para>John Ronan &lt;j0n at tssg dot wit dot ie&gt;: For grammar checks.</para></listitem></itemizedlist></sect2>
<sect2><title>Other credits</title><sect3><title>Document technique related</title><para>Writing a LDP HOWTO as a newbie (in LyX and exporting this to DocBook to conform to SGML) isn't as easy as some people say. There are some strange pitfalls... Nevertheless, thanks to:</para><itemizedlist><listitem><para>Authors of the <ulink url="http://www.tldp.org/LDP/LDP-Author-Guide/">LDP Author Guide</ulink></para></listitem><listitem><para>B. Guillon: For his <ulink url="http://perso.libertysurf.fr/bgu/doc/db4lyx/">DocBook with LyX HOWTO</ulink></para></listitem></itemizedlist></sect3>
<sect3 id="content-related-credits"><title>Content related credits</title><para>Credits for fixes and hints are listed here, will grow sure in the future</para><itemizedlist><listitem><para>S .P. Meenakshi &lt;meena at cs dot iitm dot ernet dot in&gt;: For a hint using a &quot;send mail&quot; shell program on tcp_wrapper/hosts.deny</para></listitem><listitem><para>Georg Käfer &lt;gkaefer at salzburg dot co dot at&gt;: For detection of no proper PDF creation (fixed now by LDP maintainer Greg Ferguson), input for German books, big list of URLs and some more suggestions and corrections.</para></listitem><listitem><para>Frank Dinies &lt;FrankDinies at web dot de&gt;: For a bugfix on IPv6 address explanation</para></listitem><listitem><para>John Freed &lt;jfreed at linux-mag dot com&gt;: For finding a bug in in IPv6 multicast address explanation</para></listitem><listitem><para>Craig Rodrigues &lt;crodrigu at bbn dot com&gt;: For suggestion about RHL IPv6 setup</para></listitem><listitem><para>Fyodor &lt;fyodor at insecure dot org&gt;: Note me about outdated nmap information</para></listitem><listitem><para>Mauro Tortonesi &lt;mauro at deepspace6 dot net&gt;: For some suggestions</para></listitem><listitem><para>Tom Goodale &lt;goodale at aei-potsdam dot mpg dot de&gt;: For some suggestions</para></listitem></itemizedlist></sect3>
<sect3 id="content-related-credits"><title>Content related credits</title><para>Credits for fixes and hints are listed here, will grow sure in the future</para><itemizedlist><listitem><para>S .P. Meenakshi &lt;meena at cs dot iitm dot ernet dot in&gt;: For a hint using a &quot;send mail&quot; shell program on tcp_wrapper/hosts.deny</para></listitem><listitem><para>Georg Käfer &lt;gkaefer at salzburg dot co dot at&gt;: For detection of no proper PDF creation (fixed now by LDP maintainer Greg Ferguson), input for German books, big list of URLs, checking all URLs and some more suggestions and corrections.</para></listitem><listitem><para>Frank Dinies &lt;FrankDinies at web dot de&gt;: For a bugfix on IPv6 address explanation</para></listitem><listitem><para>John Freed &lt;jfreed at linux-mag dot com&gt;: For finding a bug in in IPv6 multicast address explanation</para></listitem><listitem><para>Craig Rodrigues &lt;crodrigu at bbn dot com&gt;: For suggestion about RHL IPv6 setup</para></listitem><listitem><para>Fyodor &lt;fyodor at insecure dot org&gt;: Note me about outdated nmap information</para></listitem><listitem><para>Mauro Tortonesi &lt;mauro at deepspace6 dot net&gt;: For some suggestions</para></listitem><listitem><para>Tom Goodale &lt;goodale at aei-potsdam dot mpg dot de&gt;: For some suggestions</para></listitem></itemizedlist></sect3>
</sect2>
</sect1>
<sect1><title>The End</title><para>Thanks for reading. Hope it helps!</para><para>If you have any questions, subscribe to proper <link linkend="information-maillists">maillist</link> and describe your problem providing as much as information as possible.</para></sect1>