view the rest of the comments
Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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.
I see no reason to put iot devices on the same lan as my servers/home network, and I never suggest that to friends.
So separate WiFi name or (or probably router/AP) for separate vlan?
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.