Set up DHCP
Let kudurru assign IPv4 addresses, keep reservations and serve names for leased devices. Choose the walkthrough that matches your deployment.
| Deployment | Start here |
|---|---|
| Kubernetes store | Kubernetes DHCP walkthrough: LoadBalancer, router relay, required trusted relays and client tests |
| Linux with SQLite | Follow the 7 steps below for clients on the node's local network |
Kubernetes requires at least 1 trusted relay per scope. The router forwards client broadcasts to the DHCP LoadBalancer. Scope changes apply live.
Linux with SQLite
Before you start
- You need the
adminrole and access to the Linux host. - You need access to your current DHCP server or router.
- You need one test client on the same network.
| Step | What you do |
|---|---|
| 1. Prepare your network | Choose addresses and provide host networking and privileges |
| 2. Describe the subnet | Select an interface, server address and subnet |
| 3. Set the address pool | Set the pool, router and DNS server |
| 4. Set lease DNS | Choose a local domain and name registration |
| 5. Review and save | Check all values and save the scope |
| 6. Activate and check | Stop the old service, restart the node and test a lease |
| 7. Reserve an address | Keep a device at a known address |
A scope describes one subnet and its address pool. Saving a scope does not start DHCP on a SQLite node. Activation needs a node restart.
For a Kubernetes deployment, follow the Kubernetes walkthrough. For several Linux nodes, see Automatic failover.
DHCPv6 is not supported. Keep IPv6 router and DNS advertisements on your router. The screenshots show demo data; use your own network values.