KIA DHCP ISSUES having to switch to ISC
-
So I've had the worst luck with kia dhcp... very buggy, giving errors when I can't see why. There's no conflicts that I can see and no overlapping.. there's plenty of ip's in each pool/vlan. It won't give a dhcp address on any new device that connects to the network wired or wireless. The static mappings I thought were ok but I had an issue with one of those tonight it wouldn't give the ip.
I created another vlan and started moving everything over to that vlan cause this was only happening on 1 vlan.. but now it's happening on the new vlan too lol. I finally gave up and reverted to ISC and now so far I'm not having any issues. Has anyone else had to do this and if so is there anything to be concerned about being on the old option? I made a backup before switching I guess we'll see what happens.
Also I keep seeing where it's said to check for conflicts and overlapping..... if that were possibly the case or if that was happening switching back to ISC wouldn't fix that I wouldn't think would it? A conflicting ip or mac address would be an issue using either I would think but switching has fixed everything so far which I believe it to be KIA hasn't matured yet and still sucks. Either I hope it's better in the next release and or ISC is in the next release as well to fall back on if need.
-
No details, so let me throw in one : simply the network : no more VLANs, and I'll bet your issue is over ^^
Btw : from forum. There is a :
forum with many 'My DHCP doesn't work' and the 'Here is the answer'.
Over there you will find something to add to kea so it does what pfSense had when we were using ISC : DHCP lease logging. This will make a log file with the DHCP leases that kea offered.
The file ( ) isn't visible in the pfSense GUI, but you can have a look at it if needed. It's auto pruned so you don't need to take care of it (file getting to big, etc).
I guess Netgate removed the logging of lease offerings as it is so .. dull.
But : handy if you're looking for issues.kea, when it starts, has only you settings (in the GUI) to work with.
It's 'memory' = the state it was in in the past, is a file, and you can find it here : /var/db/kea/
What you could do : Stop kea.
Delete everything in /var/db/kea/ (or smarter : make a copy)
Start kea.@khris2fer said in KIA DHCP ISSUES having to switch to ISC:
overlapping
Between the pool = a bunch of 'randomly' assigned devices, and the static MAC leases. These should not (imho) overlap.
Example : the static assigned leases from 10 to 100, and the pool from 101 to 150. That works fine for me ever since.@khris2fer said in KIA DHCP ISSUES having to switch to ISC:
Either I hope it's better in the next release and or ISC is in the next release
Be aware :
A next pfSense will have the same ISC (as the code isn't maintained for years now) and if the slightest security issue is found, it will be removed from by pfSense. ISC isn't maintained anymore.
Kea is stable since ... a couple of years now. With stable I mean : it's used "by the millions". Look at the DHCP forum : there aren't many asking questions about it because 'it doesn't work'.
Kea is a total rewrite of ISC (same author, so they tend to know how to write a DHCP server) and as ISC before, kea tends to be the most used DHCP server on the planet.
pfSense add just ^^ a GUI interface so you don't have to create it's config file yourself : /usr/local/etc/kea/kea-dhcp4.conf
Of course, I don't say 'kea' hasn't any bug, it probably has. But your lucky, millions are using it, so it's probably just you == your settings (and other network settings on switches as you use VLANs) ^^.An easy way to see what happens : have a look here and select the interface where you want to have a look at. You can filter whatever you want. You'll see the device asking for a lease, and the answer from pfSense (kea).
Still nothing ? Then it's time to tell us more about your setup.
-
Did you see any errors logged when it stopped handing out leases?
Did you still see dhcp requests arriving at pfSense?
-
@Gertjan Thanks for the info I'll check out the dhcp part of the forum. I kept getting WARN [kea-dhcp4.alloc-engine.0x1d7af815f00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 bc:32:19:d8:98:c9], cid=[no info], tid=0x491d466a: conflicting reservation for address 192.168.50.14 with existing lease Address: 192.168.50.14 Valid life: 86400 Cltt: 1785434829 Hardware addr: Client id: (none) Subnet ID: 8 Pool ID: 0 State: declined Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "home.arpa" } } }
I could clear out the dhsp leases and arp table and it would clear it up for a few minutes. I would get this error when joining a new device.
I could get rid of my vlans but that's one of the features that I use Pfsense for. Otherwise I would have like a tp-link router and let it do its thing.
Ever since going to ISC I haven't had one problem which tells me KIA is still crap until it gets better. I guess I'll hang out here until I have good enough reason to try kia again. Thanks for the reply
-
@khris2fer what pfSense version are you using, CE 2.8.1 or pfSense+ 25/26?
-
@patient0 Yes 2.8.1 running on a Protectli vault
Privacy Policy · Cookie Policy