DHCP Pool not showing leases for VLANs

General questions
,
1

Version: VyOS 1.4.0-rc3
Release train: sagitta

DHCP isn’t showing my leases for my VLANs when I use “show dhcp server leases” or “show dhcp server leases pool Users”

It is working just fine for leases not using a VLAN.

set shared-network-name xxxxxx authoritative
set shared-network-name xxxxxx subnet xxx.xxx.3.0/24 default-router ‘xxx.xxx.3.1’
set shared-network-name xxxxxx subnet xxx.xxx.3.0/24 description ‘For casting devices’
set shared-network-name xxxxxx subnet xxx.xxx.3.0/24 name-server ‘xxx.xxx.8.8’
set shared-network-name xxxxxx subnet xxx.xxx.3.0/24 name-server ‘xxx.xxx.2.2’
set shared-network-name xxxxxx subnet xxx.xxx.3.0/24 range 0 start ‘xxx.xxx.3.10’
set shared-network-name xxxxxx subnet xxx.xxx.3.0/24 range 0 stop ‘xxx.xxx.3.240’
set shared-network-name xxxxxx authoritative
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 default-router ‘xxx.xxx.0.1’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 description ‘For lab devices in Unraid’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 name-server ‘xxx.xxx.0.1’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 range 0 start ‘xxx.xxx.0.10’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 range 0 stop ‘xxx.xxx.0.150’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 default-router ‘xxx.xxx.0.1’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 name-server ‘xxx.xxx.8.8’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 name-server ‘xxx.xxx.2.2’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 range 0 start ‘xxx.xxx.0.50’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 range 0 stop ‘xxx.xxx.0.240’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx ip-address ‘xxx.xxx.0.83’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx mac-address ‘xx:xx:xx:xx:xx:40’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx ip-address ‘xxx.xxx.0.78’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx mac-address ‘xx:xx:xx:xx:xx:39’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 vendor-option ubiquiti unifi-controller ‘xxx.xxx.0.78’
set shared-network-name xxxxxx authoritative
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 default-router ‘xxx.xxx.0.1’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 name-server ‘xxx.xxx.8.8’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 name-server ‘xxx.xxx.2.2’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 range 0 start ‘xxx.xxx.0.2’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 range 0 stop ‘xxx.xxx.0.254’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx ip-address ‘xxx.xxx.0.232’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx mac-address ‘xx:xx:xx:xx:xx:BF’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx ip-address ‘xxx.xxx.0.176’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx mac-address ‘xx:xx:xx:xx:xx:8a’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx ip-address ‘xxx.xxx.0.221’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx mac-address ‘xx:xx:xx:xx:xx:f9’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx ip-address ‘xxx.xxx.0.241’
set shared-network-name xxxxxx subnet xxx.xxx.0.0/24 static-mapping xxxxxx mac-address ‘xx:xx:xx:xx:xx:77’

2

Make sure the vlan has an IP address in that space (bit by that one myself).

If you have not already, tcpdump the VIF and make sure it sees BOOTPC datagrams to rule out any inside switch/vlan issues.

If all that is good, you can try sending a HUP to the running kea-dhcpv4, restart with systemd or reboot. Apparently, there is an issue where kea-dhcpv4 does not always pick up new VIFs and it seems others have filed bug reports on it.