Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
But i can tell dhcp server to assign a static address right for a client ? likewise what i need is when an ip from the pool is allocated to a client and say i have set the max-lease-time 600; After 5 mins it should allocate a random IP from the pool instead it is allocating same IP to the client every time. Can't i override this option ?
no, it's not part of the DHCP RFC. A client should request to continue a lease half way through the lifetime of the lease, or more frequently. There is no reason for DHCP to explicitly change IP. You *could* in theory change the config to change an explicit reservation in the config, but this is nothing inherently to do with DHCP as a standard.
Whilst I can imagine lots of scenarios where it'd be "nice" to have this feature, it's not part of DHCP, and shouldn't be.
I don't know whether it is right or wrong. But, that mentions: A Dynamic allocation where a client will always have a random IP. Also in the below link (it might be specific to his own DHCP also am not sure)
-- The DHCP server always assigns the address previously assigned to the client unless the address is unavailable. This caught my attention. In RFC it says,
"The server may choose the least recently assigned address" is this possible with RHEL 6 DHCP server or any 3rd party DHCP servers ?
All i want is DHCP server should assign a random IP (except the one assinged immediate past) to the client from the pool instead of allocating same IP every time for the client
the server will choose the least recently assigned when ALL otehr eligible IP addresses are used. If there is an expired lease, then as much as it *could* be reallocated, logic says you might as well pick a new IP for a new client, incase that other expired client comes back again in the future. When there are no IP's left, logic then says that the lease that expired longest ago is probably fair game. So I really don't think that's the opportunity you think it is.