Proxy DHCP for networks whose DHCP server stays in charge
A VLAN in proxy mode leaves addresses to the site's DHCP server; the rack only answers PXE (dnsmasq proxy range + pxe-service), machines keep DHCP unless a static range is set aside. CLI -proxy-dhcp, web UI mode select, bootstrap --proxy-dhcp, doctor/discover aware. dnsmasq 2.91 (and 2.93) loops forever in its proxy path when the proxy range carries a set: tag: option_filter appends a request's tags to the context's persistent list, so the next request's stack interface tag points at itself (found with gdb on the lab rack). Proxy ranges are untagged and PXE services limited by interface; dhcp-boot/dhcp-match only for served subnets; no dhcp-host lines for proxied ones. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
56eae695d9
commit
7a007ef048
14 files changed
+266
-37
No files matched your search
@@ -401,6 +401,31 @@ The lab runs both: `pxe-server` (embedded, 10.213.77.0/24) and `pxe-rack2`
|
||||
pxe-rack2 and its virtual BMC on pxe-rack2. Rack ↔ region traffic is mutual
|
||||
TLS (next section), so the BMC passwords of queued commands are encrypted.
|
||||
|
||||
### DHCP already on the network: proxy DHCP
|
||||
|
||||
Where the site's DHCP server keeps handing out addresses (a corporate DHCP,
|
||||
Infoblox, a router), a VLAN can be served in **proxy** mode: the rack
|
||||
controller does not hand out addresses, it only answers PXE clients with where
|
||||
to boot from (dnsmasq proxy DHCP), and TFTP and HTTP stay on the rack.
|
||||
|
||||
```
|
||||
rollcall vlan add FABRIC VID -proxy-dhcp -rack RACK # web UI: subnet, DHCP / PXE: proxy
|
||||
deploy/bootstrap.sh --iface eth1 --proxy-dhcp # the same at install time
|
||||
```
|
||||
|
||||
- The subnet needs no ranges. Without a static range, deployed machines keep
|
||||
getting their addresses from the site's server (`dhcp` links); set a static
|
||||
range aside, outside the site's pool, to give them fixed ones.
|
||||
- No `dhcp-host` lines are written for proxy subnets, and the router and DNS
|
||||
options come from the site's server.
|
||||
- `rollcall doctor` expects the foreign DHCP server here, and fails if none answers.
|
||||
- dnsmasq (2.91, still in 2.93) loops forever in its proxy code when a proxy
|
||||
range carries a `set:` tag: Rollcall's generated configuration leaves the tag
|
||||
out and limits the PXE services by interface instead.
|
||||
|
||||
Verified in the lab with a separate DHCP server on the provisioning network:
|
||||
commissioning and three deployments in a row through the proxy.
|
||||
|
||||
## Certificate authority and TLS
|
||||
|
||||
The region is the installation's certificate authority, as the llmgw control
|
||||
|
||||
Reference in new issue
Block a user