Skip to main content

DHCP Dora process

DORA in simple words is the process through which a DHCP client acquires an IP address from a DHCP server in the network

D- Discover: When a machine boots up in lan and it doesnt have an IP address configured , it would send a DHCP discover broadcast to the network. It will have a destination IP of 25.255.255.255. It also includes it mac address encapsculated in the package. The layer 2 destination would be ff:ff:ff:ff:ff:ff, ie to add devices in the network. The switch port which received the package would then forward it to all other ports in the switch except on the one from which the request is received.

O- Offer: If there is a dhcp server listening on the network, it will respond back to the DHCPrequest package with an offer package. The offer package is again a broadcast to 255.255.255.255, but it will have the destination mac address set to the DHCP client's mac address. The source mac address will be that of the DHCP server. The offer package will contain the IP address,DNS,gateway etc as well

R- Request: The dhcp client will get similar offers from all dhcp servers in the network and it will typically accept the first one that it receives.It will then send a request to the DHCP for the offered IP address.

A-Acknowledge: When DHCP received the DHCp Request from the client for the IP address, it will send back a DHCP aknowledge, thereby allocating that IP address to the client

Comments

  1. The DORA process are a part of the client message from the DHCP protocol perspective.In which only clients that are willing to request an IP address send these messages.

    Thanks
    Silvester Norman

    Change MAC Address

    ReplyDelete
    Replies
    1. You are right Silvester. Only if the client is configured to obtain IP address automatically(that is, from DHCP), this process will be initiated

      Delete
  2. Is the above information correct about the Dora process ?

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows server 2012: where is my start button??

If you have been using Windows Server OS for a while, the one thing that will strike you most when you login to a Windows server 2012 is that there is no start button!!.. What??..How am I going to manage it?? Microsoft feels that you really dont need a start button, since you can do almost everything from your server  manager or even remotely from your desktop. After all the initial configurations are done, you could also do away with the GUI and go back to server core option.(In server 2012, there is an option to add and remove GUI). So does that mean, you need to learn to live without a start button. Actually no, the start button is very much there .Lets start looking for it. Option 1: There is "charms" bar on the side of your deskop, where you will find a "start" option. You can use the "Windows +C" shortcut to pop out the charms bar Option 2: There is a hidden "start area"in  the bottom left corner of your desktop

Use Diskpart to make drives online

Issue: In disk management, disk is shown as missing or Offline in Windows Resolution: The disks can be made online by using diskpart utility - Open a command prompt->type diskpart -Inorder to list the disks in the system type: list disk -Note down the number of the disk that you want to make online -Select that disk to operate upon, For eg:, if the disk number is 1, type: Select disk 1 -Now that particular disk will be selected as teh active disk. If you type "list disk" command once more, you can see a * symbol on the left side of the selected disk -Inorder to make the selected disk online type : online disk - If the disk is made online, you will get a message that the operation is completed successfully

Kubernetes best practices in Azure: AKS name space isolation and AAD integration

Once you have decided to run your workloads in AKS service in Azure, there are certain best practices to be followed during design and implementation. In this blog we will discuss two of these recommended practices and the practical aspects of their implementation- Azure AD integration and name space isolation While AAD helps to authenticate users to your AKS cluster using the existing users and groups in your Azure AD, name space isolation provides logical isolation of resources used by them. It is useful in multi tenant scenarios where the same cluster is being used by different teams/departments to run their workloads. It is also useful in running say a dev, test and QA environment for organization in the same cluster. Combining AAD integration with name spaces allow users to login to their namespace using their Azure AD credentials AAD integration with AKS : The following Microsoft document will get you started  with AAD integration of AKS cluster.: https://docs.microsof