XG-7100 & Unify console troubles: dhcp-kea reports diffently depending...? headaches continuing. kea2unbound socket unfound!

pfS_noob_cust

Simple test config. Factory defaults, use different VLANs on each of the 6 switch ports. Fully define 2, with different VLANs & kea-DHCPd ranges.
WAN is lagg0:4090, LAN is lagg0:4091
Each switchport has its own VLAN. 2 were

Good news is: attached device gets an IP address.
Bad news is:

it gets the same LAN address, not the VLAN & port specifc address
INTERFACES reports different shown in DHCPd Leases

Current Boot Environment: default
Next Boot Environment: default

WAN (wan) -> lagg0.4090 -> v4/DHCP4: 1...WANaddr...2/24
LAN (lan) -> lagg0.4091 -> v4: 10.33.33.1/24
OPT1 (opt1) -> ix0 ->
OPT2 (opt2) -> ix1 ->
OPT3 (opt3) -> lagg0.10 ->
OPT4_P4 (opt4) -> lagg0.20 -> v4: 172.16.22.1/24
OPT5 (opt5) -> lagg0.30 ->
OPT6_P6 (opt6) -> lagg0.40 -> v4: 172.16.62.1/24
OPT7 (opt7) -> lagg0.50 ->
OPT8 (opt8) -> lagg0.60 ->
OPT9 (opt9) -> lagg0.70 ->
OPT10 (opt10) -> lagg0.80 ->
OPT11 (opt11) -> lagg0 ->

what I got, when I plugged annabelle into each of these was.
10.33.33.12
10.33.33.12
even though kea-dhcp was configured with KNOWN HOSTS on both locations.

Rebooted…And, voila, something’s weird…

but DHCPd Leases showed what the attached device saw...
DHCEd Leases.2.png

Why is that?
thanks.

Also, tested changing "ALLOW ALL CLIENTS" to "Allow known clients from only this interface" after creating a Static Mapping for the device.

Same result: device shows LAN address, not switchport specific port.

dig reports the LAN based address.
DHCP Leases shows the static mapping, without an IP address though.

Looking through dhcpd.log, one sees...
Jun 13 16:20:27 bulwark kea2unbound[78282]: Unable to find a Kea control socket: /var/run/kea4-ctrl-socket

Seems that might explain part of this.