Any news about this ?

I see the same issue, does this need tests ?

@varesa You are mixing VirtIO which needs offloading, ESXi doesn't need that, nor it's driver. It's related to native KVM mostly.

@syncer you need it on Hypervisor tap level not in the VM itself.

Update, VirtIO works: on the Hypervisor: ethtool -K <interfacename> tx off

@syncer I use(d) VirtIO driver on KVM, works OK except for the DHCP part it seems which is kinda strange.

@c-po I moved the config from a VirtIO to a vmxnet3 interface and now I get DHCP. so something is wrong with the VirtIO drivers ?

@c-po I understand partly what you say but what differs Commercial Support from community as it not work at all, I assume other Commercial Customers would have the same issue and still not fixed (for years it seems??)

@c-po how much work is it to adjust your lab for this ? most of us did this on the fly as it's not that much work and difficult. I would like to make a decission as there is too much rumour around DHCP(-RELAY) handling by VyOS and it's not going to help at the moment.

@c-po ok please let me know! I'm kinda stuck here :)

@c-po What can cause my issue that my clients don't receive the PACK as shown in the topic ? I'm unable to debug it, all inferfaces are set for dhcp-relay.

@varesa no it does not work with normal hosts, also not with PXE.

I have tested this also with putting the DHCP subnet tagged on the interface itself within proxmox. Same problem occures... So removing the server from the vlan.interface doesn't change a thing, I could test with the clients on their own interface (ethX) and add that to the relay section instead of ethX.clientVlanId but I doubt if that works.

@byteshifter are you able to give is some tcpdumps on the dhcp-ports on the switch and also some tcpdumps/logging on the DHCP server ?

@varesa as far as I can see from his start post he has already set that.

@varesa all done like that indeed.

@varesa mention that you are running it on a ESXi VM and I do KVM (proxmox). I have seen messages that it could matter...

I seem to run into the same issue but it also happened on 1.18 for me, reported here: