[6bone] link local for tunnel endpoints
Pekka Savola
pekkas@netcore.fi
Fri, 7 Nov 2003 21:31:08 +0200 (EET)
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.
Rather silly use of route6d, if you ask me. Just ask the ISP to configure
fe80::1 as the address, or find the address of the neighbor otherwise
(e.g., it can be calculated for v6-over-v4 tunnels by yourself).
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings