DHCP4.0.0a1 Release notes Question

[Troy Herr]

This behavior didn't work in my environment either with 4.0.0.  I added
a kludge to server/dhcpv6.c that provides the needed functionality in my
environment.  The code change is relatively small but I lack sufficient
understanding of the backend to know whether there are any real side
effects occurring.

Essentially when a non-static lease is encountered, the server evaluates
whether the host's group and scope information is available.  When host
specific info is available that is used instead of the global values.
If host information isn't available, then a fallback to the global/lease
scope is done.


Regards,
Troy Herr

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
Behalf Of Dries Decock
Sent: Thursday, May 29, 2008 2:01 AM
To: dhcp-users at isc.org
Subject: Re: DHCP4.0.0a1 Release notes Question

Hi,

we noticed the same problem with the 4.0.0 version. I'm only able to
match a host with the host-identifier if I also give the host a fixed
address. So :

host test-box {
    host-identifier option dhcp6.client-id
00:01:00:01:47:b3:86:d0:00:07:5b:77:87:ae;
    option dhcp6.name-servers fc00:0:4491::18;
}
doesn't work, but 
host test-box {
    host-identifier option dhcp6.client-id
00:01:00:01:47:b3:86:d0:00:07:5b:77:87:ae;
    fixed-address6 fc00:0000:4491:0200::25;
    option dhcp6.name-servers fc00:0:4491::18;
}

should work.
This is causing a lot of troubles for us, but I never got a response on
this list yet.

Best regards,
Dries


On Wed, 2008-05-28 at 11:57 -0600, chinmaya sn (chins) wrote:
> Hi,
> 
> I have been trying to find solution for providing host based DHCPv6
> options.
> Using host-identifier option under host declaration block has given me
> no
> result. If you have not read my earlier mail, this my network
> configuration.
> 
> 
> preferred-lifetime 2000;
> default-lease-time 2000;
> 
> 
> subnet6 fc00:0000:4491::/64 {
>     range6 fc00:0000:4491:0200::25 fc00:0000:4491:0200::100;
> }
> 
> host test-box {
>     host-identifier option dhcp6.client-id
> 00:01:00:01:47:b3:86:d0:00:07:5b:77:87:ae;
>     option dhcp6.name-servers fc00:0:4491::18;
> }
> # the client-id is perfectly matches hex-string displayed in wireshark
> 
> 
> 
> Well while trying to debug that ... in the DHCP4.0.0a1 release notes I
> noticed that, under DHCP limitations, 
> 
> <<The "host-identifier" option is limited to a simple token>>
> 
> What does this exactly mean? Do you think it has anything to do with
> the
> problem I am facing.
>  
> Thanks
> Chinmaya
>