Commit 6284877
fix: use correct dhcp option for unicast dhcp renewal
Talos attempts to do unicast DHCP renewal, if possible.
However, if the DHCP server announces a PXE server in
DHCP replies, talos erroneously send packets to this server,
instead of the actual DHCP server.
Because it falls back to broadcast, this issue did not surface.
On networks where the PXE server has a different IP than the
DHCP server (not uncommon in commercial and homelab setups),
talos continuously logged this error:
```
got an error while processing the request: no matching response packet received
```
Use Option 54 (`server-identifier`) as the unicast destination,
not `siaddr` (`ServerIPAddr`), which indicates the the PXE
`next server` field (RFC 2131 §2) and is not the correct field
to use in this context.
Signed-off-by: Fritz Schaal <fritz.schaal@siderolabs.com>
(cherry picked from commit 55b8721)1 parent dcf23be commit 6284877
File tree
1 file changed
+4
-4
lines changed- internal/app/machined/pkg/controllers/network/operator
1 file changed
+4
-4
lines changedLines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
463 | 463 | | |
464 | 464 | | |
465 | 465 | | |
466 | | - | |
467 | | - | |
| 466 | + | |
| 467 | + | |
468 | 468 | | |
469 | 469 | | |
470 | 470 | | |
471 | 471 | | |
472 | 472 | | |
473 | 473 | | |
474 | | - | |
| 474 | + | |
475 | 475 | | |
476 | 476 | | |
477 | 477 | | |
| |||
556 | 556 | | |
557 | 557 | | |
558 | 558 | | |
559 | | - | |
| 559 | + | |
560 | 560 | | |
561 | 561 | | |
562 | 562 | | |
| |||
0 commit comments