| 23 Mar 2026 |
 hexa | what I want is teleport with my own idp, now | 23:35:53 |
| hexa | please? 🥺 | 23:36:03 |
| 24 Mar 2026 |
|  @libjared:matrix.org left the room. | 21:26:40 |
| 26 Mar 2026 |
|  Vika (she/her) changed their profile picture. | 18:36:08 |
| 27 Mar 2026 |
|  use new account: @xengi:xengi.de changed their display name from XenGi to use new account: @xengi:xengi.de. | 11:24:44 |
| 29 Mar 2026 |
|  arcayr joined the room. | 11:15:49 |
| 31 Mar 2026 |
|  smoothie_one joined the room. | 11:48:44 |
| 1 Apr 2026 |
|  bubylou joined the room. | 00:58:41 |
| 4 Apr 2026 |
 m1cr0man | Is it possible to configure a networkd network unit using overrides in the standard module? I don't see an overrideStrategy option. | 18:56:54 |
| hexa | wdym using overrides in the standard module? | 19:43:33 |
| m1cr0man | I mean in the NixOS module - systemd.network.networks.<name> | 20:22:38 |
| m1cr0man | I want the output to be in /etc/systemd/network/<name>.d/overrides.conf | 20:22:56 |
| hexa | that exists as a concept? TIL | 20:57:12 |
| m1cr0man | The reason is that systemd ships with default network units for the nspawn container related interfaces (e.g. lib/systemd/network/80-container-vz.network for vz-* interfaces) and I want to just add some options to that instead of redefining the whole network config. | 20:27:16 |
| hexa | networkd is fully declarative, so overrides on nixos settings already work :P | 20:58:21 |
| m1cr0man | mmm actually for what I want to do, a drop-in won't even fix it as I can't change what the settings are matching against, and that's a limitation of systemd-networkd. I'll have to duplicate the configs. | 20:34:31 |
| hexa | Redacted or Malformed Event | 20:58:26 |
| m1cr0man | * mmm actually for what I want to do, a drop-in won't even fix it as I can't change the [Match] section, and that's a limitation of systemd-networkd. I'll have to duplicate the configs. | 20:34:44 |
| hexa | Redacted or Malformed Event | 20:58:32 |
| 5 Apr 2026 |
| bubylou | You can use the [Match] section in NixOS. For example a LAN config I have is setup like this.
systemd.network = {
enable = true;
networks."10-lan" = {
matchConfig.Name = "enp1s0";
| 01:17:57 |
| bubylou | * You can use the [Match] section in NixOS. For example a LAN config I have is setup like this.
systemd.network = {
networks."10-lan" = {
matchConfig.Name = "enp1s0";
| 01:18:58 |
| bubylou | * You can use the [Match] section in NixOS. For example a LAN config I have is setup like this. I could use regex instead of specifying the whole interface name such as enp*.
systemd.network = {
networks."10-lan" = {
matchConfig.Name = "enp1s0";
| 01:22:26 |
| bubylou | * You can use the [Match] section in NixOS. For example a LAN config I have is setup like this. I could use regex instead of specifying the whole interface name such as matchConfig.Name = "enp*";.
systemd.network = {
networks."10-lan" = {
matchConfig.Name = "enp1s0";
| 01:23:38 |
| bubylou | * You can use the [Match] section in NixOS. For example a LAN config I have is setup like this.
systemd.network = {
networks."10-lan" = {
matchConfig.Name = "enp*";
| 01:24:05 |
| m1cr0man | Ugh, I have spent way too long debugging why ipv6 scope IDs were not present when resolving nspawn containers from the host. It looks like nss-mymachines is broken? I would need someone else to try getent -s hosts:mymachines hosts example | 02:38:37 |
| hexa | empty | 02:44:02 |
| hexa | on the one machine I have with a nixos container | 02:44:08 |
| hexa | if that's what you were looking for | 02:44:16 |
| m1cr0man | Yep. Damn. And is that set up with a .nspawn file? | 02:46:41 |
| hexa | or maybe that's only for nspawn? | 02:46:46 |
