this post was submitted on 10 Apr 2026
54 points (98.2% liked)

Selfhosted

58417 readers
832 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hey there selfhosted community.

I had big plans when I moved last year to finally setup my homelab with proper VLAN seperation. Well a stressfull move later I simply had no energy left and just threw my whole homelab and all my services in my main LAN with no seperation whatsoever.

In how much of a world of pain am I in now when I want to switch my homelab services over in a seperate VLAN? Any recomendations or pointers to documentation for me to go through before I decide if this is something I want to do right now?

Currently this would impact a proxmox host with 3 VM's and 1 LXC and around 20 docker images.

you are viewing a single comment's thread
view the rest of the comments
[–] CompactFlax@discuss.tchncs.de 7 points 1 day ago* (last edited 1 day ago) (2 children)

First ask yourself what benefit you gain from isolating services.

Untrustworthy devices like work computers, smart TVs, and IoT sure have good reasons. Possibly a DMZ. But you might do as well to simply block all egress from a few internal IPs instead.

Move things slowly, because you’ll need to see what traffic needs to flow and what doesn’t, and you may find that you need some helper services for cross vlan (for example mDNS).

ETA: guest wifi is good too; force the traffic through firewall and keep it off your internal network

[–] possiblylinux127@lemmy.zip 1 points 1 day ago

Don't block IPs as it provides fairly weak security.

[–] SupraMario@lemmy.world 2 points 1 day ago

This is the correct answer. Unless you're just wanting to learn networking. Blocking outbound on shit that doesn't need it, and having a dmz if you're really really wanting to host outside of your environment is the best way. If someone is in your environment, vlans aren't going to stop them.