Choosing an open source DHCPv6 client

[Bjørn Mork]

Shane Kerr <shane at time-travellers.org> writes:
> On Tue, 2009-12-22 at 14:07 +0100, Bjørn Mork wrote:
>> * ISC: https://www.isc.org/software/dhcp
>> 
>>  Don't support PD (yet).  Will be interesting when it does.  But I'm not
>>  convinced the IPv4/IPv6 integration is a good idea.  It might help
>>  increase development resources though, which is definitely good.
>
> ISC DHCP 4.1 included prefix delegation:
>
> https://www.isc.org/software/dhcp/new-features
>
> This has been out for a year or so (apologies for the language which
> makes it sound like it's "coming soon").

Ah, sorry for the misinformation.  I was briefly wading through the docs
trying to figure out how to configure it for a simple PD setup when I
hit this part of dhcp-options(5):

       option dhcp6.ia-pd string;

          The ia-pd option is manufactured by clients and servers to
          create a Prefix Delegation binding - to delegate an IPv6
          prefix to the client.  There is not yet any support for prefix
          delegation in this software, and this option is provided
          informationally only.

 
I stopped reading there, I'm afraid.  Just checked the 4.1.1rc1 version
released December 8, 2009 and the 4.2.0a1 version released December 4,
2009 and they both contain the same text in
{dhcp-4.1.1rc1,dhcp-4.2.0a1}/common/dhcp-options.5 

I guess it needs an update.  The reason I ended up in dhcp-options(5) is
that I was unable to find any PD information in dhclient.conf(5).  I see
now that it is mentioned in the dhclient(8) manual.  But I'm still in
the blue wrt howto convert this very simple wide-dhcpv6 config to ISC
dhclient config: 

interface ppp0
{
  send ia-pd 0;
  script "/etc/wide-dhcpv6/dhcp6c-script";
};
id-assoc pd {
        prefix-interface eth0 {
                sla-id 0;
        };
};



Do you happen to have a PD example configuration for dhclient?


> Also, the IPv4/IPv6 integration is not an artifact of good design, but
> done because it was the simplest way to get IPv6 support in quickly.
>
> We are planning on integrating DHCP into BIND 10, which is currently in
> active development (on the DNS side at least).

I guess you see the integration advantages.  I'm afraid I don't.  There
is also a DHCP server in FreeRADIUS nowadays.  Don't really see the
point of that either.

But I guess it will make the DDNS/DHCP connection easier.

> For BIND 10 DHCP on the server side, we are planning on beginning with
> DHCPv6 and then adding DHCPv4 later. Except for the weird BOOTP-inspired
> packet format and weird things you have to do to send & receive packets
> before you have an IP address, DHCPv4 behavior is actually a simplified
> subset of DHCPv6 behavior. :) On the client side, we are looking at a
> much simpler, lower footprint client than we have today - including one
> that doesn't need to stay running all the time.

simpler, lower footprint client sounds good.

> BTW, the main thing keeping us from doing DHCP development in BIND 10
> (and in general) is lack of money. It seems very few people want to pay
> for DHCP development - if you need specific features then let me know
> and I'll see what we can do.

I'm afraid that I don't have much interest in server development.  It
seems we've already paid for that, as our BRAS vendor has implemented
something that seems to work surprisingly well :-)


Bjørn