Problem with lease time

Denis Laventure Denis_Laventure at uqac.ca
Tue Nov 3 16:58:25 UTC 2009


Just to add to my previous post,

If I do a release/renew, I get 3600 lease time. If I renew after that (without release), I get 86400 like I should... Is it a bug or it is the normal behavior? That's the first time I notice that.

Denis

De : dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] De la part de Denis Laventure
Envoyé : 2 novembre 2009 16:09
À : dhcp-users at lists.isc.org
Objet : Problem with lease time

Hi,

I have a problem today and I really don't understand why.

I'm running 4.1.0 in failover mode (also tried 4.1.1b3). My lease time in dhcpd.conf is 86400 and everytime I release/renew my ip from windows xp, I get a lease of 3600. I used tcpdump/wireshark to see what's going on and everything is fine except the lease:

    Option: (t=51,l=4) IP Address Lease Time = 1 hour
        Option: (51) IP Address Lease Time
        Length: 4
        Value: 00000E10

The only value of 3600 that I have in my config is for mclt (Max Client Lead Time) and max-balance in the failover section. If I change the mclt value to, let say, 14400, than I get a lease time of 14400. When I return it to 3600, I get 3600... Some network are ok and receive the 86400 lease time... The subnet declarations are identical.

If I create a static host entry in my config for that pc, I get the 86400 lease time. But as soon as I comment the static entry I return to 3600 lease time.

I also noticed that when the servers are restarting after a config change, sometime, if I release/renew at the same time of the server restart, I get 86400. If I renew after that I return to 3600...

I don't remember, but I don't think I had this problem last week (Friday). Something to do with daylight saving time change this weekend?

Can someone help me with this???

Dhcpd.conf:
...
default-lease-time 86400;
max-lease-time 86400;
...
#On master:
failover peer "failover-u" {
        primary;
        address 192.168.10.10;
        port 519;
        peer address 192.168.10.11;
        peer port 520;
        max-response-delay 180;
        max-unacked-updates 10;
        load balance max seconds 5;
        mclt 3600;
        split 128;
        min-balance 300;
        max-balance 3600;
}

#On secondary
failover peer "failover-u" {
        secondary;
        address 192.168.10.11;
        port 520;
        peer address 192.168.10.10;
        peer port 519;
        max-response-delay 180;
        max-unacked-updates 10;
        load balance max seconds 5;
        min-balance 300;
        max-balance 3600;
}
...
subnet 10.35.32.0 netmask 255.255.255.0 {
        option subnet-mask 255.255.255.0;
        option broadcast-address 10.35.32.255;
        option routers 10.35.32.1;
        pool {
                failover peer "failover-u";
                deny dynamic bootp clients;
                range 10.35.32.128 10.35.32.223;
                allow all clients;
        }
}


Thanks,
Denis Laventure
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20091103/41b78654/attachment.html>


More information about the dhcp-users mailing list