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

fix minor typos in Linux+IPv6-HOWTO.sgml

This commit is contained in:
Jason Leschnik 2016-10-24 20:38:35 +11:00
parent a844d8059d
commit 17a7dbdcf6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -318,7 +318,7 @@ There are some further subtypes defined, see below:</para><sect3>
<![CDATA[3ffe:ffff:100:f102::1
]]></screen><para>A special 6bone test address which will never be globally unique begins with </para><screen>
<![CDATA[3ffe:ffff:
]]></screen><para>and is mostly shown in older examples. The reason for this is, if real addresses are are shown, it's possible for someone to do a copy &amp; paste to their configuration files, thus inadvertently causing duplicates on a globally unique address. This would cause serious problems for the original host (e.g. getting answer packets for request that were never sent).
]]></screen><para>and is mostly shown in older examples. The reason for this is, if real addresses are shown, it's possible for someone to do a copy &amp; paste to their configuration files, thus inadvertently causing duplicates on a globally unique address. This would cause serious problems for the original host (e.g. getting answer packets for request that were never sent).
Because IPv6 is now in production, this prefix is no longer be delegated and is removed from routing after 6.6.2006 (see <ulink url="http://www.faqs.org/rfcs/rfc3701.html">RFC 3701 / 6bone Phaseout</ulink> for more).</para></sect3><sect3>
<title>6to4 addresses</title>
<para>These addresses, designed for a special tunneling mechanism [<ulink url="http://www.faqs.org/rfcs/rfc3056.html">RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds</ulink> and <ulink url="http://www.faqs.org/rfcs/rfc2893.html">RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers</ulink>], encode a given IPv4 address and a possible subnet and begin with </para><screen>
@ -677,7 +677,7 @@ user@::1's password: ******
# /sbin/ifconfig eth0 down
]]></screen></sect2></sect1></chapter><chapter id='chapter-configuration-address' >
<title><!-- anchor id="chapter-configuration-address" -->Configuring IPv6 addresses</title>
<para>There are different ways to configure an IPv6 address on an interface. You can use use "ifconfig" or "ip".</para><sect1>
<para>There are different ways to configure an IPv6 address on an interface. You may use "ifconfig" or "ip".</para><sect1>
<title>Displaying existing IPv6 addresses</title>
<para>First you should check, whether and which IPv6 addresses are already configured (perhaps auto-magically during stateless auto-configuration).</para>
<para>Just note that addresses beginning with &ldquo;fec0&rdquo; are deprecated, but shown here for completness!</para><sect2>
@ -1091,7 +1091,7 @@ ff00::/8 :: UA 256 0 0 sit0
<title>Numbered point-to-point tunnels</title>
<para>Sometimes it's needed to configure a point-to-point tunnel with IPv6 addresses like in IPv4 today. This is only possible with the first (ifconfig+route - deprecated) and third (ip+route) tunnel setup. In such cases, you can add the IPv6 address to the tunnel interface like shown on interface configuration. </para></sect2></sect1><sect1 id='configuring-ipv6to4-tunnels' >
<title><!-- anchor id="configuring-ipv6to4-tunnels" -->Setup of 6to4 tunnels</title>
<para>Pay attention that the support of 6to4 tunnels currently lacks on vanilla kernel series 2.2.x (see <link linkend="systemcheck-kernel">systemcheck/kernel</link> for more information). Also note that that the prefix length for a 6to4 address is 16 because of from network point of view, all other 6to4 enabled hosts are on the same layer 2.</para><sect2>
<para>Pay attention that the support of 6to4 tunnels currently lacks on vanilla kernel series 2.2.x (see <link linkend="systemcheck-kernel">systemcheck/kernel</link> for more information). Also note that the prefix length for a 6to4 address is 16 because of from network point of view, all other 6to4 enabled hosts are on the same layer 2.</para><sect2>
<title>Add a 6to4 tunnel</title>
<para>First, you have to calculate your 6to4 prefix using your local assigned global routable IPv4 address (if your host has no global routable IPv4 address, in special cases NAT on border gateways is possible):</para>
<para>Assuming your IPv4 address is </para><screen>
@ -2546,7 +2546,7 @@ Big pipe Queue 2 Queue 1 / Queue 2 / Queue 3 Thin Pipe
<![CDATA[# ip6tables -A POSTROUTING -t mangle -p tcp --dport 5003 -j MARK --set-mark 32
]]></screen></sect3><sect3>
<title>Testing filter definitions using iperf</title>
<para>Start on server side each one one separate console:</para><screen>
<para>Start on server side each one in a separate console:</para><screen>
<![CDATA[# iperf -V -s -p 5001
# iperf -V -s -p 5002
# iperf -V -s -p 5003