| 2021 | |||
|---|---|---|---|
|
Jan
9 |
|
comment |
Recreating machine-id kills DHCP in Ubuntu Solved. I am a moron: the DHCP was full. |
|
Jan
9 |
|
comment |
Recreating machine-id kills DHCP in Ubuntu Here's what happens: 1) If I "echo -n > /etc/machine-id", a new (checked contents) machine-id is created on next boot, but DHCP doesn't work. 2) If I "rm /etc/machine-id" and reboot, it's not automatically recreated 2.5) If I run "systemd-machine-id-setup" manually, it does get recreated and repopulated. But DHCP still doesn't work. As soon as I roll back my VMWare snapshot back to the pristine "autoinstall just finished" state which obviously sets machine-id back to whatever the installer had decided it to be, DHCP works again. |
|
Jan
9 |
|
comment |
Recreating machine-id kills DHCP in Ubuntu I don't think I've tried systemd-machine-id-setup because the machine-id clearly is there after the reboot, so it is regenerated by something. Does the matter in which the machine-id is regenerated matter for DHCP purposes? |
|
Jan
9 |
|
awarded | Student |
|
Jan
9 |
|
asked | Recreating machine-id kills DHCP in Ubuntu |