66

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
[-] greybeard@lemmy.one 5 points 1 year ago

For work we have standards, ideally we separate VLANs by device type and firewall off their communication, but on a home network, I'd generally group by category. .1-9 network gear like switches and firewalls. .10-19 IOT. .20-29 servers & NAS. So on and so forth.

[-] Oisteink@feddit.nl 4 points 1 year ago

I see no reason to put iot devices on the same lan as my servers/home network, and I never suggest that to friends.

[-] dream_weasel@sh.itjust.works 2 points 1 year ago

So separate WiFi name or (or probably router/AP) for separate vlan?

[-] bear@slrpnk.net 1 points 1 year ago

That's what I do. All my IOT stuff that I can't get wired or via Zigbee/Z-Wave goes on a separate VLAN along with my Home Assistant server. I have an mDNS repeater for ease of access to TV stuff via apps (might spin TVs off into its own VLAN, just haven't gotten around to it) but a 1-way firewall rule that only allows the main network to initiate connections. Certain devices which don't need internet at all get static IPs and completely firewalled.

load more comments (1 replies)
load more comments (1 replies)
load more comments (2 replies)
this post was submitted on 20 Aug 2023
66 points (92.3% liked)

Selfhosted

40415 readers
230 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