<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.5">
<TITLE>Re: DHCPd sending lease expiration of 3600 seconds</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>You are getting MCLT time. It is normal behavior for DHCP Failover configuration. After 50% of lease time, client will request Renew and will get configured lease time.<BR>
You will get MCLT time every time you perform release/renew or booting up your computer<BR>
<BR>
----- Original Message -----<BR>
From: dhcp-users-bounces@lists.isc.org <dhcp-users-bounces@lists.isc.org><BR>
To: dhcp-users@lists.isc.org <dhcp-users@lists.isc.org><BR>
Sent: Tue Feb 17 18:46:58 2009<BR>
Subject: DHCPd sending lease expiration of 3600 seconds<BR>
<BR>
On my CentOS 5.2 system I am setting up some network services for our<BR>
corporate environment. DHCP works great EXCEPT that clients are getting<BR>
a lease from the server that expires in 3600 second even though the<BR>
config says otherwise. Here is my config:<BR>
<BR>
#####<BR>
# server is authoritative<BR>
authoritative;<BR>
<BR>
# allow for booting over the network<BR>
#allow booting;<BR>
<BR>
# allow for booting<BR>
#allow bootp;<BR>
<BR>
# TFTP server for booting<BR>
#next-server 192.168.1.2;<BR>
<BR>
# kernel for network booting<BR>
#filename "pxelinux.0";<BR>
<BR>
# setup dynamic DNS updates<BR>
ddns-update-style interim;<BR>
ddns-updates on;<BR>
ddns-domainname "x10.com";<BR>
<BR>
# lease expiration<BR>
default-lease-time 86400;<BR>
max-lease-time 86400;<BR>
<BR>
# control client behaviour<BR>
allow unknown-clients;<BR>
ignore client-updates;<BR>
<BR>
key rndckey {<BR>
algorithm hmac-md5;<BR>
<BR>
# get from the /etc/rndc.key file<BR>
secret "R7+OZq87s/+0MiP+g2Mf0w==";<BR>
}<BR>
<BR>
# forward zone to update<BR>
zone x10.com<BR>
{<BR>
primary 127.0.0.1;<BR>
key rndckey;<BR>
}<BR>
<BR>
# reverse zone to update<BR>
zone 11.168.192.in-addr.arpa<BR>
{<BR>
primary 127.0.0.1;<BR>
key rndckey;<BR>
}<BR>
<BR>
# fail over configuration<BR>
failover peer "x10-corp" {<BR>
# This is the primary<BR>
primary;<BR>
<BR>
# primarys ip address<BR>
address 192.168.11.22;<BR>
port 647;<BR>
<BR>
# peer's ip address<BR>
peer address 192.168.11.23;<BR>
peer port 647;<BR>
<BR>
max-response-delay 60;<BR>
max-unacked-updates 10;<BR>
mclt 3600;<BR>
split 128;<BR>
load balance max seconds 3;<BR>
}<BR>
<BR>
# zone to issue addresses from<BR>
subnet 192.168.11.0 netmask 255.255.255.0<BR>
{<BR>
# pool for dhcp leases<BR>
pool {<BR>
failover peer "x10-corp";<BR>
deny dynamic bootp clients; <BR>
option routers 192.168.11.1;<BR>
option domain-name "x10.com";<BR>
option domain-name-servers 192.168.11.22,192.168.11.23;<BR>
option netbios-name-servers 192.168.11.8;<BR>
option netbios-dd-server 192.168.11.8;<BR>
option netbios-node-type 8;<BR>
option subnet-mask 255.255.255.0;<BR>
range 192.168.11.50 192.168.11.220;<BR>
<BR>
host jay-clark-xp {<BR>
hardware ethernet 00:17:31:89:03:fa;<BR>
fixed-address 192.168.11.205;<BR>
}<BR>
}<BR>
}<BR>
#####<BR>
<BR>
I can see clearly in a WireShark network trace that the server responds back with the lease marked as expiring in 1 hour. It's like the service is ignoring the default-lease and max-lease settings. Any thoughts?<BR>
<BR>
Thanks,<BR>
Geoff Sweet<BR>
<BR>
_______________________________________________<BR>
dhcp-users mailing list<BR>
dhcp-users@lists.isc.org<BR>
<A HREF="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</A><BR>
</FONT>
</P>
</BODY>
</HTML>