!PSmBFWNKoXmlQBzUQf:helsinki-systems.de

Stage 1 systemd

79 Members
systemd in NixOs's stage 1, replacing the current bash tooling https://github.com/NixOS/nixpkgs/projects/5127 Servers

Load older messages


SenderMessageTime
29 May 2023
@elvishjerricco:matrix.orgElvishJerricco btw flushBeforeStage2 is off by default with systemd initrd networking 01:45:41
@elvishjerricco:matrix.orgElvishJerricconot sure if that affects things01:45:46
@uep:matrix.org@uep:matrix.orgthen i wonder what changes to make the server allocate a different lease rather than reuse the existing01:45:55
@winterqt:nixos.devWinter (she/her)no clue!01:46:33
@winterqt:nixos.devWinter (she/her)very weird01:46:35
@winterqt:nixos.devWinter (she/her)as after flushing, i always get the same lease01:46:43
@winterqt:nixos.devWinter (she/her) * as after flushing in stage2, i always get the same lease01:46:55
@uep:matrix.org@uep:matrix.org(since I assumed it was some unconfigured, dynamic hostname)01:46:46
@uep:matrix.org@uep:matrix.orgperhaps some sniffing of requests is in order, assuming getting to the bottom of the issue is sufficiently interesting01:47:55
@winterqt:nixos.devWinter (she/her)
In reply to @uep:matrix.org
(since I assumed it was some unconfigured, dynamic hostname)
fun news: it's also a completely random MAC address??
18:06:12
@winterqt:nixos.devWinter (she/her)i don't think that's default networkd behavior...?18:07:11
@winterqt:nixos.devWinter (she/her)nope: https://github.com/systemd/systemd/blob/e30b4c13570a5e4ec794d480d5371e9c739570d9/network/99-default.link#L1718:07:46
@winterqt:nixos.devWinter (she/her) cc ElvishJerricco -- happy to debug this, but not sure how :) everything looks okay from the configuration's end. 18:08:30
@elvishjerricco:matrix.orgElvishJerricco

Winter (she/her):

MACAddressPolicy=

persistent

If the hardware has a persistent MAC address, as most hardware should, and if it is used by the kernel, nothing is done. Otherwise, a new MAC address is generated which is guaranteed to be the same on every boot for the given machine and the given device, but which is otherwise random. This feature depends on ID_NET_NAME_* properties to exist for the link. On hardware where these properties are not set, the generation of a persistent MAC address will fail.

18:20:26
@elvishjerricco:matrix.orgElvishJerriccoSo if the hardware doesn't have a persistent MAC address, then udev probably generates a MAC address based on stuff like the machine-id or something, which we don't currently add to the initrd18:21:11
@elvishjerricco:matrix.orgElvishJerriccoso without a machine-id, I bet it becomes random18:21:19
@elvishjerricco:matrix.orgElvishJerriccobut18:21:21
@elvishjerricco:matrix.orgElvishJerricco My impression is that it's very odd if your hardware doesn't have a persistent MAC address 18:21:36
@elvishjerricco:matrix.orgElvishJerricco so it should just be using that 18:21:41
@winterqt:nixos.devWinter (she/her)
In reply to @elvishjerricco:matrix.org
My impression is that it's very odd if your hardware doesn't have a persistent MAC address
it almost definitely does, yeah.
18:26:18
@winterqt:nixos.devWinter (she/her)
In reply to @elvishjerricco:matrix.org
My impression is that it's very odd if your hardware doesn't have a persistent MAC address
* it almost definitely does have one, yeah.
18:26:43
@winterqt:nixos.devWinter (she/her)especially since udhcpc uses a persistent one18:27:19
@winterqt:nixos.devWinter (she/her)is this worth opening an issue about, so at least it's recorded?18:31:22
@winterqt:nixos.devWinter (she/her)can't think of what the issue would be configuration-wise.18:31:29
@elvishjerricco:matrix.orgElvishJerriccoProbably18:31:56
@elvishjerricco:matrix.orgElvishJerriccowe should probably try to create a nixos test to reproduce the problem18:32:34
@uep:matrix.org@uep:matrix.org"and if it is used by the kernel" seems like one possible path of investigation22:26:15
31 May 2023
@copadium:matrix.orgCopa Dium joined the room.10:43:23
@copadium:matrix.orgCopa DiumI'm not sure what I'm doing wrong, but since I switched to initrd.systemd.enable I don't get a password prompt when using ZFS on luks. The service is just waiting for 1m30 and then I get an emergency shell. Is there something I have to configure manually?10:45:34
@lily:lily.flowers@lily:lily.flowers
In reply to @copadium:matrix.org
I'm not sure what I'm doing wrong, but since I switched to initrd.systemd.enable I don't get a password prompt when using ZFS on luks. The service is just waiting for 1m30 and then I get an emergency shell. Is there something I have to configure manually?
How did you configure luks? Is your config publicly available on github or anything?
10:46:46

Show newer messages


Back to Room ListRoom Version: 6