<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I think they could make the implementation a little smarter than
that. Like start with a 120 second lease and double the lease time
if we're renewing AND the lease expiration time is within x seconds
of the current time. A wireless client that drops off periodically
should end up settling into an appropriately long lease time for the
amount of time he's expected to be online. Like if we're losing him
several times a day and he's renewing his lease before it's expired
then he'll end up with a lease time several hours long.<br>
<br>
<blockquote
cite="mid:11998420-B4AC-48BD-BFA7-904081AA9516@lboro.ac.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
..couldn't this be really bad for wireless...where clients drop
off and reappear due to media and mobility of clients..they can
very quickly rack up requests and suddenly have lease times of
years<br>
<br>
alan<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<br>
</body>
</html>