bug in DHCPv6 option parse for on commit {} ?

perl-list perl-list at network1.net
Fri Dec 30 13:17:51 UTC 2016

I've been thinking about this. There are actually 4 settings in DHCPv6: 

#min-lease-time 600; 
#preferred-lifetime 600; 
default-lease-time 600; 
#max-lease-time 600; 

I presently have the other three commented out. So, it SHOULD be giving the client the 4500 second lease time that was included in the ia-na from the client. Instead, it is sending back 600. The client is setting 600 second lease as well. So there might be two bugs here or they might be related somehow. Should I submit this as a bug report? 

> From: "Simon Hobson" <dhcp1 at thehobsons.co.uk>
> To: "Users of ISC DHCP" <dhcp-users at lists.isc.org>
> Sent: Saturday, December 24, 2016 4:06:04 PM
> Subject: Re: bug in DHCPv6 option parse for on commit {} ?

> perl-list <perl-list at network1.net> wrote:

>> For example, if the client asked for a 3600 second lease but the server was
>> configured for 28800 second lease, the server would give the client the 3600
> > second lease right? At least that was how it worked in IPv4/DHCPv4.

> There are THREE options you can set (in teh DHCPv4 server at least) - MIN, MAX,
> and DEFAULT lease times.

> The default lease time is the time that's given if the client doesn't ask for
> something different.
> Min and max set the lower and upper bounds on the lease time that's given out.
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20161230/6b47820e/attachment.html>

More information about the dhcp-users mailing list