[Top] [All Lists]

[PATCH] IPv6: (5/5+1) Autoconfig link-local addr to IPv6 tunnels

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: [PATCH] IPv6: (5/5+1) Autoconfig link-local addr to IPv6 tunnels
From: Ville Nuorvala <vnuorval@xxxxxxxxxx>
Date: Mon, 1 Sep 2003 17:24:42 +0300 (EEST)
Cc: Pekka Savola <pekkas@xxxxxxxxxx>, <yoshfuji@xxxxxxxxxxxxxx>, <usagi-core@xxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>
In-reply-to: <20030901035134.2585aa79.davem@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 1 Sep 2003, David S. Miller wrote:

> On Mon, 1 Sep 2003 13:48:44 +0300 (EEST)
> Pekka Savola <pekkas@xxxxxxxxxx> wrote:
> > Well, link-local addresses are used e.g. by routing protocols and such, so
> > having one is probably rather important..
> Ok.
> > FWIW, on FreeBSD platform they take the link-local address of the first
> > physical interface, and give the exact same link-local address on all of
> > the tunnels, disambiuating them with the scope identifier.  Seems like an
> > OK appaorach too, and guarantees (to the degree of unique MAC addresses)
> > that the addresses of the endpoints do not clash.
> Interesting approach...  I'm not particularly picky about how this
> uniqueness issue is solved.

Ok, this incremental patch to my previous addrconf.c patch generates a
link-local address to the IPv6 tunnel device. It first tries to inherit
the EUI64 identifier of some other device and if this fails, uses a
random interface id.

Ville Nuorvala
Research Assistant, Institute of Digital Communications,
Helsinki University of Technology
email: vnuorval@xxxxxxxxxx, phone: +358 (0)9 451 5257

Attachment: ip6_tnl_autoconf.patch
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>