Exponential Lease Time

Wed Aug 29 20:08:41 UTC 2012

This is a feature which we would find *very* useful.

Like many places we run a "NetReg" system where unknown hosts
start out with an address it a walled garden and once the register
they are given a "real" address.  Necessarily the pools in the
walled garden have very short lease times.  Unfortunately, these
days a great number of WiFi capable devices wander around our
campus, many of which will never register.  This means our
DHCP server sees a kajillion transactions a day.

It seems like it would be very useful to let the lease
times on these systems grow over time.

Ideally you could specify the starting point, the growth
rate (not just fixed at 2x) and the upper bound.

In our case, we might choose something like (2 min, 1.1x, 60 mins),
for example.

John

-------------------------------------------------------------------------------
John Hascall, john at iastate.edu
Team Lead, NIADS (Network Infrastructure, Authentication & Directory Services)
IT Services, The Iowa State University of Science and Technology

> --===============7794378977409939985==
> Content-Language: en-US
> Content-Type: multipart/alternative;
> 	boundary="_000_FD06A58F482E4DFE92960C5032BC1223nominumcom_"
> 
> --_000_FD06A58F482E4DFE92960C5032BC1223nominumcom_
> Content-Type: text/plain; charset="Windows-1252"
> Content-Transfer-Encoding: quoted-printable
> 
> On Aug 29, 2012, at 12:37 PM, "McDonald, Dan" <Dan.McDonald at austinenergy.co=
> m<mailto:Dan.McDonald at austinenergy.com>>
>  wrote:
> I think you still need an upper limit. Whether weeks or months, at some poi=
> nt it needs to be capped.
> 
> I would expect that the limit for a wifi hotspot would need to be quite a b=
> it lower=97it seems to me that you're saving a very small amount of DHCP tr=
> affic, at the expense of potential address starvation if too many devices g=
> et long leases before they leave.
> 
> 
> 
> --_000_FD06A58F482E4DFE92960C5032BC1223nominumcom_
> Content-Type: text/html; charset="Windows-1252"
> Content-ID: <800F3EC0147DF741A62A7A498DD8A686 at nominum.com>
> Content-Transfer-Encoding: quoted-printable
> 
> <html>
> <head>
> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
> 252">
> </head>
> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
> e-break: after-white-space; ">
> <div>
> <div>On Aug 29, 2012, at 12:37 PM, "McDonald, Dan" <<a href=3D=
> "mailto:Dan.McDonald at austinenergy.com">Dan.McDonald at austinenergy.com</a>&gt=
> ;</div>
> <div> wrote:</div>
> <blockquote type=3D"cite"><span style=3D"font-family: Helvetica; font-size:=
>  medium; font-style: normal; font-variant: normal; font-weight: normal; let=
> ter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
> uto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2=
> ; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-wi=
> dth: 0px; display: inline !important; float: none; ">I
>  think you still need an upper limit. Whether weeks or months, at some poin=
> t it needs to be capped.<span class=3D"Apple-converted-space"> </span>=
> </span><br class=3D"Apple-interchange-newline">
> </blockquote>
> <br>
> </div>
> <div>I would expect that the limit for a wifi hotspot would need to be quit=
> e a bit lower=97it seems to me that you're saving a very small amount of DH=
> CP traffic, at the expense of potential address starvation if too many devi=
> ces get long leases before they leave.</div>
> <div><br>
> </div>
> <br>
> </body>
> </html>
> 
> --_000_FD06A58F482E4DFE92960C5032BC1223nominumcom_--
> 
> --===============7794378977409939985==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
> --===============7794378977409939985==--
> 