DHCP reservation inside existing pool
-
I need to set a dhcp reservation inside of an existing pool.
I cannot split the range, as there are existing clients with addresses. I require a dhcp reservation for an existing workload that runs k8's, and that k8's workload is currently offline because the L4/KubeVIP is offline (Tanzu k8's ties a previously leased address to the kubevip certificate via IP) - I need this system to come up with the previously leased address.
can someone point me to the php file inside pfsense to override the UI that does not allow me to set a res inside the pool?
-
@rmac1813 Can you make a range that is, say, .2 to .39, and add an additional pool that is .41 to .99, then use .40 for your reservation?
ref: https://docs.netgate.com/pfsense/en/latest/services/dhcp/mappings-in-pools.html
-
@steveits said in DHCP reservation inside existing pool:
https://docs.netgate.com/pfsense/en/latest/services/dhcp/mappings-in-pools.html
I cannot. the range must stay in tact as it is. there are active client leases, preventing the range from changing.
The problem here is that a machine leased an address, then was turned off, then came back online with a different address in the range. - the previous IP was leased out to another client. This machine that now has a different address is in a broken state (kubevip) - i can kick the client off but I need to force pfsense to lease the address to the broken control-plane (kubevip) node.
I just need to override the gui. I read there is a php file that can allow this.
-
@rmac1813 said in DHCP reservation inside existing pool:
I cannot split the range, as there are existing clients with addresses.
Why can't you? You just change the pool and, if necessary, add additional pools? After that's done, any device will get an appropriate address at the next renew.
-
????
DHCP was designed to allow for that. A device normally tries to get the previous address but, if necessary, be assigned a new one. It should never try to come up on a previous address that's occupied by a different device.
What you can do is play with the lease time, so that they get short leases and then, perhaps off hours, change your pool, first expanding and then shrinking as needed to move the pool.
-
@rmac1813 said in DHCP reservation inside existing pool:
the range must stay in tact as it is. there are active client leases, preventing the range from changing.
Not sure where you got that idea from to be honest.. This has never been a thing..
Lets say I had a pool of .100 - 200
And clients have say .100, .101, .103, etc.. Then I change the pool to be .150-250..
Clients that try and renew their .100 address will not get a renew, they would either than do a discover and get a new IP, or when their lease actually expires they would do discover and get an IP from the new pool.
The advantage of dhcp is this, I can change up the pool, I could even change the whole network from say 192.168.1.0/24 to 192.168.2.0/24 and automagically devices would move to the new range, etc.. I could set a vip on the old 192.168.1. address so that stuff continues to work with the old range until they are all moved over, etc..
You can for sure split your pool into 2 pools, leaving IPs out of the new pools to assign specific devices to those IPs via reservations.
