Does static mapping work in kea DHCP?
-
It worked fine for me for several months since I don’t use name resolution typically. Were I did run into problems was when I replaced an existing device and changed the MAC address used to reserve that IP. KEA wouldn’t handout the proper IP until the old reservations had expired for both devices. This made it complicated to access webui’s to do configurations of devices. Rebooting the Netgate appliance would correct this and maybe there are other workarounds as well but I never really saw any benefit to me running KEA so decided to wait until it’s a little more mature. This really just applies to my use case though. I’m sure many people don’t even use MAC reservations.
-
@wgstarks said in Does static mapping work in kea DHCP?:
I’m sure many people don’t even use MAC reservations.
That might be a good poll.. The only things that don't have reservations on my network - are guest devices, like friends phone on my guest wifi. And devices when I first bring them online.. As soon as its ready to actually join the network full time, it gets a reservation and IP set, etc..
Just powered up my new nvr with cameras for outside.. To just make sure it worked and cameras worked, etc. I just plugged it into port on switch in the av cab.. It came up on my roku vlan.. Made sure it all worked - then setup a reservation for it on my new cam vlan.. Changed the config on the port on that switch, and rebooted it. Now its up on correct vlan, with IP I assigned it, etc..
I would bet many users of pfsense, use at least some reservations.. Can we create "polls" here on the forum, I don't think have ever seen one.. I would be curious to see.. Might throw up something in general off topic section.. even have to just count posts..
-
@johnpoz said in Does static mapping work in kea DHCP?:
Can we create "polls" here on the forum
You should probably talk to a Global Moderator about that. ;)
-
@SteveITS ahahahah - oh that is funny ;) hahaha
Here we go, https://forum.netgate.com/topic/186312/do-you-use-dhcp-reservations
Mod is different than Admin btw.. I can delete posts, that sort of thing.. But any sort of backend anything to do with the forums would have to be an Admin... You had me rolling on that comment.. Still giggling.. Good one!
-
@johnpoz said in Does static mapping work in kea DHCP?:
Can we create "polls" here on the forum
I'll start right away : don't.
@johnpoz said in Does static mapping work in kea DHCP?:
I would bet many users of pfsense, use at least some reservations..
Others, recently, just refuse to do so. For whatever their reasons are.
( they will be forced to the light as soon as IPv6 becomes main stream ) -
I'm running CE 2.7.2 and the static DHCP mapping does not work for me with KEA.
So here's the static mapping for my
alpine
host.
And here's the DHCP leases where the same host got a second (dynamic) IP assigned.
As I've never observed such a behaviour in the past, I switched back to the ISC DHCP.
-
@CyBiS https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#kea-dhcp-server-feature-preview-now-available
“Currently the Kea implementation lacks the following DHCP server features:
Local DNS Resolver/Forwarder Registration for static and dynamic DHCP clients”
-
@SteveITS Thanks for the link, but I'm not sure how that is related to the static DHCP mapping (MAC address to IP address). I'm not looking for DNS resolution of the host (
alpine
host name to IP address) but its actual IP/DHCP lease which is supposed to be static, i.e. the host must not get any other IP than the one specified in the static DHCP mapping. -
@CyBiS ah, sorry I misunderstood. I think there was a thread about that either here or on Reddit. IIRC it was a theory about how it had the lease already so was granted the renewal instead of sending the new/static IP? I didn’t notice it but mine had the same IPs for the brief time I used Kea.
-
@SteveITS No problem I had KEA active for a couple of weeks now but today I noticed the first time that the policy-based routing for that particular host wasn't working as expected due to the wrong IP. Not sure though what exactly triggers this incorrect DHCP lease.