Comment on Issues with Immich
SatanClaus@lemmy.dbzer0.com 2 months agoThis is my guess. Always set static in the device and in your router settings.
Comment on Issues with Immich
SatanClaus@lemmy.dbzer0.com 2 months agoThis is my guess. Always set static in the device and in your router settings.
gray@pawb.social 2 months ago
don’t do this, use DHCP reservations instead so you actually have a list of what all your servers are and most routers register hostnames in DNS for you which is even better.
SatanClaus@lemmy.dbzer0.com 2 months ago
Confused what you mean.? I have a range of IPs for my servers and such IE 192.168.2.2-12. And then the DHCP pool 192.168.2.13-xxx. I set the servers IP static on its OS. And then set a static in my routers settings for the same IP I set in the OS. What is it that I would be doing incorrect in this setup?
gray@pawb.social 2 months ago
Instead of doing a manual action in two different places and having to keep them in sync, just do it once on the DHCP server. Setting a static IP on the server is superfluous.
ShellMonkey@lemmy.socdojo.com 2 months ago
While handy on a personal net, on a larger corporate net this isn’t practical and even adds a security risk. By having servers request leases you run the chance that someone gets into a segment, funds the ARP association for an IP/MAC combo and can take over a server’s spot simply by spoofing their own MAC to match at the time of lease renewal.
In the post above about setting a static address in two spots that in itself isn’t required either. So long as there are no duplicates you would just set the static address on the end device, then the network will sort it out with ARP ‘who has’ requests in local segments, or routing in the case of distinct subnets.