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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
view the rest of the comments
FWIW, I use the VLAN approach. I have a VLAN (101) specifically for IoT shit. The firewall allows devices on other VLANs - general purpose (104), infrastructure (102) and servers (103) to connect in to 101, but nothing can reach out. Works seamlessly. The only issue you might bump into is that some devices use UPnP/mDNS for discovery, but OpenWRT has a proxy module you can install to facilitate that.
You may be wondering why the tags I use for my VLANs are so odd. I also wonder that sometimes.
Are those also the aame subnet or in different network (e.g. 192.168.101.0/24 and 192.168.104.0/24)?
Different subnets, similar to how you describe. It would be really tricky to have them on the same subnet, especially if you want a firewall between them.