How can I recreate a unique identifier for DHCP in Ubuntu 18.04?
up vote
0
down vote
favorite
Following up from this question: Wrong IP address from DHCP client on Ubuntu 18.04
.
The TL;DR version of the question above is that Ubuntu has changed from identifying itself to DHCP servers with the MAC address to a unique identifier (presumably) generated when the OS is installed. The solution is to change a config file to restore the old behaviour.
I recently ran into this behaviour when working with a set of VirtualBox VMs. I was working on a project involving communications between a set of servers, so I set up a "base" server with the software I needed then cloned it multiple times. Of course, each cloned server had the same identifier, so they all received the same IP address from our DHCP server.
The answer to the question above solved the problem, but it left me wondering: How can I change the identifier assigned when Ubuntu is installed?
networking ubuntu dhcp
add a comment |
up vote
0
down vote
favorite
Following up from this question: Wrong IP address from DHCP client on Ubuntu 18.04
.
The TL;DR version of the question above is that Ubuntu has changed from identifying itself to DHCP servers with the MAC address to a unique identifier (presumably) generated when the OS is installed. The solution is to change a config file to restore the old behaviour.
I recently ran into this behaviour when working with a set of VirtualBox VMs. I was working on a project involving communications between a set of servers, so I set up a "base" server with the software I needed then cloned it multiple times. Of course, each cloned server had the same identifier, so they all received the same IP address from our DHCP server.
The answer to the question above solved the problem, but it left me wondering: How can I change the identifier assigned when Ubuntu is installed?
networking ubuntu dhcp
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Following up from this question: Wrong IP address from DHCP client on Ubuntu 18.04
.
The TL;DR version of the question above is that Ubuntu has changed from identifying itself to DHCP servers with the MAC address to a unique identifier (presumably) generated when the OS is installed. The solution is to change a config file to restore the old behaviour.
I recently ran into this behaviour when working with a set of VirtualBox VMs. I was working on a project involving communications between a set of servers, so I set up a "base" server with the software I needed then cloned it multiple times. Of course, each cloned server had the same identifier, so they all received the same IP address from our DHCP server.
The answer to the question above solved the problem, but it left me wondering: How can I change the identifier assigned when Ubuntu is installed?
networking ubuntu dhcp
Following up from this question: Wrong IP address from DHCP client on Ubuntu 18.04
.
The TL;DR version of the question above is that Ubuntu has changed from identifying itself to DHCP servers with the MAC address to a unique identifier (presumably) generated when the OS is installed. The solution is to change a config file to restore the old behaviour.
I recently ran into this behaviour when working with a set of VirtualBox VMs. I was working on a project involving communications between a set of servers, so I set up a "base" server with the software I needed then cloned it multiple times. Of course, each cloned server had the same identifier, so they all received the same IP address from our DHCP server.
The answer to the question above solved the problem, but it left me wondering: How can I change the identifier assigned when Ubuntu is installed?
networking ubuntu dhcp
networking ubuntu dhcp
asked Dec 3 at 16:52
Kryten
21114
21114
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
As I wrote in the thread you linked to, it generates the ID based on /etc/machine-id
.
The default ClientIdentifier= mode in systemd-networkd is
duid
, which means the DHCPv4 client ID is based on networkd's DHCPv6 DUID.
The default DUIDType= setting in networkd.conf is
vendor
, which is described as:
If "DUIDType=vendor", then the DUID value will be generated using "43793" as
the vendor identifier (systemd) and hashed contents of machine-id(5). This is
the default if DUIDType= is not specified.
The machine-id is also used for generating other identifiers, such as IPv6 addresses, and so should be removed/recreated even if you don't use DHCP.
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380443%2fhow-can-i-recreate-a-unique-identifier-for-dhcp-in-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As I wrote in the thread you linked to, it generates the ID based on /etc/machine-id
.
The default ClientIdentifier= mode in systemd-networkd is
duid
, which means the DHCPv4 client ID is based on networkd's DHCPv6 DUID.
The default DUIDType= setting in networkd.conf is
vendor
, which is described as:
If "DUIDType=vendor", then the DUID value will be generated using "43793" as
the vendor identifier (systemd) and hashed contents of machine-id(5). This is
the default if DUIDType= is not specified.
The machine-id is also used for generating other identifiers, such as IPv6 addresses, and so should be removed/recreated even if you don't use DHCP.
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
add a comment |
up vote
0
down vote
As I wrote in the thread you linked to, it generates the ID based on /etc/machine-id
.
The default ClientIdentifier= mode in systemd-networkd is
duid
, which means the DHCPv4 client ID is based on networkd's DHCPv6 DUID.
The default DUIDType= setting in networkd.conf is
vendor
, which is described as:
If "DUIDType=vendor", then the DUID value will be generated using "43793" as
the vendor identifier (systemd) and hashed contents of machine-id(5). This is
the default if DUIDType= is not specified.
The machine-id is also used for generating other identifiers, such as IPv6 addresses, and so should be removed/recreated even if you don't use DHCP.
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
add a comment |
up vote
0
down vote
up vote
0
down vote
As I wrote in the thread you linked to, it generates the ID based on /etc/machine-id
.
The default ClientIdentifier= mode in systemd-networkd is
duid
, which means the DHCPv4 client ID is based on networkd's DHCPv6 DUID.
The default DUIDType= setting in networkd.conf is
vendor
, which is described as:
If "DUIDType=vendor", then the DUID value will be generated using "43793" as
the vendor identifier (systemd) and hashed contents of machine-id(5). This is
the default if DUIDType= is not specified.
The machine-id is also used for generating other identifiers, such as IPv6 addresses, and so should be removed/recreated even if you don't use DHCP.
As I wrote in the thread you linked to, it generates the ID based on /etc/machine-id
.
The default ClientIdentifier= mode in systemd-networkd is
duid
, which means the DHCPv4 client ID is based on networkd's DHCPv6 DUID.
The default DUIDType= setting in networkd.conf is
vendor
, which is described as:
If "DUIDType=vendor", then the DUID value will be generated using "43793" as
the vendor identifier (systemd) and hashed contents of machine-id(5). This is
the default if DUIDType= is not specified.
The machine-id is also used for generating other identifiers, such as IPv6 addresses, and so should be removed/recreated even if you don't use DHCP.
answered Dec 3 at 16:59
grawity
230k35484544
230k35484544
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
add a comment |
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
Thanks. I didn't read far enough to find your answer; I think I need more coffee this morning.
– Kryten
Dec 3 at 17:02
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380443%2fhow-can-i-recreate-a-unique-identifier-for-dhcp-in-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown