after a reboot the system (Fedora 35) comes up like this:
# ss -tulpn | grep kea udp UNCONN 0 0 0.0.0.0:44267 0.0.0.0:* users:(("kea-dhcp6",pid=734,fd=16)) udp UNCONN 0 0 127.0.0.1:53001 0.0.0.0:* users:(("kea-dhcp-ddns",pid=728,fd=10)) udp UNCONN 0 0 0.0.0.0:45047 0.0.0.0:* users:(("kea-dhcp4",pid=731,fd=16)) udp UNCONN 0 0 10.0.0.10:67 0.0.0.0:* users:(("kea-dhcp4",pid=731,fd=19)) after restarting kea-dhcp6 it looks like this: # ss -tulpn | grep kea udp UNCONN 0 0 127.0.0.1:53001 0.0.0.0:* users:(("kea-dhcp-ddns",pid=728,fd=10)) udp UNCONN 0 0 0.0.0.0:59344 0.0.0.0:* users:(("kea-dhcp6",pid=1463,fd=16)) udp UNCONN 0 0 0.0.0.0:45047 0.0.0.0:* users:(("kea-dhcp4",pid=731,fd=16)) udp UNCONN 0 0 10.0.0.10:67 0.0.0.0:* users:(("kea-dhcp4",pid=731,fd=19)) udp UNCONN 0 0 [fd00::10]:547 [::]:* users:(("kea-dhcp6",pid=1463,fd=19)) udp UNCONN 0 0 [fe80::71aa:aab2:a98a:445c]%enp1s0:547 [::]:* users:(("kea-dhcp6",pid=1463,fd=20)) udp UNCONN 0 0 [ff02::1:2]%enp1s0:547 [::]:* users:(("kea-dhcp6",pid=1463,fd=21)) # kea-dhcp4 -V 2.0.2 tarball linked with: log4cplus 2.0.5 OpenSSL 1.1.1n FIPS 15 Mar 2022 database: MySQL backend 12.0, library 10.5.5 PostgreSQL backend 6.2, library 130004 Memfile backend 2.1 # kea-dhcp6 -V 2.0.2 tarball linked with: log4cplus 2.0.5 OpenSSL 1.1.1n FIPS 15 Mar 2022 database: MySQL backend 12.0, library 10.5.5 PostgreSQL backend 6.2, library 130004 Memfile backend 2.1 - What are the extra ports - beyond 67 and 547 - good for? - Why does kea-dhcp6 always need a restart? - Why does kea-dhcp6 bind to [ff02::1:2] if it is configured to get requests via a dhcp relay? -- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users