Selfhosted

39435 readers

3 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Does setting/reserving a static IP via router prevent its allocation to other devices in its network? (lemm.ee)

submitted 1 month ago by [email protected] to c/[email protected]

24 comments fedilink hide all child comments

Asking for clarification as what I've read suggests yes, but is also sometimes coupled with advice to (still?) set a static IP outside of the DHCP address range as well.

Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 31 points 1 month ago (2 children)

TL;DR: it depends entirely on the DHCP server software.

Generally the safe/reliable policy is to assign a smaller DHCP range (or ranges) and allocate static assignments outside of the DHCP range(s).

Assume your network is 192.168.1.0/24.

Specify 192.168.1.128/25 for DHCP, which means all DHCP addresses will be above 192.168.1.128.

This leaves you everything below 192.168.1.127 for static assignments.

[–] [email protected] 12 points 1 month ago

I'd agree with this recommendation. I believe there were multiple occasions where my router assigned a dynamic IP the same as some other reserved IP. Hard as hell to diagnose. Key indicator was that roughly half the packets were being lost.

[–] [email protected] 6 points 1 month ago (1 children)

Appreciate the example! It's when handling a DHCP range and the related CIDR notation that I tend to get especially muddled in this area. It certainly doesn't help that each router's interface and terminology tends to vary just enough to add uncertainty.

Regardless, the comments here and more focus on this have helped clear some of this up for me.

[–] [email protected] 4 points 1 month ago

I still double-check my CIDR's/netmasks and expected ranges with a tool (some online one or other). Easier to avoid silly mistakes or typo's