Kea DHCP stops working
-
okay, basically nothing is changng/updating related to DHCP. In one of the static-mappings, I provided custom DNS Servers (under the Server Options) and it's still showing the old DNS server address, even after restarting the client device. I'm very sure that it won't change, regardlessly what I do from/on the client side, nothing will change until I reboot the PFS box.
I'll restart and report here back soon.
-
@MacUsers said in Kea DHCP stops working:
Just to give it a benefit of doubt: how do I chk that device was actually pulling a new lease?
The logging in Kea is (currently) unhelpful for that.
The only way to really know for sure would be to run a packet capture when the client renews and see what's actually being sent.
-
The packet capture setup for DHCPv4 :
-
Select the interface you want to capture, typically LAN
-
The details : you want them all
-
It's UDP
-
and ports involved are 67 and 68.
-
Hit start.
-
Go to a device, and execute the DHCP Release and then DHCP renew command.
Get back to pfSense, and you should see a (1) packets coming in (the DHCP request) and the one packet getting send to the device with the DHCP lease info.
-
-
Okay, I do see the request hitting PFS when I release and renew the lease:
But no change in IP at all, as it should be
10.1.20.12now as that's what the static mapping is now set:
🔒 Log in to viewThis is happening for every single devices I have tested so far. Do you need the full capture?
-
Hmm, note that it's requesting the old IP. If you clear the client side lease cache does it get the new static IP?
Might need to force that in Kea.
-
@stephenw10 I did everything: restarted Kea, cleared client side lease, even tried with a brand new device, predefined static mapping even before pluging in - not getting the actual IP if PFS not rebooted. Trying out all the usual stuff for almost a week now.
In case of the brand new device, it's getting an IP from the dynamic pool but that lease is not showing up inStatus > DHCP leaseat all. -
@stephenw10 said in Kea DHCP stops working:
note that it's requesting the old IP
Question though - how it's gonna know what IP to ask for, in the first place?
AFAIK, device broadcasts aDHCP Discovermessage to find a DHCP server and the DHCP server responds with aDHCP Offergiving it an IP. Kea should offer the IP from static-mapping and after accepting that offer (followed by aDHCP Request), it should beAcknowledgedby the server - is not what happens? -
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
🔒 Log in to viewbut 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:
🔒 Log in to view -
@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?