this post was submitted on 22 Sep 2024
42 points (95.7% liked)

Selfhosted

40198 readers
727 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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] 5 points 1 month ago* (last edited 1 month ago)

Good question, and I'm curious what the experts say. Surely it depends on the software that handles DHCP.

I've always set static addresses in the DHCP address range and it has always been reserved and never assigned to other devices. I've used ASUS and MikroTik for what it's worth.

If you're the type to set static addresses on the devices themselves, then that would certainly increase the risk of a conflict if it's inside the address range.