systemd.networkd: DHCP and link-local address
up vote
0
down vote
favorite
Is it possible to configure systemd-networkd in a way like on Windows i nterms of DHCP and link-local address?
I mean:
- if address can be obtained from DHCP, then fine - we are done.
- if getting address from DHCP fails, then backfall to 169.254.x.x.
Also similar to RFC3927.
I am bit surprised how LinkLocalAddressing= option works. It just overrides DHCP. With settings like:
[Match]
Name=eth0
KernelCommandLine=!nfsroot
[Network]
DHCP=ipv4
LinkLocalAddressing=yes
I get:
Dec 17 15:10:43 my-system systemd-networkd[1276]: eth0: IPv6 successfully enabled
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: Gained carrier
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: DHCPv4 address 10.114.138.133/24 via 10.114.138.1
Dec 17 15:10:45 my-system systemd-networkd[1276]: eth0: Gained IPv6LL
Dec 17 15:10:57 my-system systemd-networkd[1276]: eth0: Configured
root@my-system:~#
root@my-system:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:44:44:00:04:17
inet addr:169.254.184.36 Bcast:169.254.255.255
Mask:255.255.0.0
networking systemd systemd-networkd
asked yesterday
coulomb
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
Is it possible to configure systemd-networkd in a way like on Windows i nterms of DHCP and link-local address?
I mean:
- if address can be obtained from DHCP, then fine - we are done.
- if getting address from DHCP fails, then backfall to 169.254.x.x.
Also similar to RFC3927.
I am bit surprised how LinkLocalAddressing= option works. It just overrides DHCP. With settings like:
[Match]
Name=eth0
KernelCommandLine=!nfsroot
[Network]
DHCP=ipv4
LinkLocalAddressing=yes
I get:
Dec 17 15:10:43 my-system systemd-networkd[1276]: eth0: IPv6 successfully enabled
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: Gained carrier
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: DHCPv4 address 10.114.138.133/24 via 10.114.138.1
Dec 17 15:10:45 my-system systemd-networkd[1276]: eth0: Gained IPv6LL
Dec 17 15:10:57 my-system systemd-networkd[1276]: eth0: Configured
root@my-system:~#
root@my-system:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:44:44:00:04:17
inet addr:169.254.184.36 Bcast:169.254.255.255
Mask:255.255.0.0
networking systemd systemd-networkd
asked yesterday
coulomb
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is not that the default behaviour?
– Rui F Ribeiro
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is it possible to configure systemd-networkd in a way like on Windows i nterms of DHCP and link-local address?
I mean:
- if address can be obtained from DHCP, then fine - we are done.
- if getting address from DHCP fails, then backfall to 169.254.x.x.
Also similar to RFC3927.
I am bit surprised how LinkLocalAddressing= option works. It just overrides DHCP. With settings like:
[Match]
Name=eth0
KernelCommandLine=!nfsroot
[Network]
DHCP=ipv4
LinkLocalAddressing=yes
I get:
Dec 17 15:10:43 my-system systemd-networkd[1276]: eth0: IPv6 successfully enabled
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: Gained carrier
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: DHCPv4 address 10.114.138.133/24 via 10.114.138.1
Dec 17 15:10:45 my-system systemd-networkd[1276]: eth0: Gained IPv6LL
Dec 17 15:10:57 my-system systemd-networkd[1276]: eth0: Configured
root@my-system:~#
root@my-system:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:44:44:00:04:17
inet addr:169.254.184.36 Bcast:169.254.255.255
Mask:255.255.0.0
networking systemd systemd-networkd
asked yesterday
coulomb
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is it possible to configure systemd-networkd in a way like on Windows i nterms of DHCP and link-local address?
I mean:
- if address can be obtained from DHCP, then fine - we are done.
- if getting address from DHCP fails, then backfall to 169.254.x.x.
Also similar to RFC3927.
I am bit surprised how LinkLocalAddressing= option works. It just overrides DHCP. With settings like:
[Match]
Name=eth0
KernelCommandLine=!nfsroot
[Network]
DHCP=ipv4
LinkLocalAddressing=yes
I get:
Dec 17 15:10:43 my-system systemd-networkd[1276]: eth0: IPv6 successfully enabled
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: Gained carrier
Dec 17 15:10:44 my-system systemd-networkd[1276]: eth0: DHCPv4 address 10.114.138.133/24 via 10.114.138.1
Dec 17 15:10:45 my-system systemd-networkd[1276]: eth0: Gained IPv6LL
Dec 17 15:10:57 my-system systemd-networkd[1276]: eth0: Configured
root@my-system:~#
root@my-system:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:44:44:00:04:17
inet addr:169.254.184.36 Bcast:169.254.255.255
Mask:255.255.0.0
networking systemd systemd-networkd
networking systemd systemd-networkd
asked yesterday
coulomb
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
coulomb
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
coulomb
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
coulomb
62
asked yesterday
coulomb
62
62
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
coulomb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is not that the default behaviour?
– Rui F Ribeiro
yesterday
add a comment |
Is not that the default behaviour?
– Rui F Ribeiro
yesterday
Is not that the default behaviour?
– Rui F Ribeiro
yesterday
Is not that the default behaviour?
– Rui F Ribeiro
yesterday
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Try using "ip addr show" rather than ifconfig. I suspect that this will show you two IP addresses:
- the link local address; and
- the DHCP assigned IP address.
systemd-networkd is not "overriding" the DHCP assigned address with the link local address. Both addresses are active and working. It's just that ifconfig is only capable of showing a single IP address on the interface and it shows you the first address that it sees, ignoring any others.
ifconfig is already deprecated. It's time to switch to using the ip utility instead... Here's a cheat sheet that might help:
https://access.redhat.com/sites/default/files/attachments/rh_ip_command_cheatsheet_1214_jcs_print.pdf
answered yesterday
the_kid
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
coulomb is a new contributor. Be nice, and check out our Code of Conduct.
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%2funix.stackexchange.com%2fquestions%2f489520%2fsystemd-networkd-dhcp-and-link-local-address%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
Try using "ip addr show" rather than ifconfig. I suspect that this will show you two IP addresses:
- the link local address; and
- the DHCP assigned IP address.
systemd-networkd is not "overriding" the DHCP assigned address with the link local address. Both addresses are active and working. It's just that ifconfig is only capable of showing a single IP address on the interface and it shows you the first address that it sees, ignoring any others.
ifconfig is already deprecated. It's time to switch to using the ip utility instead... Here's a cheat sheet that might help:
https://access.redhat.com/sites/default/files/attachments/rh_ip_command_cheatsheet_1214_jcs_print.pdf
answered yesterday
the_kid
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
Try using "ip addr show" rather than ifconfig. I suspect that this will show you two IP addresses:
- the link local address; and
- the DHCP assigned IP address.
systemd-networkd is not "overriding" the DHCP assigned address with the link local address. Both addresses are active and working. It's just that ifconfig is only capable of showing a single IP address on the interface and it shows you the first address that it sees, ignoring any others.
ifconfig is already deprecated. It's time to switch to using the ip utility instead... Here's a cheat sheet that might help:
https://access.redhat.com/sites/default/files/attachments/rh_ip_command_cheatsheet_1214_jcs_print.pdf
answered yesterday
the_kid
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
Try using "ip addr show" rather than ifconfig. I suspect that this will show you two IP addresses:
- the link local address; and
- the DHCP assigned IP address.
systemd-networkd is not "overriding" the DHCP assigned address with the link local address. Both addresses are active and working. It's just that ifconfig is only capable of showing a single IP address on the interface and it shows you the first address that it sees, ignoring any others.
ifconfig is already deprecated. It's time to switch to using the ip utility instead... Here's a cheat sheet that might help:
https://access.redhat.com/sites/default/files/attachments/rh_ip_command_cheatsheet_1214_jcs_print.pdf
answered yesterday
the_kid
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Try using "ip addr show" rather than ifconfig. I suspect that this will show you two IP addresses:
- the link local address; and
- the DHCP assigned IP address.
systemd-networkd is not "overriding" the DHCP assigned address with the link local address. Both addresses are active and working. It's just that ifconfig is only capable of showing a single IP address on the interface and it shows you the first address that it sees, ignoring any others.
ifconfig is already deprecated. It's time to switch to using the ip utility instead... Here's a cheat sheet that might help:
https://access.redhat.com/sites/default/files/attachments/rh_ip_command_cheatsheet_1214_jcs_print.pdf
answered yesterday
the_kid
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
the_kid
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
the_kid
1
answered yesterday
the_kid
1
1
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
the_kid is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
coulomb is a new contributor. Be nice, and check out our Code of Conduct.
coulomb is a new contributor. Be nice, and check out our Code of Conduct.
coulomb is a new contributor. Be nice, and check out our Code of Conduct.
coulomb is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f489520%2fsystemd-networkd-dhcp-and-link-local-address%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
Is not that the default behaviour?
– Rui F Ribeiro
yesterday