[Olsr-dev] IPv6 Unique Local Addresses

Alexander Morlang (spam-protected)
Sat Nov 29 02:02:01 CET 2008

Hash: SHA1

Alina Friedrichsen schrieb:
> Hello Alex!
>> i think, interface configuration is not the job of a routing
>> daemon,
> well, but...
>> if you want to do stateless ipv6 autoconfiguration in a mesh, you
>> can use an protocol like ahcp
>> (http://www.pps.jussieu.fr/~jch/software/ahcp/), which also gives
>> you a global routeble prefix before starting the olsr daemon (if
>> you want it).
> An external daemon don't have the topologic information, which is for
> now the best internet-gateway, so that it can take the global prefix
> from it. This is the job of the routing daemon, but I think this
> routing concept should be implemented as an external olsrd-plugin and
> not in the main olsrd, so that it naturally don't plays with your
> interface configuration.

As you can in in the specs of AHCP, is does not need any topological
information. AHCP has to spread Data like prefix, DNS server ad NTP
server, so a routing protocol can start routing.

The specific usecase you are writing about is not existing, yet to be
implemented and would work perfect in given realworl AHCP szenario.

As you might have read, the configuration process with AHCP will start
stateless and might go into stateful for getting v4 adresses leases out
of a pool, after ipv6 routing is established.

the the "prefix allocation protocol" you want to have implemented should
be done on this manner, so the ability of runtime configuration of HNA6
prefixes should suffice.

Maybe, reading the AHCP specs helps.

> Regards Alina

Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Olsr-dev mailing list