svn commit: r44182 - head/en_US.ISO8859-1/books/handbook/advanced-networking
Dru Lavigne
dru at FreeBSD.org
Fri Mar 7 18:34:23 UTC 2014
Author: dru
Date: Fri Mar 7 18:34:22 2014
New Revision: 44182
URL: http://svnweb.freebsd.org/changeset/doc/44182
Log:
Clean up IPv6 Addresses section.
Update Table 30.3 with corrections from Wout Decre.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Mar 7 17:56:09 2014 (r44181)
+++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Mar 7 18:34:22 2014 (r44182)
@@ -4374,31 +4374,86 @@ Received 264951 bytes in 0.1 seconds</sc
<sect2>
<title>Background on <acronym>IPv6</acronym> Addresses</title>
- <para>There are different types of <acronym>IPv6</acronym>
- addresses: unicast, anycast, and multicast.</para>
+ <para>There are three different types of <acronym>IPv6</acronym>
+ addresses:</para>
- <para>Unicast addresses are the well known addresses. A packet
+ <variablelist>
+ <varlistentry>
+ <term>Unicast</term>
+ <listitem>
+ <para>A packet
sent to a unicast address arrives at the interface
belonging to the address.</para>
+ </listitem>
+ </varlistentry>
- <para>Anycast addresses are syntactically indistinguishable from
+ <varlistentry>
+ <term>Anycast</term>
+ <listitem>
+ <para>These addresses are syntactically indistinguishable from
unicast addresses but they address a group of interfaces. The
packet destined for an anycast address will arrive at the
- nearest (in router metric) interface. Anycast addresses may
- only be used by routers.</para>
-
- <para>Multicast addresses identify a group of interfaces. A
+ nearest router interface. Anycast addresses are
+ only used by routers.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Multicast</term>
+ <listitem>
+ <para>These addresses identify a group of interfaces. A
packet destined for a multicast address will arrive at all
- interfaces belonging to the multicast group.</para>
-
- <note>
- <para>The <acronym>IPv4</acronym> broadcast address, usually
+ interfaces belonging to the multicast group. The
+ <acronym>IPv4</acronym> broadcast address, usually
<systemitem class="ipaddress">xxx.xxx.xxx.255</systemitem>,
is expressed by multicast addresses in
<acronym>IPv6</acronym>.</para>
- </note>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>When reading an <acronym>IPv6</acronym> address, the canonical form is represented as
+ <systemitem>x:x:x:x:x:x:x:x</systemitem>, where each
+ <literal>x</literal> represents a 16 bit hex value. An example is
+ <systemitem>FEBC:A574:382B:23C1:AA49:4592:4EFE:9982</systemitem>.</para>
+
+ <para>Often, an address will have long substrings of all zeros.
+ A <literal>::</literal> (double colon) can be used to replace
+ one substring per address. Also, up to three leading
+ <literal>0</literal>s per hex value can be omitted. For example,
+ <systemitem>fe80::1</systemitem> corresponds to the
+ canonical form
+ <systemitem>fe80:0000:0000:0000:0000:0000:0000:0001</systemitem>.</para>
+
+ <para>A third form is to write the last 32 bits using the
+ well known <acronym>IPv4</acronym> notation. For example,
+ <systemitem>2002::10.0.0.1</systemitem> corresponds to the
+ hexadecimal canonical representation
+ <systemitem>2002:0000:0000:0000:0000:0000:0a00:0001</systemitem>,
+ which in turn is equivalent to
+ <systemitem>2002::a00:1</systemitem>.</para>
- <table frame="none">
+ <para>To view a &os; system's <acronym>IPv6 </acronym> address,
+ use &man.ifconfig.8;:</para>
+
+ <screen>&prompt.root; <userinput>ifconfig</userinput></screen>
+
+ <programlisting>rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
+ inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255
+ inet6 fe80::200:21ff:fe03:8e1%rl0 prefixlen 64 scopeid 0x1
+ ether 00:00:21:03:08:e1
+ media: Ethernet autoselect (100baseTX )
+ status: active</programlisting>
+
+ <para>In this example, <systemitem>fe80::200:21ff:fe03:8e1%rl0</systemitem> is an
+ auto-configured link-local address which was automatically generated from
+ the <acronym>MAC</acronym> address.</para>
+
+ <para>Some <acronym>IPv6</acronym> addresses are reserved. A
+ summary of these reserved addresses is seen in
+ <xref linkend="reservedip6"/>:</para>
+
+ <table xml:id="reservedip6" frame="none">
<title>Reserved <acronym>IPv6</acronym> Addresses</title>
<tgroup cols="4">
@@ -4449,17 +4504,24 @@ Received 264951 bytes in 0.1 seconds</sc
</row>
<row>
- <entry><systemitem>fe80::</systemitem> -
- <systemitem>feb::</systemitem></entry>
+ <entry><systemitem>fe80::/10</systemitem></entry>
<entry>10 bits</entry>
<entry>link-local</entry>
- <entry>Equivalent to the loopback address, automatic
- private addresses (169.254.1.0-169.254.254.255), or
- private IP address ranges in
+ <entry>Equivalent to the loopback address or automatic
+ private addresses (169.254.1.0-169.254.254.255) in
<acronym>IPv4</acronym>.</entry>
</row>
<row>
+ <entry><systemitem>fc00::/7</systemitem></entry>
+ <entry>7 bits</entry>
+ <entry>unique-local</entry>
+ <entry>Unique local addresses are intended for local
+ communication and are only routable within a set of
+ cooperating sites.</entry>
+ </row>
+
+ <row>
<entry><systemitem>ff00::</systemitem></entry>
<entry>8 bits</entry>
<entry>multicast</entry>
@@ -4478,85 +4540,14 @@ Received 264951 bytes in 0.1 seconds</sc
</tgroup>
</table>
- <para>When reading an <acronym>IPv6</acronym> address, the canonical form is represented as:
- <systemitem>x:x:x:x:x:x:x:x</systemitem>, with each
- <quote>x</quote> being a 16 bit hex value. For example:
- <systemitem>FEBC:A574:382B:23C1:AA49:4592:4EFE:9982</systemitem>.</para>
-
- <para>Often an address will have long substrings of all zeros.
- One such substring per address can be abbreviated by
- <quote>::</quote>. Also, up to three leading
- <quote>0</quote>s per hex quad can be omitted. For example,
- <systemitem>fe80::1</systemitem> corresponds to the
- canonical form
- <systemitem>fe80:0000:0000:0000:0000:0000:0000:0001</systemitem>.</para>
-
- <para>A third form is to write the last 32 bit part in the
- well known (decimal) <acronym>IPv4</acronym> style with dots
- (<quote>.</quote>) as separators. For example,
- <systemitem>2002::10.0.0.1</systemitem> corresponds to the
- hexadecimal canonical representation
- <systemitem>2002:0000:0000:0000:0000:0000:0a00:0001</systemitem>,
- which in turn is equivalent to
- <systemitem>2002::a00:1</systemitem>.</para>
-
- <para>Here is a sample entry from &man.ifconfig.8;:</para>
-
- <screen>&prompt.root; <userinput>ifconfig</userinput></screen>
-
- <programlisting>rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
- inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255
- inet6 fe80::200:21ff:fe03:8e1%rl0 prefixlen 64 scopeid 0x1
- ether 00:00:21:03:08:e1
- media: Ethernet autoselect (100baseTX )
- status: active</programlisting>
-
- <para><systemitem>fe80::200:21ff:fe03:8e1%rl0</systemitem> is an
- auto configured link-local address. It is generated from
- the <acronym>MAC</acronym> address as part of the auto
- configuration.</para>
-
<para>For further information on the structure of
- <acronym>IPv6</acronym> addresses, see <link
+ <acronym>IPv6</acronym> addresses, refer to <link
xlink:href="http://www.ietf.org/rfc/rfc3513.txt">RFC3513</link>.</para>
</sect2>
<sect2>
<title>Configuring <acronym>IPv6</acronym></title>
- <para>Currently, there are four ways to connect to other
- <acronym>IPv6</acronym> hosts and networks:</para>
-
- <itemizedlist>
- <listitem>
- <para>Contact an Internet Service Provider to see if they
- offer <acronym>IPv6</acronym>.</para>
- </listitem>
-
- <listitem>
- <para><link xlink:href="http://www.sixxs.net">SixXS</link>
- offers tunnels with end-points all around the
- globe.</para>
- </listitem>
-
- <listitem>
- <para><link
- xlink:href="http://www.tunnelbroker.net">Hurricane
- Electric</link> offers tunnels with end-points all
- around the globe.</para>
- </listitem>
-
- <listitem>
- <para>Tunnel via 6-to-4 as described in <link
- xlink:href="http://www.ietf.org/rfc/rfc3068.txt">RFC3068</link>.</para>
- </listitem>
-
- <listitem>
- <para>Use the <package>net/freenet6</package> port for a
- dial-up connection.</para>
- </listitem>
- </itemizedlist>
-
<para>To configure a &os; system as an
<acronym>IPv6</acronym> client, add these two lines to
<filename>rc.conf</filename>:</para>
@@ -4592,10 +4583,43 @@ rtsold_enable="YES"</programlisting>
<sect2>
<title>Connecting to a Provider</title>
+ <para>Currently, there are four ways to connect to other
+ <acronym>IPv6</acronym> hosts and networks:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Contact an Internet Service Provider to see if they
+ offer <acronym>IPv6</acronym>.</para>
+ </listitem>
+
+ <listitem>
+ <para><link xlink:href="http://www.sixxs.net">SixXS</link>
+ offers tunnels with end-points all around the
+ globe.</para>
+ </listitem>
+
+ <listitem>
+ <para><link
+ xlink:href="http://www.tunnelbroker.net">Hurricane
+ Electric</link> offers tunnels with end-points all
+ around the globe.</para>
+ </listitem>
+
+ <listitem>
+ <para>Tunnel via 6-to-4 as described in <link
+ xlink:href="http://www.ietf.org/rfc/rfc3068.txt">RFC3068</link>.</para>
+ </listitem>
+
+ <listitem>
+ <para>Use the <package>net/freenet6</package> port for a
+ dial-up connection.</para>
+ </listitem>
+ </itemizedlist>
+
<para>This section demonstrates how to take the directions
from a tunnel provider and convert it into settings that
will persist through reboots.</para>
-
+
<para>To restore the tunnel on
startup, add the following lines to
<filename>/etc/rc.conf</filename>.</para>
More information about the svn-doc-head
mailing list