DHCP DORA narrated tour
DHCP DORA narrated tour
DHCP DORA narrated tour
Narrated audio tour. The full transcript is below.
Play the tour to open the simulator. Pause, replay a beat, or read the full transcript below.
Some beats explain situations this teaching model cannot show; those beats keep the existing frame and provide captions only.
Full transcript — DHCP DORA (8 beats)
B1 — Sensor lease
You are the technician bringing a battery sensor onto a building network. Its readings need to reach a dashboard, and getting network settings is part of that job. Before the sensor can use an assigned address, how does it obtain a lease, and how long does that lease last?
Model caption: A battery sensor needs network settings as part of reaching its dashboard. How does its lease begin and end?
B2 — Timed assignment
Dynamic Host Configuration Protocol, or DHCP, supplies network settings. It gives the sensor a lease: an address assignment with a lifetime. The conversation moves from finding a server to agreeing on an assignment. The server's final confirmation starts the timer for renewal and expiry.
Model caption: Dynamic Host Configuration Protocol supplies settings. A lease is a timed address assignment; final confirmation starts its timer.
B3 — Discover
First comes Discover. The sensor has no address yet and does not know the server, so it broadcasts its discovery message. Broadcasting lets it seek a server before it knows which server will provide its settings. Your sensor is asking for configuration.
Model caption: The unassigned sensor broadcasts because it does not yet know the server.
B4 — Competing offers
Next comes Offer. A server proposes an address, a subnet mask, and a gateway. Suppose two servers answer. The sensor chooses one offer by naming the selected server in its request. That choice tells the other server which assignment the sensor is claiming.
Model caption: An offer proposes an address, mask, and gateway. The client identifies one selected server in its request.
B5 — Request and acknowledge
The sensor broadcasts its Request for the chosen offer. The other server can reclaim its unused offer. Then the selected server sends an acknowledgement, confirming the lease. The sensor can now configure the assigned address, and the lease timer begins.
Model caption: Request selects Server A; Server B reclaims its unused offer. Acknowledgement confirms the lease and starts its timer.
B6 — Lease checkpoints
Give your sensor an eight hour lease in the model. The usual first renewal point is fifty percent of the lifetime: eight times one half gives four hours. The later fallback is eighty seven point five percent: eight times that fraction gives seven hours. Unless overridden, those are the checkpoints; the original lease expires at eight hours.
Model caption: Eight-hour model lease: 8 × 0.5 = 4 hours to normal renewal; 8 × 0.875 = 7 hours to fallback; original expiry at 8 hours, unless renewed.
B7 — Offer is a proposal
The misconception is that receiving an offer already grants a usable lease. An offer only proposes the assignment. The client still requests its choice, and the server confirms it. Receiving an offer and receiving that final acknowledgement are different stages.
Model caption: Misconception: an offer grants the lease. Offer is a proposal; Request chooses it; Acknowledge confirms it.
B8 — Renewal and expiry
At the first checkpoint, the sensor tries its original server. If renewal has failed by the later checkpoint, it tries any server. Expiry means starting the address acquisition exchange again. A lease is a timed agreement, from confirmed assignment to renewal or expiry.
Model caption: First try the original server. If renewal fails by the later checkpoint, try any server. At expiry, restart address acquisition. A lease is a timed agreement, from confirmed assignment to renewal or expiry.