Skip to content
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

networkd: IPv6PrivacyExtensions=kernel doesn't honor kernel setting #18003

Closed
flokli opened this issue Dec 16, 2020 · 1 comment · Fixed by #18069
Closed

networkd: IPv6PrivacyExtensions=kernel doesn't honor kernel setting #18003

flokli opened this issue Dec 16, 2020 · 1 comment · Fixed by #18069
Labels

Comments

@flokli
Copy link
Contributor

flokli commented Dec 16, 2020

systemd version the issue has been seen with

247, 247.1

Used distribution

NixOS

Linux kernel version used (uname -a)

Linux 5.4.83

CPU architecture issue was seen on

x86_64

Expected behaviour you didn't see

networkd honors the net.ipv6.conf.$interface.use_tempaddr sysctl values set when IPv6PrivacyExtensions=kernel is set

Unexpected behaviour you saw

net.ipv6.conf.$interface.use_tempaddr is -1, no IPv6 private IP addresses are assigned, traffic goes out with the EUI-64 address

Steps to reproduce the problem

Configure your interface with IPv6PrivacyExtensions=kernel, set the net.ipv6.conf.$interface.use_tempaddr sysctl to 2`, plug it into a network with IPv6 router advertisements

Bisecting showed this seems to have been introduced by 5e0534f, which was part of #17240. More details are in NixOS/nixpkgs#106858 (comment).

flokli added a commit to flokli/nixpkgs that referenced this issue Dec 16, 2020
networkd seems to be buggy with IPv6PrivacyExtensions=kernel being set,
and the addresses don't appear anymore. In fact, the corresponding
sysctl seems to be set to -1 again.

Fixes NixOS#106858.
Upstream Issue: systemd/systemd#18003
FRidh pushed a commit to NixOS/nixpkgs that referenced this issue Dec 17, 2020
networkd seems to be buggy with IPv6PrivacyExtensions=kernel being set,
and the addresses don't appear anymore. In fact, the corresponding
sysctl seems to be set to -1 again.

Fixes #106858.
Upstream Issue: systemd/systemd#18003
flokli added a commit to flokli/systemd that referenced this issue Dec 23, 2020
When set to "kernel", systemd is not supposed to touch that sysctl.

e0534f1c13cd50ec2b143a8b18156cd37e502f7, part of
systemd#17240 forgot to handle that
case.

Fixes systemd#18003
yuwata pushed a commit to flokli/systemd that referenced this issue Dec 23, 2020
When set to "kernel", systemd is not supposed to touch that sysctl.

5e0534f, part of
systemd#17240 forgot to handle that
case.

Fixes systemd#18003
@WhoNeedszZz
Copy link

Considering this has to do with privacy why has this not been patched yet?

yuwata pushed a commit to yuwata/systemd-stable that referenced this issue Jan 20, 2021
When set to "kernel", systemd is not supposed to touch that sysctl.

5e0534f, part of
systemd/systemd#17240 forgot to handle that
case.

Fixes systemd/systemd#18003

(cherry picked from commit d3ccb1b)
keszybz pushed a commit to systemd/systemd-stable that referenced this issue Feb 2, 2021
When set to "kernel", systemd is not supposed to touch that sysctl.

5e0534f, part of
systemd/systemd#17240 forgot to handle that
case.

Fixes systemd/systemd#18003

(cherry picked from commit d3ccb1b)
flokli added a commit to flokli/nixpkgs that referenced this issue Feb 3, 2021
This reverts commit d349582.

The workaround initially applied isn't necessary anymore, as 247.3
contains the following commit:

> 242fc1d261 network: fix IPv6PrivacyExtensions=kernel handling

… which fixes systemd/systemd#18003.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

3 participants