Maybe somebody (not me) will create a fork that does that. I was hoping they might dig into it and provide an option to generate new DHCP UUIDs like they do for partition UUIDs. The program is designed to create an exact backup - if you want a card for a second Pi, you will need to make whatever adjustments are required yourself, I'm afraid. This may well lead to problems if you try and run 2 Pis with identical cards on the same network, but equally it may well lead to problems if we try to modify someone's image which they are relying on being a drop-in backup of their existing card. The purpose of the SD card cloner, as the name suggests, is to completely copy the original card to create a clone for backup purposes. Now we just need to find a medieval forest of oak trees in order to rebuild the roof. An electrical fire on the platform installed for the renovation of the spire is the likely cause. The spire that went down was less than 200 years old, the original one had been destroyed during the Revolution.Īll firefighters accounted for. Nothing of great importance has perished it seems, some paintings and stained glass pieces suffered from fumes but neither from fire nor water. Re: Notre Dame, yes there was a few trinkets there. The location of these files and the generation procedure depends on the DHCP client. Don't clone DUID files or past DHCP leases files either. In short if you're cloning, don't clone /etc/machine-id, bad things could happen. So DHCP clients tend to use DUIDs, even over ipv4. There are different flavors of DUIDs and every DHCP client handles either identification options in their own way.Įven in case DHCPv6 doesn't finally meet the success it doesn't deserve, DUID has some attraction because with hardware virtualisation MACs are not as solid as they used to be. The subject of DHCP client identification is protracted because it mixes DHCP-ipv4, traditionally relying on MAC address and that curious beast that is DHCPv6 which introduced the notion of machine-specific "DHCP UID". Notre Dame: wasn't there a bunch of unique art at risk of getting destroyed or water damaged? This machine's been on that IP for months, the 222 is easy to remember. No, the MAC address didn't get cloned, the DHCP server just put the cloned machine on the same IP as the original, for some reason. Oh well, if nobody else is having a problem with it. But a DHCP server can usually read a MAC address directly. Maybe it should leave out /etc/machine-id or generate a new one, like it can generate new UUIDs.īut would that get passed to the DHCP server? Hmm, there's an /etc/dhcpd.duid which contains the MAC address, that would have gotten cloned too. I was cloning SDs a year or so ago and this never happened. Of course, there are special motions to go through in case you want to re-generate /etc/machine-id. Systemd has made the role of /etc/machine-id (a D-Bus thing) more prominent, perhaps your DHCP client uses that ID when it talks to the server. It seems unlikely that the DHCP server only uses 3 bytes to match an IP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |