Kea DHCP stops working
-
Yes, but when it's renewing it will just request the old IP. And in some cases will just request an old cached lease address anyway. The server can refuse and issue a new lease.
However it sounds like it's just not seeing the new static lease entry.
Do you see the reservation listed in /usr/local/etc/kea/kea-dhcp4.conf? -
@stephenw10 said in Kea DHCP stops working:
Do you see the reservation listed in /usr/local/etc/kea/kea-dhcp4.conf?
Yes, the IP is in the file against the correct MAC
but looks like not being offered?
-
@RobbieTT said in KEA DHCP - lacking features:
Before it went live it was suggested that encouraging users to leave ISC for Kea was rather over done, considering its immaturity.
I did switch to Kea during the beta period and it was seamless with no apparent drawbacks but once I released some basics were missing and that it was relying on previous ISC managed data to function, had me switching back.
As I understand it, simple static mappings / reservations from Kea are not actually supported. However, it may give an illusion of functionality if you have run ISC previously. Existing mappings / reservations will still be resolvable as the hosts file still contains them as a hang-over from running ISC. Any new mappings added or modified will not be resolvable.
To me, the ability to set a static mapping / reservation is a basic cornerstone of networking. I think there will be a cascade of confusion as and when the previous hosts file becomes out-of-date.
️That's a post from back in 2023 and looks like it's not fixed. I think that's exactly happening here too - the already existing records (from ISC) are working and the new ones are not at all.
-
Nope that's unrelated. At that time both dynamic and static leases were not resolvable at all. 24.11 has out custom binary that handles the Kea-Unbound glue to allow it. But that didn't affect the actual leases, only resolving hosts.
What client type are you testing this from?
-
@stephenw10 said in Kea DHCP stops working:
Nope that's unrelated. At that time both dynamic and static leases were not resolvable at all.
May be it was but still matches exactly with my case. Probably this particular part somehow escape testing before release?
@stephenw10 said in Kea DHCP stops working:
What client type are you testing this from?
I tested with two MacBooks, Minix U22-XJ, Raspberry Pi 5 and even with a Netgate 6200 - none of 'em got the IP they deserv :)
If that's what you meant. It doesn't matter what client or type - any new mapping (brand-new or edited) not working.Pls let me know if there is anything else I can provide to get it fix.
-
@MacUsers said in Kea DHCP stops working:
May be it was but still matches exactly with my case.
So you are also seeing issues resolving hosts?
-
Can you test the 25.03-Beta?
I can't replicate that issue here. I reconnect a client (Linux Laptop) after setting a static lease and it immediately pulls that. -
@stephenw10 said in Kea DHCP stops working:
So you are also seeing issues resolving hosts?
I was talking about this part:
-
@stephenw10 said in Kea DHCP stops working:
Can you test the 25.03-Beta?
Is Beta stable enough to run for regulat use atm? Anything in particular I should be aware of before upgrading?
-S
-
Yes, I'm running it as my edge device now and have been for some time.
If you're running ZFS you always roll back to the 24.11 BE snap anyway.
-
Thnaks @stephenw10!
I'll give it a try. Kea is definately not working, for me, to do the static mapping without restarting PFS.-S
-
Kea started crashing a few days ago, requiring a reboot almost every day to resolve this week. Sometimes Kea would restart, sometimes required reboot. Upgraded to 25.03 BETA (amd64) and Kea continues to fail. I reverted back to ISC to keep the network stable.
-
Anything logged?
-
I didn't get around to upgrade to Beta but without any known development to fix Kea issue, I think it'll continue to fail.
@swmspam said in Kea DHCP stops working:
Kea started crashing a few days ago, requiring a reboot almost every day to resolve this week
Just out of interest, is happening on any Netgate device, especially 6200 or 8200?
-S
-
There are a load of fixes in 25.03. AFAIK this issue is fixed there for arm64 and aarch64. You should try the beta if you can. If there is still an issue there we need to know about it.
-
@MacUsers said in Kea DHCP stops working:
is happening on any Netgate device, especially 6200 or 8200?
Can't speak for those device, I use a 4100. So a very comparable CPU.
The sofwtare (binaries) are all the some, bit for bit.
The OS also.
Only our 'settings' differ.My kea runs flawlessly.
24.03 was already good for me, now, just for the fun, I use 23.03 beta and no issues what so ever.[25.03-BETA][root@pfSense.bhf.tld]/root: ps aux | grep kea root 15715 0.0 0.6 50404 24708 - S 26Feb25 2:00.36 /usr/local/sbin/kea-dhcp4 -c /usr/local/etc/kea/kea-dhcp4.conf root 16458 0.0 0.6 47800 24420 - S 26Feb25 0:53.59 /usr/local/sbin/kea-dhcp6 -c /usr/local/etc/kea/kea-dhcp6.conf root 62819 0.0 0.5 34780 18464 u0 I 26Feb25 0:00.11 /usr/local/sbin/kea-dhcp-ddns -c /usr/local/etc/kea/kea-dhcp-ddns.confI even manually kick started "kea-dhcp-ddns", not yet supported by pfSense (GUI), but I saw it was there and I needed it.
For more then 6 moths I use the patch that adds DHCP Options to kea : works perfectly.I'm writing my goodbye word for ISC right now.
-
Apologies to the community, I didn't capture the logs. It's a bit of a pain at this point. I can only run Kea during the afternoons when I can oversee it, but have to switch back to ISC during the night. There's no way to guarantee Kea will crash opportunistically.
Running on mini-ITX motherboard with:
Vendor: American Megatrends Inc.
Version: P1.00
Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
Current: 1500 MHz, Max: 1501 MHz
4 CPUs : 1 package(s) x 4 core(s)
Memory: 4GB
Storage: 60GB SATA SSD -
Might this issue be related? It’s about a static mapping for a Synology NAS that only turns on 3am to 4am for backups and also incidentally at day time for video playback. Yesterday it received a fresh dynamic IP from the KEA DHCP server, which should be considered a DHCP malfunction.
I am not 100% certain that it’s a 24.11 issue, but 15 days ago I went from 24.03 (never had KEA DHCP issues) to 24.11 and this error is the first time since.
-
You have all the patches applied in 24.11?
How loaded is subnet? Like number of clients vs available dhcp leases?
