os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove all references to the now-defunct 6bone [1]

Browse source 
Replace 3ffe:* (6bone) prefixes with the prefix reserved for documentation
in RFC 3849 (while I'm here).

Prompted by:	paul beard <paulbeard@gmail.com> [1]
This commit is contained in:
Doug Barton 2007-04-26 20:27:03 +00:00
parent 113943ac4d
commit 8a313d7dcb
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30093
2 changed files with 7 additions and 66 deletions
en_US.ISO8859-1/books
developers-handbook/ipv6
chapter.sgml
handbook/advanced-networking
chapter.sgml

12
en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml
View file

@ -637,9 +637,9 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
choose the right source address. Those embedded indices will not choose the right source address. Those embedded indices will not
be on the wire). If the outgoing interface has multiple address for be on the wire). If the outgoing interface has multiple address for
the scope, a source is selected longest match basis (rule 3). Suppose the scope, a source is selected longest match basis (rule 3). Suppose
3ffe:501:808:1:200:f8ff:fe01:6317 and 3ffe:2001:9:124:200:f8ff:fe01:6317 2001:0DB8:808:1:200:f8ff:fe01:6317 and 2001:0DB8:9:124:200:f8ff:fe01:6317
are given to the outgoing interface. 3ffe:501:808:1:200:f8ff:fe01:6317 are given to the outgoing interface. 2001:0DB8:808:1:200:f8ff:fe01:6317
is chosen as the source for the destination 3ffe:501:800::1.</para> is chosen as the source for the destination 2001:0DB8:800::1.</para>
<para>Note that the above rule is not documented in the IPv6 spec. <para>Note that the above rule is not documented in the IPv6 spec.
It is considered "up to implementation" item. There are some cases It is considered "up to implementation" item. There are some cases
@ -1195,8 +1195,8 @@ FreeBSD 4.x configurable supported
TCP connection toward that prefix to IPv4 destination.</para> TCP connection toward that prefix to IPv4 destination.</para>
<para>For example, if the reserved IPv6 prefix is <para>For example, if the reserved IPv6 prefix is
3ffe:0501:0200:ffff::, and the IPv6 destination for TCP connection 2001:0DB8:0200:ffff::, and the IPv6 destination for TCP connection
is 3ffe:0501:0200:ffff::163.221.202.12, the connection will be is 2001:0DB8:0200:ffff::163.221.202.12, the connection will be
relayed toward IPv4 destination 163.221.202.12.</para> relayed toward IPv4 destination 163.221.202.12.</para>
<screen> destination IPv4 node (163.221.202.12) <screen> destination IPv4 node (163.221.202.12)
@ -1204,7 +1204,7 @@ FreeBSD 4.x configurable supported
| IPv4 tcp toward 163.221.202.12 | IPv4 tcp toward 163.221.202.12
FAITH-relay dual stack node FAITH-relay dual stack node
^ ^
| IPv6 TCP toward 3ffe:0501:0200:ffff::163.221.202.12 | IPv6 TCP toward 2001:0DB8:0200:ffff::163.221.202.12
source IPv6 node source IPv6 node
</screen> </screen>

