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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
Is there a technical advantage to using a 192 network vs a 10 network like you described? I would've thought they're just addresses, still IPv4 as well.
I tend to use hostnames where possible. Maybe that's not viable for your situation?
No. But segregation into vlans has advantages. As this comes with new adresses anyway, might as well tidy up the adress space entirely.
In the end 10.20.20.10 feels much neater than 192.168.174.10.
But yes, you are right, technically the 192.168.xx.yy adress space works the same and has plenty of space for home use.
Going back a little bit, you mentioned advantages to "segregating into vlans"?
Would you like to elaborate on some of those advantages?
I am certainly not an expert by any stretch. But here are my reasons: Ability to isolate some “sketchy” IOT devices into an IOT only vlan, where they are not allowed to access the rest of the network, only the internet and incoming traffic from the other vlans. Having a “clean” vlan/subnet for servers and services where I can give out static IPs without worrying about collisions with client devices
Ah, nice. Very cool, very reasonable.
And you can do this all with a consumer grade router maybe? Or do you need to have like a small PC-like device running special software that acts like a router, that handles this?
I have a Unifi router (Unifi cloud Gateway Fiber to be precise), which one you could argue is on the higher end of consumer hardware. But there are also more consumer oriented routers with that capability.
Cool, thank you so much for the info, mate!
Ah okay, so it's kinda just for aesthetic reasons mostly? I'll take that explanation home any day 😄
Exactly. You could say it was unnecessary, but I think we have crossed that line a long time ago.
😁 "Maaaybe"