[Dibbler-devel] Prefix Delegation

Tomasz Mrugalski thomson at klub.com.pl
Tue Jan 9 20:28:09 CET 2007


On Tue, 9 Jan 2007 somebody known as Arne Bernin wrote:

> Hi!
>
> I just read the news on the dibbler hp regarding prefix delegation. As i
> understand it, it is now possible to provide multiple prefixes to a
> client and this client will use this prefixes to generate corresponding
> radvd.conf files. Is there Any mechanism planned or implemented to
Yes, client will generate radvd.conf file and will also configure received 
prefix on the interfaces, which it has received the prefix on.
(that is not the most useful the client can do with a prefix, but it was 
the best from the testing point of view). Also this will be default 
behavior when client's node has IPv6 forwarding disabled.

Anyway, within two weeks client will be able to split received prefix and 
configure subprefixes on its interfaces and generate radvd.conf file. Take 
a look at User's Guide, section 3.6 and especially figure 9. It is 
described there in detail how this will work.

> configure a (local) dibbler server with the information from the prefix
> delegation (If i get a /48 prefix via dhcpv6 by a provider and want to
> use this to generate local /64 prefixes on multiple interfaces
> (eth,wlan) for clients to use ?
Yes. It will work like this. Clients on your local links will get those
prefixes configured via RADVD.

> Is it possible to call a script whenever the client gets a new prefix
> from upstream ?
No, not yet. But such feature will be implemented soon. I think that by 
default this script should restart radvd if it is already running.

Do you have any suggestions related to this behavior?

By the way: I'm going on a business trip. I'll be back on Jan. 15th, so 
dibbler will be on hold for a few days.

-- 
Tomasz Mrugalski,              | "I think there is a world market for     |
thomson(at)klub(dot)com(dot)pl |  about five computers."                  |
                                |     Thomas J. Watson (Chairman, IBM) 1943|


More information about the Dibbler-devel mailing list