Upgraded to 2.8.0. Kea causes all ports to fail
-
I'm running psfsense on a Qotom MIni PC. I've had no problems with version 2.7.2 and Kea enabled. After I upgraded to 2.8.0 all ports stopped working. If I reset the backend DHCP to ICS DHCP and reboot, everything runs fine. With Kea enabled, the ports aren't working and OpenVPN can't find its daemon.
Again, my configuration worked fine with Kea and 2.7.2.
Any suggestions?
Thanks.
-
@aiz said in Upgraded to 2.8.0. Kea causes all ports to fail:
After I upgraded to 2.8.0 all ports stopped working
What does 'all ports stopped working' refer too? Do the clients not get an IP anymore?
If yes, does KEA run? And are there any logs error regarding KEA?
-
When the kea config line is included in the config restore file all the activity lights on the box's ports go out. Looking at the console, the list of port assignments ahead of the pfsense menu are all correct. But the port is "dead" when I try to connect via the lan. If I manually assign the displayed IP address to the lan port from the console, I can then connect via the lan. The dashboard shows all the other ports (4 total) as not functioning and further shows an inability to connect with the OpenVPN daemon.
I also got a page full of php errors during my attempts to make things work. I'm pretty unsophisticated at this networking stuff but I'm trying to plod through it. In the interim, I'm sticking with 2.7.2. It seems to work fine.
[16-Aug-2025 16:04:04 America/Chicago] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 162 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(162): array_get_path()
#1 /etc/inc/system.inc(628): kea_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/rc.bootup(215): system_hosts_generate()
#4 {main}
thrown in /etc/inc/util.inc on line 3961
[16-Aug-2025 16:06:34 America/Chicago] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 162 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(162): array_get_path()
#1 /etc/inc/system.inc(628): kea_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/inc/services.inc(4983): system_hosts_generate()
#4 /etc/inc/interfaces.inc(4475): services_unbound_configure()
#5 /etc/inc/interfaces.inc(443): interface_configure()
#6 /etc/inc/interfaces.inc(4045): interface_vlan_configure()
#7 /etc/inc/interfaces.inc(4212): interface_virtual_create()
#8 /etc/inc/interfaces.inc(443): interface_configure()
#9 /etc/inc/interfaces.inc(375): interface_vlan_configure()
#10 /etc/inc/interfaces.inc(1630): interfaces_vlan_configure()
#11 /etc/inc/pfsense-utils.inc(1073): interfaces_configure()
#12 /etc/rc.initial.setports(42): reload_interfaces_sync()
#13 {main}
thrown in /etc/inc/util.inc on line 3961
[16-Aug-2025 16:06:40 America/Chicago] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 162 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(162): array_get_path()
#1 /etc/inc/system.inc(628): kea_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/rc.newwanip(150): system_hosts_generate()
#4 {main}
thrown in /etc/inc/util.inc on line 3961
[16-Aug-2025 16:06:41 America/Chicago] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 162 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(162): array_get_path()
#1 /etc/inc/system.inc(628): kea_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/rc.newwanip(150): system_hosts_generate()
#4 {main}
thrown in /etc/inc/util.inc on line 3961
[16-Aug-2025 16:11:02 America/Chicago] PHP Fatal error: Uncaught TypeError: array_get_path(): Argument #1 ($arr) must be of type array, string given, called in /usr/local/pfSense/include/www/services_dhcp.inc on line 162 and defined in /etc/inc/util.inc:3961
Stack trace:
#0 /usr/local/pfSense/include/www/services_dhcp.inc(162): array_get_path()
#1 /etc/inc/system.inc(628): kea_earlydnsreg_mappings()
#2 /etc/inc/system.inc(660): system_hosts_entries()
#3 /etc/inc/interfaces.inc(4459): system_hosts_generate()
#4 /etc/inc/interfaces.inc(1808): interface_configure()
#5 /etc/rc.initial.setlanip(495): interface_reconfigure()
#6 {main}
thrown in /etc/inc/util.inc on line 3961 -
@aiz said in Upgraded to 2.8.0. Kea causes all ports to fail:
/usr/local/pfSense/include/www/services_dhcp.inc on line 162
It looks like your config contains some old dhcp server settings for interfaces that no longer exist. That shouldn't be possible but if it was an older config that has been upgraded across many versions it might pre-date the error checking.
Are you able to upload the config for us to test against?
https://nc.netgate.com/nextcloud/s/4oBCW3MWNoHx5q5 -
@stephenw10 Thank you for the response. I just uploaded my latest config file.
I should also have noted that it appears not to be a hardware problem. If I install 2.8.0 and set the dhcpbackground to kea, it works fine. The failure occurs when I upload my config file.
I look forward to anything you might find.
-
Great I see that. So that is the backup from 2.7.2 with Kea enabled? Before upgrading?
-
Yup, OK. It's almost certainly the empty tags for opt3 in the dhcpd section there. Line 662 in the config:
... <opt3></opt3> ...If you remove that line Kea should start normally with early DNS registration enabled in 2.8.0.
-
@stephenw10 You were exactly correct! I removed the line and the firewall is working just fine. In fact, I see the performance increase people were talking about. (One day I may understand how that line got there since I do virtually all of my configuring through the GUI.)
Thank you very much for your help.
