<html><body><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><div>I'll go ahead and report this as a bug.</div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><br><br><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Darren Ankney" <perl-list@network1.net><br><b>To: </b>"Users of ISC DHCP" <dhcp-users@lists.isc.org><br><b>Sent: </b>Friday, December 30, 2016 8:17:51 AM<br><b>Subject: </b>Re: bug in DHCPv6 option parse for on commit {} ?<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><div>I've been thinking about this. There are actually 4 settings in DHCPv6:</div><br><div><div>#min-lease-time 600;</div><div>#preferred-lifetime 600;</div><div>default-lease-time 600;</div><div>#max-lease-time 600;</div></div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000"><br></div><div style="font-family: Andale Mono; font-size: 10pt; color: #000000">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?<br><br><hr id="zwchr"><div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Simon Hobson" <dhcp1@thehobsons.co.uk><br><b>To: </b>"Users of ISC DHCP" <dhcp-users@lists.isc.org><br><b>Sent: </b>Saturday, December 24, 2016 4:06:04 PM<br><b>Subject: </b>Re: bug in DHCPv6 option parse for on commit {} ?<br></blockquote></div><div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">perl-list <perl-list@network1.net> wrote:<br><br>> 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.<br><br>There are THREE options you can set (in teh DHCPv4 server at least) - MIN, MAX, and DEFAULT lease times.<br><br>The default lease time is the time that's given if the client doesn't ask for something different.<br>Min and max set the lower and upper bounds on the lease time that's given out.<br>_______________________________________________<br>dhcp-users mailing list<br>dhcp-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/dhcp-users</blockquote></div></div><br></div><br>_______________________________________________<br>dhcp-users mailing list<br>dhcp-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/dhcp-users</blockquote></div></div><div><br></div></div></body></html>