KEA DHCP missing "Register DHCP leases in DNS Resolver..."
-
@Qinn doesn't really answer the question. Where do we get a list of the patches available and what they are for?
-
Install this package, you see a list recommended system patches for Netgate pfSense and for each patch there is a description what it does or do. After you installed the package see this list and you can choose to apply each one of them individually (even revert most of them if you for some reason want to) or change nothing and remove the whole package, as in the link above this package is recommended by Netgate.
-
@Qinn no recommendations
-
@4o4rh what version are you on? 24.03 has none because their code is included.
Typically patches appear either a few weeks/months after a release, to fix bugs, or else they dropped a bunch of them for 2.7.2/23.09 after 24.03 was released because there are security fixes they backported for 2.7:2,
https://forum.netgate.com/topic/187622/system-patches-package-v2-2-10_1Patches appear after the package is updated not on their own.
-
Same question here ;)
Btw I am on 2.7.2 CE ( as is in my signature) and use System_Patches v2.2.10_1, updated recently, say last week and as you can see patches are sane to install, as like this example https://redmine.pfsense.org/issues/14991 is target for the not released pfSense version 2.8.0
[2.7.2-RELEASE][root@pfSense.localdomain]/root: pkg info pfSense-pkg-System_Patches-2.2.10_1 pfSense-pkg-System_Patches-2.2.10_1 Name : pfSense-pkg-System_Patches Version : 2.2.10_1 Installed on : Wed Apr 24 10:50:01 2024 CEST Origin : sysutils/pfSense-pkg-System_Patches Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : sysutils -
I somehow got burned by this too. No, I do not read release notes, I just trust that the latest and greatest firmware protects my family's network. I had some performance issues on my ISP so rebooted everything to try to fix and it took me several hours to get to a root cause. I am sad, but happy to have it all back up and running nicely. Next time I will be more leery!
-
It's been well over a year right? Still waiting. I would be very surprised if this was that hard to integrate considering half the code is already written for the DHCP half.
-
Glad I found this thread. I was trying to figure out why DHCP leases weren't resolvable on my home network when they once were. Forgot that I had cut over to KEA DHCP days ago. Reverted to ISC DHCP and checked "Ignore Deprecation Warning" - all better now.
-
I too followed the EOL suggestion and switch - and this is a total mess. How can I back this change out, I see nothing to switch back!!!
How can you POSSIBLY suggest this dysfunctional nonsense as an alternative? You've had this out for what, almost a year now - and it's still totally broken.
CAN YOU FIX YOUR BROKEN SH*T?!
-
@bson https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#kea-dhcp-server-feature-preview-now-available
"Administrators can easily switch between ISC DHCPD and Kea by navigating to System > Advanced, Networking tab and changing the new Server Backend setting in the DHCP Options section."
The wording in pfSense about ISC DHCP is a bit misleading but Kea is in "feature preview" a.k.a. alpha/beta/whatever.
-
The current goal is to have Kea at feature parity with ISC DHCP by the end of the year, then one release with Kea being optional, another release with Kea being the default for new installs, and finally another release to completely remove ISC DHCP entirely.
-
@SteveITS I switched it back but it still wouldn't resolve. I don't know what fixed it, perhaps DNS caches just had to expire, or my poking around in DDNS options (we don't use DDNS) fixed it. I think I enabled the DDNS host registration option without overall enabling DDNS. It's not clear if that has any effect or not, but after a while things were working again. Famous last words! Without it being at feature parity I think it's fine to as for testing feedback, but there shouldn't be a nag about it being deprecated. This suggests a need to migrate. It should also warn about a lack of feature parity, IMO.
-
Oh, I think I know why it took a while to return to normal: the migration wipes the existing leases, and it takes a while for clients to discover this and renew. Until that happens the client identifiers aren't going to be injected into DNS.
-
@bson said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
This suggests a need to migrate. It should also warn about a lack of feature parity, IMO.
That's fair. The current warning definitely has a "the sky is falling" tone to it, which it certainly isn't.
-
This post is deleted! -
@cmcdonald said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
That's fair. The current warning definitely has a "the sky is falling" tone to it, which it certainly isn't.
This. 100% this. The warning gives the impression that one should update ASAP and gives zero indication that the replacement isn't feature complete.
-
Still an issue.
-
@softwareplumber said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
Still an issue.
https://www.netgate.com/blog/improvements-to-kea-dhcp
-
There is no longer a way to revert back in the GUI, so my setup is broken.
It should not have been released without better migration testing.
-
@uneventfullogs I believe you should be able to revert in System->Advanced->Networking. At least, that's where I've been able to do it in the past.
