Arch Linux

parbleu

Member

Registered: 2021-11-28

Posts: 19

IPv6 SLAAC according to RFC 7217 (and potentially RFC 4941)

As a sort of follow up to this thread: How is the IPv6 link-local unicast address generated?, I wonder what the kernel defaults are regarding RFC 7217 and RFC 4941?

I use systemd-networkd and at least the Privacy Extensions can be configured using the kernel defaults. Is this useful or is it better to explicitly force RFC 7217 and RFC 4941 in systemd-networkd with:

IPv6Token=prefixstable
IPv6PrivacyExtensions=true (*)

* Is it actually true or yes? IMO it should be true, but examples for systemd-networkd often use yes

I would like to use both since RFC 7217 handles the address for incoming connections and RFC 4941 the outgoing ones (if I'm right).

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: IPv6 SLAAC according to RFC 7217 (and potentially RFC 4941)

* Is it actually true or yes? IMO it should be true, but examples for systemd-networkd often use yes

Boolean arguments used in configuration files can be written in various formats. For positive settings the strings 1, yes, true and on are equivalent. For negative settings, the strings 0, no, false and off are equivalent.

https://man.archlinux.org/man/core/syst … yntax.7.en

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

parbleu

Member

Registered: 2021-11-28

Posts: 19

Re: IPv6 SLAAC according to RFC 7217 (and potentially RFC 4941)

Okay, I added both values to the .network file. However, ip -d link still shows

addrgenmode eui64

and it does not indicate that temporary addresses are used.