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 might sound naive, but are you talking about a homelab that is running more than 253 separetly networked machines, virtual or otherwise? I personally am only running a dozen or so with all my Pis and VMs as everything else is just port forwarded containers on those hosts. My understanding was that ipv6 was for better public facing IPs, since on LAN ipv4 offers a few thousand IPs for private use.
Na IPv6 goes back to what ipv4 was when there isn't a public and private range. Private ranges were due to ip exhaustion. NAT is then used.
With ipv6 you subnet your Lan with ipv6 delegate range from your ISP. Basically it's like subnetting your lan with a public ipv4 range. No nat required. As a firewall is used to stop packets not NAT. Also ipv4 RFC1918 doesn't provide a few thousand for private, it provides 17 million.