Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
my dhcpd server is not letting go of the leases. Is this common? I have computers not even attached to the network which still have a leased dhcp address. any thoughts on this?
my max lease time is 7200 (is that in sec or mins?)
instead each client has IP address for only 2 minutes or less, and then requests for a new (or same in my case) IP address
do i need to change default-lease to a higher number
Okay, so the leases in dhcpd.leases for the computers that no longer are attached to the network has expired, but the addresses are still reserved... strange
Is it more than 7 days since you removed those computers?
You probably have to clean up your dhcpd.leases yourself, if you don't want old leases to be in there. When a lease is given it starts at a given time and date, and ends after the default lease time has expired. In your case this is 86400s ( = 24 h ). The ip-address becomes available to other hosts after the max lease time has expired, which in your case is 604800s ( = 7 days ).
So that means that your ip 192.168.1.38 is probably available again ( became available on 2002/01/06 19:24:21 + 7 days = 2002/01/13 19:24:21 ), even though the lease still excists in dhcpd.leases.
I was receiving the same message for some time--not only does it appear to be harmless, but also easy to eliminate.
The script which I was using to control the dhcp daemon contained a line which was trying to add a route to 255.255.255.255 every time the script was executed.
A temporary fix was to remove "route add -host 255.255.255.255 dev eth0" from the script. Ideally, I'd like to add to the script a test for the above route, only adding it should it not already exist.
"route -n | grep -c "255.255.255.255" works well enough from the command line, now I just have to figure out how to execute it properly from the script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.