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!
view the rest of the comments
I run double firewalls.
I just don't fully trust the ISP router, so I disabled the wifi and hooked it up to my own router. If the ISP router gets hacked, my internal network doesn't get exposed.
Port forwarding is a bit harder, but you probably aren't even doing that at all (and it still works anyway, it's just an extra step).
That's an interesting idea. How do you access the router connected to the ISP to setup port forwarding to your second router? If it's too complicated to type out here, I'll understand.
The easiest way would be to just bridge the ISP router if it supports that feature. To connect back to the ISP router's webui you can setup outbound NAT on your second router (generally only available on enterprise gear). Don't double NAT unless there's no other option.
If you can bridge, the sky's the limit in terms of what gear you can have on the backend. My bridged modem is directly connected to a L3 switch which links to my Proxmox cluster, and my Opnsense router exists virtually in the cluster and can be migrated freely between the machines.
Your setup sounds very interesting to me. If I wasn't so obsessed with writing code, I would have been deep into hardware. I imagine that it will become a hobby of mine when I hit my midlife crisis. I'll be buying up all kinds of hardware, quiting my job, and connecting everything to everything.
Homelabbing is an amazing hobby if you're into this stuff, and you can go as far down the rabbit hole as you like :)
My lab also supports my coding endeavors since I can deploy VMs, run a local Git server, and so forth. Most of my development is done in a SPICE VDI on Proxmox.