IPv4 TCP/UDP Clients net * DruckerScanner net 631 * *
IPv4 TCP/UDP Clients net * DruckerScanner net 515 * *
IPv4 TCP/UDP Clients net * MulticastDNS 5353 - 5354 * *
IPv4 TCP Clients net * DruckerScanner net 80 (HTTP) * *
IPv4 TCP Clients net * DruckerScanner net 443 (HTTPS) * *
IPv4 ICMP Clients net * DruckerScanner net * * *
IPv4 TCP Clients net * DruckerScanner net 631 * *
IPv4 TCP Clients net * DruckerScanner net 80 (HTTP) * *
IPv4 TCP Clients net * DruckerScanner net 443 (HTTPS) * *
# Setup ng_bridge if required
if ! ngctl status bnet0: >/dev/null 2>&1; then
ngctl -f- <<END
mkpeer igc0: bridge lower link0
name igc0:lower bnet0
connect igc0: bnet0: upper link1
msg igc0: setpromisc 1
msg igc0: setautosrc 0
END
fi
bhyve \
-c sockets=1,cores=8,threads=1 \
-m 16G \
-s 0,hostbridge \
-s 2,virtio-blk,/vm/hdd.img \
-s 3,virtio-net,netgraph,path=bnet0:,peerhook=link2 \
-s 4,virtio-9p,data=/zdata/vm \
-s 5,virtio-rnd \
-s 31,lpc \
-l bootrom,/vm/BHYVE_UEFI.fd,/vm/efi-vars.fd \
-l com1,stdio \
-u \
-H -P -S \
Quote from: Stormscape on December 25, 2025, 10:10:12 AMExactly — Kea isn't dnsmasq. The DHCP behavior differs, and Unbound will need some extra configuration for IPv6 to fully integrate reservations. It's not a bug, just a difference in implementation.Quote@DEC670airp414user. Is there a downside to DNSSEC? From google:Well Kea isn't dnsmasq, now is it?
"DNSSEC as securing the message content (authenticity)"
"DoT as securing the envelope (privacy/confidentiality)."
Both of these seem like it would be a benefit.
@Stormscape. I do not think your answer is accurate. I use kea for DHCP and unbound.
IPv4 LAN does get local name resolution.
IPv6 LAN gets resolution when a reservation is added after a restart of the unbound service.