Re: system is not match systemd.link configs

[Andrei Borzenkov <arvidjaar@xxxxxxxxx>]

On Mon, Oct 28, 2024 at 3:07 PM Henti Smith <henti@xxxxxxxxxxxxxxxxx> wrote:
>
> On Mon, 28 Oct 2024 at 10:38, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote:
>>
>> On Thu, Oct 24, 2024 at 6:29 PM Henti Smith <henti@xxxxxxxxxxxxxxxxx> wrote:
>> >
>> > Good day everybody
>> >
>> > I have two link files for mvc-sw1 and mvc-sw2.
>> >
>> > # mvc-sw1
>> > ```
>> > # Fixed MAC and name for eno2 (Switch 1 connection) when debug board is plugged in
>> > # Renamed to mvc-sw1 by PCI Address and set custom MAC address.
>> > [Match]
>> > Property=DEVPATH=/devices/pci0000:00/0000:00:10.0/0000:05:00.0/net/eno2
>> >
>> > [Link]
>> > MACAddress=02:00:00:00:05:00
>> > Name=mvc-sw1
>> > ```
>> >
>> > # mvc-sw2
>> > ```
>> > # Fixed MAC and name for enp6s0 (Block Diagram) when debug board is plugged in
>> > # Renamed to mvc-sw2 by PCI Address and set custom MAC address.
>> > [Match]
>> > Property=DEVPATH=/devices/pci0000:00/0000:00:11.0/0000:06:00.0/net/enp6s0
>> >
>>
>> These names are already the result of earlier renamoing. I am not sure
>> systemd/udev/networkd will rename the second time.
>>
>
> Would that be udev ?
>
> we're trying hard to use systemd for all our network management. If this is not a realistic goal, what is the correct way of managing our network with systemd alongside other tools ?
>

Yes, networkd.link files provide the desired names and naming policy,
it is systemd-udevd that applies them.

You need to match on some intrinsic device properties and these rules
must be present when systemd-udevd first sees and renames these
interfaces. Which often means in initrd/initramfs.