[6bone] link local for tunnel endpoints
Todd T. Fries
todd@fries.net
Fri, 7 Nov 2003 16:50:10 -0600
Penned by Jun-ichiro itojun Hagino on Sat, Nov 08, 2003 at 06:41:41AM +0900, we have:
| > On Fri, 7 Nov 2003, Todd T. Fries wrote:
| > > I use this successfully with my OpenBSD links. As pointed out to me
| > > several years back by itojun, this is quite fun to setup a v6 tunnel
| > > when the remote tunnel end is running route6d:
| > >
| > > - ifconfig gif0 tunnel <local v4 address> <remote v4 address>
| > >
| > > - ifconfig fxp0 inet6 <global v6 address>
| > >
| > > - route6d
| > >
| > > - ping6 www.kame.net ;-)
| > >
| > >
| > > route6d automatically assigns the link-local address presuming the remote
| > > route6d is advertising via the tunnel.
| >
| > No, the link local addresses are already assigned. The only thing route6d
| > does is to basically create a mapping between the default route and the
| > link local address of the next-hop router, i.e., discover the link-local
| > next-hop address.
|
| pekka's description is more correct.
Thanks Pekka and Itojun for clarifying my bad wording. Yes, Pekka is saying
the meaning I originally intended to convey...
--
Todd Fries .. todd@fries.net
Free Daemon Consulting, LLC VOIP: 1.636.410.0632
http://FreeDaemonConsulting.com Land: 1.405.810.2918
"..in support of free software solutions." Mobile: 1.405.203.6124
Key fingerprint: 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
Key: http://todd.fries.net/pgp.txt