Doing static IPs in the device itself and managing them (and changing them if necessary) is definitely adding several layers of complexity.I'm not sure how I would be interfering with the DHCP server. It has a pool of addresses from 192.168.1.100 to 192.168.1.200. I assign any/all static addresses from 192.168.1.2 to 192.168.1.99. For a home network, both of these ranges are more than sufficient in size.
Using a 3rd party device to "assign" static IP's never sat well with me. Doing it based on MAC address is just an added layer of complexity for no apparent reason.
DHCP is reliable and well known, and you are currently using it. All you would be doing is earmarking a couple of devices that should get the same address every time.
You can do as you please, of course, but your reasons for doing what you are doing are specious at best.
The only issue is, as you have noted, that the supplied router may not support DHCP in the manner you require. I had the same problem with mine in that it can only manage a list of eight devices that should have fixed IPs. The solution is to turn off DHCP in the router and use a different host for DHCP. In my case I am running Pi-hole on another Raspberry Pi, so I turned on its DHCP service, which is super easy to administer through the Pi-hole web interface.
Statistics: Posted by ame — Wed May 01, 2024 12:07 am