| 29 May 2023 |
 Winter (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.org | 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.org | So 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 initrd | 18:21:11 |
| @elvishjerricco:matrix.org | so without a machine-id, I bet it becomes random | 18:21:19 |
| @elvishjerricco:matrix.org | but | 18:21:21 |
| @elvishjerricco:matrix.org | My impression is that it's very odd if your hardware doesn't have a persistent MAC address | 18:21:36 |
| @elvishjerricco:matrix.org | so it should just be using that | 18:21:41 |
| Winter (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 |
| Winter (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 |
| Winter (she/her) | especially since udhcpc uses a persistent one | 18:27:19 |
| Winter (she/her) | is this worth opening an issue about, so at least it's recorded? | 18:31:22 |
| Winter (she/her) | can't think of what the issue would be configuration-wise. | 18:31:29 |
| @elvishjerricco:matrix.org | Probably | 18:31:56 |
