Question - VLANs with systemd-networkd in dracut-sshd

[helperlings]

Hi there,

this is not a direct bug but I hope someone can give me insight into this and maybe the answer will be helpful to other people as well.

I have several servers running dracut-sshd but now I have one that can not use an untagged network connection but needs a VLAN so that the network traffic is tagged with the appropriate ID.

I created a /etc/systemd/network/10-enp105s0f0.network file to bring up the interface

[Match]
Name=enp105s0f0
Type=ether

[Network]
# Bring the interface up without IP assignment
LinkLocalAddressing=no
DHCP=no

VLAN=vlan20

Additionally I created a 20-vlan20.netdev file to create a new interface.

[NetDev]
Name=vlan20
Kind=vlan
VLAN=enp105s0f0  # Parent interface
Id=20

Also I created a 30-vlan20.network file to bring up the network

[Match]
Name=vlan20
Type=vlan

[Network]
DHCP=yes

And finally I edited the /etc/dracut.conf.d/90-networkd.conf like this:

install_items+=" /etc/systemd/network/10-enp105s0f0.network /etc/systemd/network/20-vlan20.netdev /etc/systemd/network/30-vlan20.network "
add_dracutmodules+=" systemd-networkd "

and regenerated the initramfs.

Still when I reboot I can neither connect with SSH nor ping the device so something is not working here.

Any advice would be appreciated.

[gsauthof]

Hm, one thing I would double-check is the match section. Maybe the interface is enumerated differently in the early boot environment.

Perhaps it's possible to match on the MAC-address instead, as an alternative.

If this doesn't help, the generic advice is to get backup access to the console (e.g. via a BMC), boot into a dracut emergency shell as described in the README and debug the situation interactively.

[tessus]

I believe the order is wrong. 20-vlan20.netdev should be 00-vlan20.netdev. The other 2 are ok.

P.S.: Oh, and the 8021q module should be available/loaded.