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
Yes, it's not the same, but it can be used to bridge private addresses onto a public network, which is basically what NAT is trying to achieve. If you're running an ISP and don't want customers to be directly accessible from the internet, it seems reasonable. In an ISP setup, you would issue private net addresses and just not do the translation if the customer doesn't pay.
Yes, you can achieve the same thing another way, but I could see them deciding to issue private net addresses so customers don't expect public routing without paying, whereas issuing regular public IPv6 addresses makes it clear that the block is entirely artificial.
Just because you can doesn't mean anyone does. I've never seen an ISP hand out "private" IPv6 addresses. Ever.
If you're doing NAT on IPv6, you're doing it wrong and stupid. Plain and simple.