The Dynamic Host Configuration Protocol (DHCP) lease process consists of four processes. The processes are
1. Discover
2. Offer
3. Request
4. Acknowledgment
In the Discover process the DHCP client initiates the process by trying to discover any DHCP servers in the network. This discover packet is a broadcast packet.
DHCP discover is a way for a client to locate a local DHCP server if one exists.
A client will request an IP address it had previously in a DHCP Discover or Request message with option 50 marked, and an IP address inserted into the data field of option 50.
The port 67 and port 68 are used by DHCP and the DHCP clients.
dhcp has to be authorized
The use of a DHCP relay agent is an agent that relays DHCP between DHCP clients and DHCP servers on different IP networks. The DHCP relay agent is compliant with RFC 1542.
router (config)# ip dhcp servicerouter (dhcp-config)# ip dhcp pool router (dhcp-config)# network
The answer is yes. The RFC 1541 states that a server "should" try unicast first, but then can use broadcast when offering. Some OS's like Microsoft skip the unicast part of this as it is not required. I would like to improve upon this answer As i see in RFC 1541, server would try to unicast DHCP offer in case it has received DHCP Discover from a DHCP relay agent otherwise it would broadcast. Would like to know if anybody differ in opinion....
(DHCP) Dynamic host Configuration Protocol. The Default Port Number is: for DHCP client : 546 for DHCP server : 547
The DHCP Server keeps all the information and data base about the DHCP Cliencts. And it works as folows. ________ ________ | | <-----D------------> Discover-------------> | | |DHCP | <-----O------------> Offer----------------> |DHCP | |SERVER | <-----R------------> Request--------------> |CLIENT | |________| <-----A------------> Acknowledgement------> |________| I want further answers regarding this. please do send me. 1. DHCP automatically Discover the systems , 2. Server Send the offer to the client systems , 3. Client send the Request to Server System, 4. last one Acknowledgement send by Server to Client I would like to make an amendment to that so that it is somewhat further understood in it's entirety. 1st: Hardware sends a broadcast asking for information regarding DHCP servers within the network (or Sub-net of course). 2nd. DHCP server responds saying "Hey, I'm here!" 3rd. Hardware sends a query for an IP address (not the same as the request phase.) 4th. DHCP server comes back with "Here ya go, you can have xxx.xxx.xxx.xxx if you want it!" 5th. Hardware decides that's what it wants, so it requests a lease for that IP address. 6th. DHCP server acknowledges the request and assigns a lease time to that piece of hardware (identified by it's MAC address). 1st through 3rd is done through MAC as the hardware has no IP address and cannot communicate through IP. To do those communications before the IP addresses are assigned they use UDP packets with Source and Destination MAC addresses as beginning and end-points. And DHCP servers don't discover the hardware added, the hardware discovers the DHCP servers. That's DORA in a nutshell.
yes DHCP require the authorization of the dhcp server before IP addresses can be allocated because until we authorize DHCP server the network does not know who is the dhcp server for the subnet. The DHCP server broadcasts the information to all.
Those are the four phases of acquiring an IP address via DHCP. More information would be needed to indicate which of the 4 phases are being used at this point.
dhcp-client
DHCP server configuration in /etc/dhcp/dhcpd.conf(FEDORA)or /etc/dhcpd.conf (RHEL).