[prev in list] [next in list] [prev in thread] [next in thread]
List: dhcp-users
Subject: Odd lease and renewal times
From: Gregory Sloop <gregs () sloop ! net>
Date: 2017-10-07 0:21:59
Message-ID: 516928346.20171006172159 () sloop ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I have a number of stations and printers that are renewing their leases at intervals \
shorter than n/2 - where N is the lease time. [In this case, 14400s]
However if I look in dhcp.leases - the lease is written as 10m.
Huh?
I'm running a fail-over pair.
mclt is 30m
default-lease-time 14400;
max-lease-time 14400;
I can't seem to grok where the 10m lease time is coming from.
Any ideas where to look?
[Oh, and yes, as far as I can tell, only some clients are so afflicted.]
Here's a excert of leases
lease 10.1.1.148 {
starts 6 2017/10/07 00:03:39;
ends 6 2017/10/07 00:13:39;
tstp 6 2017/10/07 00:18:39;
tsfp 6 2017/10/07 00:13:37;
cltt 6 2017/10/07 00:03:39;
binding state active;
next binding state expired;
hardware ethernet 00:00:00:00:00:00;
set ddns-fwd-name = "some-stupidhost.somedom.com";
set ddns-txt = "00 ... db";
set ddns-rev-name = "148.1.1.10.in-addr.arpa.";
client-hostname "abc-hp-4200";
}
[Yeah, this is an HP printer/print-server, but some Windows clients do it too.]
---
Another random case is a Windows laptop.
It DOES get a 4h lease, but then makes DHCPREQUEST's at crazy intervals.
Sometimes it's 90m, others 90s. [I can't find any consistency...]
This is a wireless device, I believe, would it make a new request if it were dropped \
and re-connected to the network?
Nothing's "broken." Everything is getting leases as they should, but I'm trying to \
understand why. Mostly looking for a good methodology and reasoning to start running \
the oddities down.
TIA
-Greg
[Attachment #5 (text/html)]
<html><head><title>Odd lease and renewal times</title>
</head>
<body>
<span style=" font-family:'Courier New'; font-size: 9pt;">I have a number of stations \
and printers that are renewing their leases at intervals shorter than n/2 - where N \
is the lease time.<br> [In this case, 14400s]<br>
<br>
However if I look in dhcp.leases - the lease is written as 10m. <br>
Huh?<br>
<br>
I'm running a fail-over pair.<br>
<br>
mclt is 30m<br>
<br>
default-lease-time 14400;<br>
max-lease-time 14400;<br>
<br>
I can't seem to grok where the 10m lease time is coming from.<br>
Any ideas where to look?<br>
<br>
[Oh, and yes, as far as I can tell, only some clients are so afflicted.]<br>
<br>
Here's a excert of leases<br>
<br>
lease 10.1.1.148 {<br>
starts 6 2017/10/07 00:03:39;<br>
ends 6 2017/10/07 00:13:39;<br>
tstp 6 2017/10/07 00:18:39;<br>
tsfp 6 2017/10/07 00:13:37;<br>
cltt 6 2017/10/07 00:03:39;<br>
binding state active;<br>
next binding state expired;<br>
hardware ethernet 00:00:00:00:00:00;<br>
set ddns-fwd-name = "some-stupidhost.somedom.com";<br>
set ddns-txt = "00 ... db";<br>
set ddns-rev-name = "148.1.1.10.in-addr.arpa.";<br>
client-hostname "abc-hp-4200";<br>
}<br>
[Yeah, this is an HP printer/print-server, but some Windows clients do it too.]<br>
<br>
---<br>
Another random case is a Windows laptop.<br>
<br>
It DOES get a 4h lease, but then makes DHCPREQUEST's at crazy intervals.<br>
Sometimes it's 90m, others 90s. [I can't find any consistency...]<br>
This is a wireless device, I believe, would it make a new request if it were dropped \
and re-connected to the network?<br> <br>
Nothing's "broken." Everything is getting leases as they should, but I'm trying to \
understand why.<br> Mostly looking for a good methodology and reasoning to start \
running the oddities down.<br> <br>
<br>
TIA<br>
-Greg<br>
</span><a style=" font-family:'arial';" \
href="mailto:gregs@sloop.net"></a></body></html>
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic