Monday, February 19, 2018

Is there any lower bound on DHCP lease time?

Currently I am facing an issue to change the value of the DHCP lease time option in the server and configuring the the client with the same value. I have used dhcp-server package and have put the following entry in the /etc/dhcp/dhcpd.conf file in the server for the default lease time.



default-lease-time 60;



However when I start the dhcp service at the client side, the client still takes 300 seconds as its dhcp lease time value. I have tried to make it work by deleting the /var/lib/dhcp/dhclient.leases file at the clients side and restart the DHCP server, but it did not help. It always gets 300 seconds as its dhcp lease time value.




What do you think may be the possible cause behind this? Do you think there is any lower bound on the dhcp lease time option value?
N.B. I am aware that setting a DHCP lease as low as 60 seconds does not make much sense from the perspective that a client has to refresh its lease information in at most 60 seconds and this increases the network traffic. But I was experimenting with different configuration parameters and would appreciate if someone can tell me if it is possible to set a DHCP lease time as low as 60 seconds. If not, then why?

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...