Come on, let us create DHCP reservations inside the pool
-
@CCNewb
https://docs.netgate.com/pfsense/en/latest/services/dhcp/mappings-in-pools.htmlOne can also create an Additional pool, so .10-.19 and .21-.49 to exclude .20.
https://docs.netgate.com/pfsense/en/latest/services/dhcp/ipv4.html#additional-pools
-
@CCNewb so 300 some DHCP servers? I am curious to why you would even be running DHCP on pfsense - if what your after is so simple on any of your 300 some DHCP just run dhcp on one of those pfsense can relay DHCP to one of those
-
Sometimes context is important. We have over 100 DHCP servers. Sounds crazy, but we have over 100 sites around the world. We have how many we need.
Back to the subject, it would be nice to be able to have reservations in the scope. The kindly provided links indicate the DHCP server is 1 flag from working this way. If an address has a reservation, a flag needs to be set to NOT give it out if the MAC does not match. One change and the phrase "unexpected behavior" can be removed from the document.
-
@AndyRH This is an unbound Redmine but mentions DHCP in the context of registering leases in DNS:
https://redmine.pfsense.org/issues/5413#note-49
"It's no secret that ISC DHCPD is dead. I'm exploring Kea as well...."You can make a feature request Redmine, but it sounds like they are looking to change software.
I had this conflict the other way once, an out of state client put a static IP on a switch, and didn't tell anyone, but Windows Server detected that and didn't hand out that IP...until the switch was off one day. Then the switch had an IP conflict once it turned back on. That wasn't fun to diagnose. :(
-
@SteveITS said in Come on, let us create DHCP reservations inside the pool:
I had this conflict the other way once, an out of state client put a static IP on a switch, and didn't tell anyone, but Windows Server detected that and didn't hand out that IP...until the switch was off one day. Then the switch had an IP conflict once it turned back on. That wasn't fun to diagnose. :(
Yep, real fun when a customer decides they know better than you and makes some "improvement".
-
Soon, but not yet:
-
@johnpoz we don't use PFSense at work, I use it at home.
-
@jimp said in Come on, let us create DHCP reservations inside the pool:
Soon, but not yet:
awesome! Looking forward to it
-
@CCNewb said in Come on, let us create DHCP reservations inside the pool:
I use it at home.
Well why and the heck would you need to adjust your scope for then?
as I'm having to resize my pool for the 5th+ time and shuffle IPs around.
Sounds like your just lacking when it comes to IP management to be honest.. Especially in a home setup.. Leave IPs open on the front and back for reservations.. If you need more than draw from the back end because the dhcp server starts handing out at front, or vise versa, etc.
The idea of making reservations inside a pool, seems like just pointless non feature to be honest. Anyone that has any foresight at all should leave IP on the front and back end of any network for reservations, etc. Been like this since the beginning days of dhcp, etc..
Its nice to see a new dhcpd coming, but I don't see why people complain that the reservations needs to be outside the pool.. If you had some actual need to set a reservation in the middle - then create 2 pools ;)
I actually have a very small pool for dhcp.. because as I bring a new device I let it grab dhcp, then set its reservation for the IP I want it to have.. Then have it renew - now you don't end up with shotgun IPs for your devices ;)
-
@johnpoz said in Come on, let us create DHCP reservations inside the pool:
making reservations inside a pool, seems like just pointless non feature
One scenario where it's useful is when a client installs a printer/scanner/whatever, then calls us. It's easier to make the IP permanent than try to log in to the device and set one (edit: esp. if they started using it). Just saves us time hence them money.
(and yes if we set it up we have a pattern for printer IPs...
)
