this post was submitted on 20 Aug 2023
72 points (92.9% liked)

Selfhosted

40408 readers
214 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 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
72
How do you organize your DHCP clients? (self.selfhosted)
submitted 1 year ago by DrakeRichards to c/selfhosted
51 comments fedilink hide all child comments
 

I’m setting up DHCP reservations on my home network and came up with a simple schema to identify devices: .100 is for desktops, .200 for mobiles, .010 for my devices, .020 for my wife’s, and so on. Does anyone else use schemas like this? I’ve also got .local DNS names for each device, but having a consistent schema feels nice to be able to quickly identify devices by their IPs.

you are viewing a single comment's thread
view the rest of the comments
[–] DrakeRichards 2 points 1 year ago (2 children)

A couple dozen devices maybe. I don’t really need dedicated ranges, but it’s nice to know exactly which device I’m looking at just by the IP when reading logs.

[–] [email protected] 1 points 1 year ago

Checking logs is perhaps the only real reason I can see for reserved ip-s. But then again you can do reverse lookups - and like I said in another reply ipv6 is dynamic by nature, so any device will only stay on the same ip for the configured amount of time.
You might not know, but several of your devices might already be communicating using ipv6 on your home network. Both windows and iOS will use link (osi layer 2) local IPv6 and mdns for discovery and communication. This is not true if your switch denies IPv6 but you’d need a level 2 switch or some way to block IPv6 multicast for that.

[–] [email protected] 1 points 1 year ago (1 children)

I'm not saying in anyway that what you're doing is in anyway wrong. It's good that you're thinking the way you are. Just saying, if you're in this frame of mind now, it's a good time to look at vlans. Think dedicated ranges with the benefit of reduced traffic saturation.

[–] [email protected] 3 points 1 year ago (1 children)

I don’t see how VLANs would help OP.

[–] [email protected] 0 points 1 year ago

I didn't say they would. I said it's a good time to learn.