Am 08.08.19 um 13:39 schrieb Marc Haber: > On Wed, 07 Aug 2019 09:28:12 -0400, The Wanderer > <wande...@fastmail.fm> wrote: >> On 2019-08-07 at 04:26, Russell Stuart wrote: >> >>> On Wed, 2019-08-07 at 09:34 +0200, Marc Haber wrote: >>> >>>> I am using Debian for two decades now, and I realized that >>>> necessity two days ago. >>> >>> Ditto - except for me it was a few seconds ago. >> >> In my case, it was when I read this thread last night. (After more like >> ~1.5 decades of Debian, for what that's worth.) > > Generating a new machine-id doesn't seem as easy as generating a new > ssh key: Removing /etc/machine-id doesn't do it as > systemd-machine-id-setup seems to pull the machine-id from dbus. > > I have four Banana Pis with identical machine IDs because they were > cloned from a common image. Since that one originates from a Debian > Wiki Page about the Banana Pi I guess that the vast majority of Banana > Pis running Debian has this machine id. > > How do I generate a new one?
I followed https://unix.stackexchange.com/questions/402999/it-is-ok-to-change-etc-machine-id last time which means rm -f /etc/machine-id dbus-uuidgen --ensure=/etc/machine-id rm /var/lib/dbus/machine-id dbus-uuidgen --ensure Last time I only removed /etc/machine-id (hoping it would be regenerated on Reboot) rendered the machine unbootable. FTR, I have also only recently learned about this. Duplicate machine-ids can have very nasty consequences. We recently had a weird networking issue at one department where clients got assigned the same address from the dynamic DHCP pool and kicked each other out of the network. It took us a while to figure out the admin had cloned Kubuntu 18.04 workstations that use systemd-networkd for network configuration. systemd-networkd DHCP by default sends the machine-id as client-identifier, and isc-dhcp by default uses the client-identifier (if present) instead of the MAC address to track leases. Bernhard