-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface stuck on configuring with DHCPv6 #31349
Labels
bug 🐛
Programming errors, that need preferential fixing
dhcp
network
regression ⚠️
A bug in something that used to work correctly and broke through some recent commit
Comments
Ouch. Please try to set |
Regression caused by 195b83e. |
yuwata
added
network
regression ⚠️
A bug in something that used to work correctly and broke through some recent commit
dhcp
labels
Feb 16, 2024
(c.f. similar issue #29979, but with UseAddress=no, and it is already fixed.) |
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Feb 16, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Feb 16, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Feb 16, 2024
Fix is waiting in #31362. |
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Feb 16, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349.
yuwata
added a commit
to yuwata/systemd
that referenced
this issue
Feb 16, 2024
bluca
pushed a commit
to yuwata/systemd
that referenced
this issue
Feb 17, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349.
bluca
pushed a commit
to yuwata/systemd
that referenced
this issue
Feb 17, 2024
Amazing, thanks a lot for your quick response, @yuwata ! |
ayhamthemayhem
pushed a commit
to neighbourhoodie/nh-systemd
that referenced
this issue
Mar 25, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349.
ayhamthemayhem
pushed a commit
to neighbourhoodie/nh-systemd
that referenced
this issue
Mar 25, 2024
intelfx
pushed a commit
to intelfx/systemd
that referenced
this issue
Mar 27, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349. (cherry picked from commit b4054af)
intelfx
pushed a commit
to intelfx/systemd
that referenced
this issue
Mar 27, 2024
For issue systemd#31349. (cherry picked from commit 3b677c6)
chunyi-wu
pushed a commit
to chunyi-wu/systemd
that referenced
this issue
Apr 3, 2024
…delegation This does not change anything for DHCPv4, as a DHCPv4 address is always requested anyway. However for DHCPv6, the client may not request IA_NA addresses by UseAddress=no, or even if it is requested, the server may not provide any IA_NA addresses. Even in such cases, here the check is for delegated prefixes, hence it is not necessary to check if DHCPv6 IA_NA addresses are configured. Fixes a bug introduced by 195b83e. Fixes systemd#31349.
chunyi-wu
pushed a commit
to chunyi-wu/systemd
that referenced
this issue
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug 🐛
Programming errors, that need preferential fixing
dhcp
network
regression ⚠️
A bug in something that used to work correctly and broke through some recent commit
systemd version the issue has been seen with
255.2
Used distribution
NixOS unstable
Linux kernel version used
6.7.4
CPU architectures issue was seen on
x86_64
Component
No response
Expected behaviour you didn't see
Interface is configured like this:
It gets stuck in configuring:
Presumably because the dhcpv6 protocol didn't finish? Journalctl output below.
Unexpected behaviour you saw
No response
Steps to reproduce the problem
No response
Additional program output to the terminal or log subsystem illustrating the issue
The text was updated successfully, but these errors were encountered: