| 10 Jun 2025 |
 Ramses 🇵🇸 | I have the stable-privacy addressing method configured for all my networks with networkd, and I recently noticed that for one particular interface, this setting is not being honoured, and the interface still uses eui64. I checked that the right values are actually set in /proc/sys/net/ipv6/conf/<iface>/addr_gen_mode so it seems that networkd is doing what it's supposed to be doing, but the kernel isn't. One characteristic of this particular interface, is that it has a bunch of tagged vlan interfaces stacked on top of it, which is kind of the only thing that makes it stand out from the other interfaces. I was just wondering if anyone has by any change already stumbled upon this behaviour and looked into it? And if others are observing the same behaviour? | 11:23:18 |
| Ramses 🇵🇸 | Ah, I am talking about the LL addresses specifically here | 11:26:12 |
 hexa | module for /etc/gai.conf https://github.com/NixOS/nixpkgs/pull/413986 | 12:29:35 |
|  weriomat joined the room. | 17:39:25 |
|  samemrecebi joined the room. | 20:20:26 |
| 11 Jun 2025 |
| samemrecebi changed their profile picture. | 10:33:41 |
|  elamon joined the room. | 15:14:20 |
|  @saiko:knifepoint.net changed their profile picture. | 16:12:16 |
| @saiko:knifepoint.net changed their display name from Katalin 🔪 to Katalin ⚧︎. | 16:13:38 |
|  @donjoe:nanashi0x74.dev changed their display name from Rian to Rian (moved to @nanashi0x74:tchncs.de). | 18:01:05 |
 wriver4 | My NixOS installation is stuck in the download buffer is full; consider increase download-buffers-size setting loop. Any advice on how to get out? | 19:11:27 |
| hexa | #nix-dev:nixos.org | 19:12:33 |
| 12 Jun 2025 |
|  zenware joined the room. | 00:53:06 |
 emily | what networkd configuration do you have on enp1s0 for this? | 14:11:59 |
| hexa | "30-enp1s0" = {
matchConfig.Name = "enp1s0";
# Allow baby jumbo frames to theoretically allow
# PPP-encapsulated packets with 1500 Bytes payload
# to pass through here.
linkConfig.MTUBytes = "1512";
address = [
"192.168.1.2/24"
];
};
| 14:13:00 |
| hexa | * "30-enp1s0" = {
matchConfig.Name = "enp1s0";
# Allow baby jumbo frames to theoretically allow
# PPP-encapsulated packets with 1500 Bytes payload
# to pass through here.
linkConfig.MTUBytes = "1512";
address = [
"192.168.1.2/24"
];
};
| 14:13:03 |
| hexa | that's the subnet I share with my modem | 14:13:22 |
| hexa | for management purposes | 14:13:39 |
| emily | aha | 14:15:02 |
| emily | yeah I think it fails to work for me because the port never comes up | 14:15:12 |
| emily | so I guess I need configuration to tell networkd "no, trust me, put it up, even without IP or anything" | 14:15:23 |
 K900 | ConfigureWithoutCarrier? | 14:15:31 |
| emily | right | 14:15:37 |
| emily | that's what I was in the process of trying, just wanted to check I hadn't missed anything | 14:15:50 |
 adamcstephens | Doesn't systemd-networkd need access to secrets? | 14:19:27 |
| emily | the current state is that pppd succeeds and networkd considers the resulting device to have a carrier:
Dec 20 12:04:39 bpi-r4 pppd[2265]: Connect: ppp-wan <--> wan
Dec 20 12:04:39 bpi-r4 systemd-timesyncd[430]: Network configuration changed, trying to establish connection.
Dec 20 12:04:39 bpi-r4 systemd-networkd[471]: ppp-wan: Configuring with /etc/systemd/network/10-ppp-wan.network.
Dec 20 12:04:39 bpi-r4 systemd-networkd[471]: ppp-wan: Link UP
Dec 20 12:04:39 bpi-r4 systemd-networkd[471]: ppp-wan: Gained carrier
but it remains in the configuring state
19 ppp-wan ppp carrier configuring
and doesn't get any address
17: ppp-wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 3
link/ppp
| 14:19:41 |
| emily | (that's after I manually networkctl up wan and with
systemd.network.networks."10-ppp-wan" = {
matchConfig.Name = "ppp-wan";
networkConfig.KeepConfiguration = true;
linkConfig.RequiredForOnline = "routable";
};
for the created interface)
| 14:20:00 |
| emily | (wait, in what context?) | 14:20:12 |
| adamcstephens | I know when working with networkd and wireguard, it's necessary to give systemd-networkd permissions to read the keys | 14:20:36 |
| emily | pppd is a separate daemon. networkd has no native support for PPPoE | 14:20:58 |