61
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -4178,10 +4178,6 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<listitem> <listitem>
<para><ulink url="http://www.kame.net">KAME.net</ulink></para> <para><ulink url="http://www.kame.net">KAME.net</ulink></para>
</listitem> </listitem>
<listitem>
<para><ulink url="http://www.6bone.net">6bone.net</ulink></para>
</listitem>
</itemizedlist> </itemizedlist>
<sect2> <sect2>
@ -4339,10 +4335,6 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<para>Currently there are four ways to connect to other IPv6 hosts and networks:</para> <para>Currently there are four ways to connect to other IPv6 hosts and networks:</para>
<itemizedlist> <itemizedlist>
<listitem>
<para>Join the experimental 6bone</para>
</listitem>
<listitem> <listitem>
<para>Getting an IPv6 network from your upstream provider. Talk to your <para>Getting an IPv6 network from your upstream provider. Talk to your
Internet provider for instructions.</para> Internet provider for instructions.</para>
@ -4357,56 +4349,6 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<para>Use the <filename role="package">net/freenet6</filename> port if you are on a dial-up connection.</para> <para>Use the <filename role="package">net/freenet6</filename> port if you are on a dial-up connection.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>Here we will talk on how to connect to the 6bone since it currently seems
to be the most popular way.</para>
<para>First take a look at the <ulink url="http://www.6bone.net/">6bone</ulink> site and find a 6bone connection nearest to
you. Write to the responsible person and with a little bit of luck you
will be given instructions on how to set up your connection. Usually this
involves setting up a GRE (gif) tunnel.</para>
<para>Here is a typical example on setting up a &man.gif.4; tunnel:</para>
<screen>&prompt.root; <userinput>ifconfig gif0 create</userinput>
&prompt.root; <userinput>ifconfig gif0</userinput>
gif0: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1280
&prompt.root; <userinput>ifconfig gif0 tunnel <replaceable>MY_IPv4_ADDR MY_IPv4_REMOTE_TUNNEL_ENDPOINT_ADDR</replaceable></userinput>
&prompt.root; <userinput>ifconfig gif0 inet6 alias <replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR MY_IPv6_REMOTE_TUNNEL_ENDPOINT_ADDR</replaceable></userinput></screen>
<para>Replace the capitalized words by the information you received from the
upstream 6bone node.</para>
<para>This establishes the tunnel. Check if the tunnel is working by &man.ping6.8;
'ing <hostid role="ip6addr">ff02::1%gif0</hostid>. You should receive two ping replies.</para>
<note><para>In case you are intrigued by the address <hostid role="ip6addr">ff02:1%gif0</hostid>, this is a
multicast address. <literal>%gif0</literal> states that the multicast address at network
interface <devicename>gif0</devicename> is to be used. Since we <command>ping</command> a multicast address the
other endpoint of the tunnel should reply as well.</para></note>
<para>By now setting up a route to your 6bone uplink should be rather
straightforward:</para>
<screen>&prompt.root; <userinput>route add -inet6 default -interface gif0</userinput>
&prompt.root; <userinput>ping6 -n <replaceable>MY_UPLINK</replaceable></userinput></screen>
<screen>&prompt.root; <userinput>traceroute6 www.jp.FreeBSD.org</userinput>
(3ffe:505:2008:1:2a0:24ff:fe57:e561) from 3ffe:8060:100::40:2, 30 hops max, 12 byte packets
1 atnet-meta6 14.147 ms 15.499 ms 24.319 ms
2 6bone-gw2-ATNET-NT.ipv6.tilab.com 103.408 ms 95.072 ms *
3 3ffe:1831:0:ffff::4 138.645 ms 134.437 ms 144.257 ms
4 3ffe:1810:0:6:290:27ff:fe79:7677 282.975 ms 278.666 ms 292.811 ms
5 3ffe:1800:0:ff00::4 400.131 ms 396.324 ms 394.769 ms
6 3ffe:1800:0:3:290:27ff:fe14:cdee 394.712 ms 397.19 ms 394.102 ms</screen>
<para>This output will differ from machine to machine. By now you should be
able to reach the IPv6 site <ulink url="http://www.kame.net">www.kame.net</ulink>
and see the dancing tortoise &mdash; that is if you have a IPv6 enabled browser such as
<filename role="package">www/mozilla</filename>, <application>Konqueror</application>,
which is part of <filename role="package">x11/kdebase3</filename>,
or <filename role="package">www/epiphany</filename>.</para>
</sect2> </sect2>
<sect2> <sect2>
@ -4457,8 +4399,7 @@ gif0: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1280
<sect3> <sect3>
<title>IPv6 Router/Gateway Settings</title> <title>IPv6 Router/Gateway Settings</title>
<para>This will help you take the directions that your tunnel provider, <para>This will help you take the directions that your tunnel provider has
such as the <ulink url="http://www.6bone.net/">6bone</ulink>, has
given you and convert it into settings that will persist through reboots. given you and convert it into settings that will persist through reboots.
To restore your tunnel on startup use something like the following in To restore your tunnel on startup use something like the following in
<filename>/etc/rc.conf</filename>:</para> <filename>/etc/rc.conf</filename>:</para>