[Dibbler] Assigning fixed addresses

[David Antos]

Hello,

On Wed, Nov 28, 2007 at 12:16:11AM +0100, Tomasz Mrugalski wrote:
> Can you send your server.conf file? You didn't provide much information, 
> but maybe you have put the "freely assigned" pool BEFORE the reserved 
> pools?

I believe that order doesn't matter at all. Attached you find the config. I
also tried inserting "reject-clients" constructs---containing all the DUIDs
for fixed machines---to the pool, but the fixed machines get pool addresses
anyway.

There may also be a more simple way to configure what I want. What I
understand from the documentation, the classes are selected in a random
manner (only accept and reject statements are checked).

> > P.S.: It would also be nice to allow more pools in classes.
> Yes, I know. But I don't have time to code it. :(

That's always a problem ;). To be honest, we patched wide-dhcpv6 (in an
ugly way) to support multiple pools and we run it with Dibbler clients
(which is the only that supports link-layer DUIDs). I've been pleased that
the implementations interoperate well.

> Sorry for replying with such delay - I was on vacation.

No problem, hope you enjoyed it ;)

Regards,
D.A.

-- 
This is experimental code. Don't change it, don't rely on                    
this interface remaining the same, don't use tricks used                     
here but not described in manuals, so: assume that this                      
file does not exists.
-- Hans Hagen (Pragma ADE)
-------------- next part --------------
iface "eth0" {
  class { # trurl
    accept-only 0x00030001000423c39123
    pool 2001:0718:0801:0031:0000:0000:0000:0012/128
  }

  class { # klapacius
    accept-only 0x00030001000423c3907d
    pool 2001:0718:0801:0031:0000:0000:0000:0013/128
  }

  ########## Rest of the POOL #########
  class {
    # w54-<n>.ip6.fi.muni.cz segment
    pool 2001:0718:0801:0031:0000:0000:0000:0120
    pool 2001:0718:0801:0031:0000:0000:0000:0121
  }
}