VLAN joy denied

[boldandbusted]

Howdy. I've got a 'metal' setup like so:

I have a 'smart switch'. I've got a node attached to the switch. The port it is connected to has a "untagged" setup which has PXE services on it, and I'm using iPXE with DHCP to boot Talos (yay!). I have OpnSense handing out the PXE files, and the DHCP addresses. That works fine.

What I want to do is have a VLAN that the nodes switch to after boot, and use DHCP there to get their addresses, routes, NTP servers, DNS search domain, hostnames, etc. I have this patch that I've applied, and it seems like Talos is getting it:

---
machine:
  network:
    interfaces:
      - interface: en01
        dhcp: true
        vlans:
          - vlanId: 411
            dhcp: true

The primary interface on all hosts is en01. However, I get no love from this setup - only the physical interface gets a DHCP assignment. I did a network sniff of the VLAN, and there's no traffic at all from the cluster hosts. :(

I took a look at the Talos Advanced Networking for Metal docs, and it doesn't seem to have a way to configure DHCP on a VLAN interface, but perhaps I'm reading the Talos Advanced Networking spec wrong? I would like to keep it simple, and not have to reach for Advanced Networking, if I can avoid it.

Thanks in advance for the help. Cheers.

[smira]

I wonder if your interface is eno1, not en01 ?