[Dibbler] Static DHCPv6 address support

[Burden, Ken]

Hi,

Thanks.  I have tested 3 different DHCPv6 servers - each has its own way
of telling the server how to do what you want.  The docs are not always
clear about what needs to be done.

So, if I want the server to handle requests on the local subnet/link,
which eth0 is connected to, and I want to relay requests in from other
subnets/links via my Cisco router this will work?

Or should I change the iface eth0 section to have a real pool?

Basically I want to be able to accept DHCPv6 requests from the local
link (eth0 is connected to) and other remote links (forwarded by the
Cisco router) and offer both static reserved IPv6 addresses and
simultaneously offer addresses from a pool groups if there is no match
for a static reserved entry.

Regards,

Ken Burden

-----Original Message-----
From: dibbler-bounces at klub.com.pl [mailto:dibbler-bounces at klub.com.pl]
On Behalf Of Tomasz Mrugalski
Sent: Tuesday, May 09, 2006 4:46 PM
To: Dibbler users list
Subject: Re: [Dibbler] Static DHCPv6 address support

On Tue, 9 May 2006 somebody known as Burden, Ken wrote:

> Hi,
>
> Thanks for the reply.  I had thought of this but wasn't sure if there
> was another option.
>
> Next question - I am using a Cisco router to relay the DHCP messages
> from another subnet/link to the Dibbler server.  I am seeing errors in
> the log file and would appreciate help figuring out what I am missing
in
> the config file.
>
> Here is my config file.
Take a look at server-relay.conf example config file. If you are going
to 
use more than one relay, please take a look 2relays-*.conf files.

Your config file should (more or less) look like this:
-------------------
log-level 7
log-mode short

iface eth0 {
  # dummy class (an ugly workaround)
  class { pool ::-:: }

}

iface relay1 {
   relay eth0
   interface-id 27
# clients should renew every half an hour
   T1 1800
   T2 2000
   prefered-lifetime 3600
   valid-lifetime 7200
   unicast 2001:1890:1109:4:230:6eff:fef2:dc19
   class {
      accept-only 0x0001000100d257440014220f5116
      pool 2001:1890:1109:2::40
   }

   option dns-server 2001:1890:1109::10
   option domain vcd.ipv6.hp.com

}
----------------------
Let me explain, how this works. You have physical interface eth0, which 
has logical interface relay1 defined on it. (This logical interface is 
dibbler specific and is not seen in the system). This means that packets

from the link designated as interface-id=27 can only be received via
eth0 
interface.

Also a word of explanation about dummy class defined on the eth0 
directly. This is a unfortunate feature of the dibbler parser. It won't 
allow to define empty (without any addresses) interface. I have submited
a bug for this: http://klub.com.pl/cgi-bin/bugzilla/show_bug.cgi?id=123

> Also, what is the correct syntax for a DUID for the accept-only
> statement?
Ahhh, the docs seem not to be updated. The proper format is as follows:

      accept-only 0x0001000100d257440014220f5116

Best regards,

-- 
Tomasz Mrugalski,              | " Talk is cheap. Show me the code."  |
thomson(at)klub(dot)com(dot)pl |                     Linus Torvalds   |

_______________________________________________
Dibbler mailing list
Dibbler at klub.com.pl
http://klub.com.pl/cgi-bin/mailman/listinfo/dibbler