Free forever·no account, no tracking, no third-party requests ·open data, free API
showstack / protocols / dhcp

DHCP

Also called Dynamic Host Configuration Protocol.

Automatic IP address assignment. Convenient on an office network and a liability on a show network, where a device that comes back with a different address after a power cycle is a device the console can no longer find.

Network transportOpenIETFReported
Management Housekeeping, no deadline

Discovery, monitoring, configuration, backups, updates. Useful, and none of it has a deadline of its own.

What kills it. Nothing kills it. That is the problem: with no deadline it has no manners, and it will happily starve everything that does have one. Putting it on a show VLAN is the commonest self-inflicted wound in the industry.

Why this one, and not what the category suggests. Address handout. Nothing that has started working depends on it continuing.

Ports

udp/67 DHCP server
udp/68 DHCP client

What goes wrong

Two DHCP servers on one network — often a house router and somebody's travel switch — hand out conflicting addresses and are hard to find.
Show-critical devices usually want a static address or a DHCP reservation. A lighting node that moves address between the tech and the show is not a network problem you want to debug during a show.
When no server answers, most devices self-assign in 169.254.0.0/16. That looks like a working network and reaches nothing.

Typical use

Sources

Understand the mechanism
Something wrong, or missing?

Known gaps on this entry: first_published, implementations. If you can source one of them, that is a ten minute pull request.

Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.

Work at IETF? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.