svn commit: r44187 - head/en_US.ISO8859-1/books/handbook/advanced-networking
Dru Lavigne
dru at FreeBSD.org
Fri Mar 7 20:23:35 UTC 2014
Author: dru
Date: Fri Mar 7 20:23:34 2014
New Revision: 44187
URL: http://svnweb.freebsd.org/changeset/doc/44187
Log:
White space fix only. Translators can ignore.
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 19:59:50 2014 (r44186)
+++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Mar 7 20:23:34 2014 (r44187)
@@ -4259,8 +4259,9 @@ Received 264951 bytes in 0.1 seconds</sc
<para><acronym>IPv6</acronym> is the new version of the well known
<acronym>IP</acronym> protocol, also known as
- <acronym>IPv4</acronym>. <acronym>IPv6</acronym> provides several advantages over
- <acronym>IPv4</acronym> as well as many new features:</para>
+ <acronym>IPv4</acronym>. <acronym>IPv6</acronym> provides
+ several advantages over <acronym>IPv4</acronym> as well as many
+ new features:</para>
<itemizedlist>
<listitem>
@@ -4274,12 +4275,12 @@ Received 264951 bytes in 0.1 seconds</sc
<listitem>
<para>Routers only store network aggregation addresses in
their routing tables, thus reducing the average space of a
- routing table to 8192 entries. This addresses the scalability
- issues associated with <acronym>IPv4</acronym>, which required every
- allocated block of <acronym>IPv4</acronym> addresses to be
- exchanged between Internet routers, causing
- their routing tables to become
- too large to allow efficient routing.</para>
+ routing table to 8192 entries. This addresses the
+ scalability issues associated with <acronym>IPv4</acronym>,
+ which required every allocated block of
+ <acronym>IPv4</acronym> addresses to be exchanged between
+ Internet routers, causing their routing tables to become too
+ large to allow efficient routing.</para>
</listitem>
</itemizedlist>
@@ -4329,52 +4330,54 @@ Received 264951 bytes in 0.1 seconds</sc
<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>A packet sent to a unicast address arrives at the
+ interface belonging to the address.</para>
+ </listitem>
+ </varlistentry>
- <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 router interface. Anycast addresses are
- only used by routers.</para>
- </listitem>
- </varlistentry>
+ <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 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. 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>
- </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. 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>
+ </listitem>
+ </varlistentry>
</variablelist>
- <para>When reading an <acronym>IPv6</acronym> address, the canonical form is represented as
+ <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
+ <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
+ <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,
+ <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>,
@@ -4393,13 +4396,14 @@ Received 264951 bytes in 0.1 seconds</sc
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>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>
+ 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>
@@ -4496,44 +4500,44 @@ Received 264951 bytes in 0.1 seconds</sc
<sect2>
<title>Configuring <acronym>IPv6</acronym></title>
- <para>To configure a &os; system as an
- <acronym>IPv6</acronym> client, add these two lines to
- <filename>rc.conf</filename>:</para>
+ <para>To configure a &os; system as an <acronym>IPv6</acronym>
+ client, add these two lines to
+ <filename>rc.conf</filename>:</para>
- <programlisting>ifconfig_<replaceable>em0</replaceable>_ipv6="inet6 accept_rtadv"
+ <programlisting>ifconfig_<replaceable>em0</replaceable>_ipv6="inet6 accept_rtadv"
rtsold_enable="YES"</programlisting>
- <para>The first line enables the specified interface to receive
- router solicitation messages. The second line enables the
- router solicitation daemon, &man.rtsol.8;.</para>
+ <para>The first line enables the specified interface to receive
+ router solicitation messages. The second line enables the
+ router solicitation daemon, &man.rtsol.8;.</para>
- <para>For &os; 8.<replaceable>x</replaceable>,
- add a third line:</para>
+ <para>For &os; 8.<replaceable>x</replaceable>, add a third
+ line:</para>
- <programlisting>ipv6_enable="YES"</programlisting>
+ <programlisting>ipv6_enable="YES"</programlisting>
- <para>If the interface needs a statically assigned <acronym>IPv6</acronym>
- address, add an entry to specify the static address and
- associated prefix length:</para>
+ <para>If the interface needs a statically assigned
+ <acronym>IPv6</acronym> address, add an entry to specify the
+ static address and associated prefix length:</para>
- <programlisting>ifconfig_<replaceable>fxp0</replaceable>_ipv6="inet6 <replaceable>2001:db8:4672:6565:2026:5043:2d42:5344</replaceable> prefixlen <replaceable>64</replaceable>"</programlisting>
+ <programlisting>ifconfig_<replaceable>fxp0</replaceable>_ipv6="inet6 <replaceable>2001:db8:4672:6565:2026:5043:2d42:5344</replaceable> prefixlen <replaceable>64</replaceable>"</programlisting>
- <para>On a &os; 8.<replaceable>x</replaceable> system,
- that line uses this format instead:</para>
+ <para>On a &os; 8.<replaceable>x</replaceable> system, that
+ line uses this format instead:</para>
- <programlisting>ipv6_ifconfig_<replaceable>fxp0</replaceable>="<replaceable>2001:db8:4672:6565:2026:5043:2d42:5344</replaceable>"</programlisting>
+ <programlisting>ipv6_ifconfig_<replaceable>fxp0</replaceable>="<replaceable>2001:db8:4672:6565:2026:5043:2d42:5344</replaceable>"</programlisting>
- <para>To assign a default router, specify its address:</para>
+ <para>To assign a default router, specify its address:</para>
- <programlisting>ipv6_defaultrouter="<replaceable>2001:db8:4672:6565::1</replaceable>"</programlisting>
- </sect2>
+ <programlisting>ipv6_defaultrouter="<replaceable>2001:db8:4672:6565::1</replaceable>"</programlisting>
+ </sect2>
- <sect2>
- <title>Connecting to a Provider</title>
+ <sect2>
+ <title>Connecting to a Provider</title>
- <para>In order to connect to other
- <acronym>IPv6</acronym> networks, one must have a
- provider or a tunnel that supports <acronym>IPv6</acronym>:</para>
+ <para>In order to connect to other <acronym>IPv6</acronym>
+ networks, one must have a provider or a tunnel that supports
+ <acronym>IPv6</acronym>:</para>
<itemizedlist>
<listitem>
@@ -4556,55 +4560,55 @@ rtsold_enable="YES"</programlisting>
</itemizedlist>
<note>
- <para>Install the <package>net/freenet6</package> package or port for a
- dial-up connection.</para>
- </note>
+ <para>Install the <package>net/freenet6</package> package or
+ port for a dial-up connection.</para>
+ </note>
- <para>This section demonstrates how to take the directions
- from a tunnel provider and convert them into
- <filename>/etc/rc.conf</filename> settings that
- will persist through reboots.</para>
+ <para>This section demonstrates how to take the directions from
+ a tunnel provider and convert them into
+ <filename>/etc/rc.conf</filename> settings that will persist
+ through reboots.</para>
- <para>The first <filename>/etc/rc.conf</filename> entry
- creates the generic tunneling interface
- <filename>gif0</filename>:</para>
+ <para>The first <filename>/etc/rc.conf</filename> entry creates
+ the generic tunneling interface
+ <filename>gif0</filename>:</para>
- <programlisting>gif_interfaces="gif<replaceable>0</replaceable>"</programlisting>
+ <programlisting>gif_interfaces="gif<replaceable>0</replaceable>"</programlisting>
- <para>Next, configure that interface with the
- <acronym>IPv4</acronym> addresses of the local and remote endpoints. Replace
- <replaceable>MY_IPv4_ADDR</replaceable> and
- <replaceable>REMOTE_IPv4_ADDR</replaceable> with the actual
- <acronym>IPv4</acronym> addresses:</para>
+ <para>Next, configure that interface with the
+ <acronym>IPv4</acronym> addresses of the local and remote
+ endpoints. Replace <replaceable>MY_IPv4_ADDR</replaceable>
+ and <replaceable>REMOTE_IPv4_ADDR</replaceable> with the
+ actual <acronym>IPv4</acronym> addresses:</para>
- <programlisting>gifconfig_gif0="<replaceable>MY_IPv4_ADDR REMOTE_IPv4_ADDR</replaceable>"</programlisting>
+ <programlisting>gifconfig_gif0="<replaceable>MY_IPv4_ADDR REMOTE_IPv4_ADDR</replaceable>"</programlisting>
- <para>To apply the <acronym>IPv6</acronym> address that has
- been assigned for use as the <acronym>IPv6</acronym> tunnel
- endpoint, add this line, replacing
- <replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable>
- with the assigned address:</para>
+ <para>To apply the <acronym>IPv6</acronym> address that has been
+ assigned for use as the <acronym>IPv6</acronym> tunnel
+ endpoint, add this line, replacing
+ <replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable>
+ with the assigned address:</para>
- <programlisting>ifconfig_gif0_ipv6="inet6 <replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable>"</programlisting>
+ <programlisting>ifconfig_gif0_ipv6="inet6 <replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable>"</programlisting>
- <para>For &os; 8.<replaceable>x</replaceable>,
- that line should instead use this format:</para>
+ <para>For &os; 8.<replaceable>x</replaceable>, that line
+ should instead use this format:</para>
- <programlisting>ipv6_ifconfig_gif0="<replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable>"</programlisting>
+ <programlisting>ipv6_ifconfig_gif0="<replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable>"</programlisting>
- <para>Then, set the default route for
- the other side of the
- <acronym>IPv6</acronym> tunnel. Replace
- <replaceable>MY_IPv6_REMOTE_TUNNEL_ENDPOINT_ADDR</replaceable>
- with the default gateway address assigned by the provider:</para>
+ <para>Then, set the default route for the other side of the
+ <acronym>IPv6</acronym> tunnel. Replace
+ <replaceable>MY_IPv6_REMOTE_TUNNEL_ENDPOINT_ADDR</replaceable>
+ with the default gateway address assigned by the
+ provider:</para>
- <programlisting>ipv6_defaultrouter="<replaceable>MY_IPv6_REMOTE_TUNNEL_ENDPOINT_ADDR</replaceable>"</programlisting>
+ <programlisting>ipv6_defaultrouter="<replaceable>MY_IPv6_REMOTE_TUNNEL_ENDPOINT_ADDR</replaceable>"</programlisting>
- <para>If the &os; system will route <acronym>IPv6</acronym>
- packets between the rest of the network and the world, enable
- the gateway using this line:</para>
+ <para>If the &os; system will route <acronym>IPv6</acronym>
+ packets between the rest of the network and the world, enable
+ the gateway using this line:</para>
- <programlisting>ipv6_gateway_enable="YES"</programlisting>
+ <programlisting>ipv6_gateway_enable="YES"</programlisting>
</sect2>
<sect2>
More information about the svn-doc-all
mailing list