this post was submitted on 20 Aug 2023
67 points (92.4% liked)

Selfhosted

40183 readers
128 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
 

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
[–] Faceman2K23@discuss.tchncs.de 1 points 1 year ago

I have a few vlan subnets, one for IOT devices (smart junk, automation, media players etc), one for general LAN devices (mostly computers, NAS etc), one for VMs and other services and one for guest access. all with their own fairly simple firewall rules to eachother and to the web. there are also matching Wifi networks for IOT, Main and Guest that are on those Vlans.

As for DHCP, I tend to set the DHCP ranges for xxx.100 - xxx.254 and anything below 100 is for static allocations. all in standard 192.168.x.x ranges, no need to go bigger than that. I only have IPv6 for the VMs for testing cause i'm still learning how to use that properly and safely.