Do you use dhcp reservations?
-
I don't currently use any DHCP reservations in my home network. I have a carved out block of IP addresses where I place static IP assignments for a few servers (virtual machines and two ESXi hosts). I use static IPs when configuring those machines.
I do manage the firewall for a local church (SG-6100 appliance) and have some DHCP reservations configured there for a pair of label printers for the nursery. They print labels to "tag the kids with" on Sunday mornings .
For my home network, I currently use DHCP on my Windows domain controller. Would like to eventually retire that and use pfSense exclusively, but really want the dynamic DNS update feature of the DHCP server to work better (not the current "restart the service with each lease renewal" method used now). Hopefully Kea offers opportunity for finally fixing that quirk once Kea is fully fleshed out in pfSense.
-
Poll seems 7 to yes 0 - 0 by when I voted.
Yes we do use reservations. For everything. Only known Macs are allowed to connect to networks.
There is one network without reservations, the gust network.Now-a-days there are devices that cloak their real MAC address, so sometimes what we do when a new device is introduced to the home network (we don't exchange phones that much) we temporarily allow any client to connect, then make the reservation.
-
I only use static when I have to, gateway, Proxmox, Piholes.
Anything that I care about the address is a DHCP reservation, such as AP, computers, servers, cameras.
Other is just DHCP, I do not care what IP a phone has. The DHCP scope is small, I think it is 30 addresses.
VLAN666 (Alexia) is isolated and is straight DHCP, I don't manage the evil network... -
@AndyRH said in Do you use dhcp reservations?:
I only use static when I have to, gateway, Proxmox, Piholes.
Anything that I care about the address is a DHCP reservation, such as AP, computers, servers, cameras.Not trying to be argumentative, and don't want to start a war ... just asking why choose reservation over static when you want a given device to have a given IP.
To me, it is easier in such situations to use a static IP assignment. That way, should I replace the physical device, I simply configure it with the same static IP.
If I use a reservation, I have to find the new MAC address for the replacement device, then go edit the DHCP reservation, then either reboot the device or renew its lease so it picks up the proper IP address. It just seems like extra work. Carving out a section of the IP space for static assignments seems easier. For example, in a /24 netblock I might carve out .1 through .29 for static assignments (more or less depending on anticipated needs). And in the DHCP configuration in pfSense, you can't assign a reservation from your DHCP scope anyway. It must be a separate IP address not covered in the active DHCP scope pool. At least in Windows you can arbitrarily choose any IP within the scope to be a DHCP reservation.
-
@bmeeks No war needed. If I change PiHoles, which has happened, I update DHCP and the changes are propagated. Same thing with NTP.
When I changed physical firewalls, it was great. I just put in the new settings and waited a day then turned off the old one.
Either way is valid. -
@bmeeks said in Do you use dhcp reservations?:
just asking why choose reservation over static when you want a given device to have a given IP
Mind elaborating the difference between "reservation" and "static" in your perspective. afaik there is none.
-
@AndyRH said in Do you use dhcp reservations?:
@bmeeks No war needed. If I change PiHoles, which has happened, I update DHCP and the changes are propagated. Same thing with NTP.
When I changed physical firewalls, it was great. I just put in the new settings and waited a day then turned off the old one.
Either way is valid.Agree that either way is valid. It is a lot based on personal preference.
I came from a Fortune 500 network environment where we managed probably 50,000 devices or more (nearly 30,000 of those were employee desktop PCs and laptops). We made extensive use of Windows DHCP dynamic DNS updates to register those employee devices so the internal Help Desk could find them quickly by name instead of having to talk the user through identifying the particular IP address they had at the moment. We named the devices using a variation of the employee's network login ID.
We also used small static IP blocks carved out of the various IP subnets. In those static blocks is where we put things like core switches, network closet switch stacks, and most servers.
-
@maverickws said in Do you use dhcp reservations?:
@bmeeks said in Do you use dhcp reservations?:
just asking why choose reservation over static when you want a given device to have a given IP
Mind elaborating the difference between "reservation" and "static" in your perspective. afaik there is none.
Reservation is a DHCP construct based off of the client's MAC address. So anytime the hardware changes (new device or replace the network card), the MAC changes and you need to edit the reservation in the DHCP server. With static IP, I simply type in the desired IP address in the client's network setup screen. Both yield the same end result -- a given client gets a particular fixed IP address. What's different is exactly how you get there (at least that's how I define it).
-
@bmeeks I don't think it was ever discussed in this topic "client-side configurations".
Truth be told, there is no reference on the pfSense software to DHCP Reservations (may be wrong but I really don't think there are).
When you go to DHCP Server you have an option to add a static entry. I believe it's a colloquialism where people are using reservation instead of static entry. You can't add "reservations" on pfSense, at least not by that nomenclature. -
@maverickws said in Do you use dhcp reservations?:
@bmeeks I don't think it was ever discussed in this topic "client-side configurations".
Truth be told, there is no reference on the pfSense software to DHCP Reservations (may be wrong but I really don't think there are).
When you go to DHCP Server you have an option to add a static entry. I believe it's a colloquialism where people are using reservation instead of static entry.The wording can be confusing. I like to think of it as a reservation because you are reserving that IP address in the mind of the DHCP server, but only for a client whose MAC address matches the one you enter in the static assignment setup.
The other way, when I say "static", is on the actual client device I configure the network for "static IP" and not DHCP, and I manually type in the address and subnet I want that client to use. I realize that in the world of IoT, there may be devices that can only do DHCP, and if that is the case then you would need to use the DHCP reservation route to have a known, fixed IP address on the device.
So, to clarify, when I say "reservation" I am thinking of an entry in the DHCP server's configuration where I link a particular MAC address with a particular IP address. When I say "static", I am thinking of the situation where the client device is NOT using DHCP and I instead enter the IP information directly into the client manually. Been doing this sort of thing for a little over 40 years, and that's just the way I learned way back when.
-
Yep. Been using them for a long time on the home network.
Makes it very easy to distingush "normal" devices from guests.
Since pretty much everything defaults to doing DHCP you wind up managing everything from a single place. -
@bmeeks got it.
I figured it was just some nuance of speech but wanted to clear it out just to make sure. Personally I most times call them "static mappings" or "arp mappings".Also I believe there is a situation here, if I'm wrong please someone correct me but
pfSense allows a static mapping from many to one. This is, you can have several static entries using different MACs and the same IP address.
Now I am not sure because I hardly ever selected this option, but I figure when you select the option to have that
ARP Table Static Entry maybe then it is a reservation? Again, not sure on this one.
But in the true concept of the term, as it allows several entries for the same IP, it hardly ever is a reservation.
Also, by the way pfSense works, static mappings only exist outside the DHCP dynamic range, so an IP on the range "static" wouldn't go to the dynamic attributions. -
I use it, even with IPv6.
(One person doesn't like this) -
I don't use reservations at home or at the office. For me the only benefit would be easier renumbering, and that's something I haven't needed to do in the 20+ years I've been at this company. I report directly to the owners and they want to be able to do whatever they want when they want including weekends and evenings when I'm not around. I appreciate the security aspects but the owners don't like security getting in the way of their convenience.
-
@johnpoz
Yes, I rely heavily on DHCP reservations for firewall rules and grouping of similar devices..Does Kea DHCP not allow for static mappings?
-
@bmeeks said in Do you use dhcp reservations?:
To me, it is easier in such situations to use a static IP assignment....
Maybe in some cases. However, many dumb IOT devices are 'hardwired' for DHCP.
-
Yes I use lot of DHCP Static Mappings all over my VLAN's :)
-
@azdeltawye said in Do you use dhcp reservations?:
Does Kea DHCP not allow for static mappings?
It does, but does not register them in unbound for dns as of yet.
-
Yes, for all my home VLANs except the Guest one.
-
@maverickws said in Do you use dhcp reservations?:
Personally I most times call them "static mappings" or "arp mappings".
Why I called it out and hope make clear what I was talking about.. The static mapping term seems to be newer wording.. Us old farts, at least in my part of the world use reservation - because that is what they are, they are reservation for that mac to get this specific IP.. Kind of like when you make a reservation at a restraunt for table by the window..
But maybe it also just regions of the world use different terms?
That is another thing that is curious ;) maybe I could start another poll - hehehe
static mapping and arp mapping don't make a lot sense to me... Because that is not what it is, its a "reservation" on the dhcp server to give client X ip Y..
And unlike the Seinfeld episode, a dhcp server normally knows how to hold a reservation ;)