this post was submitted on 13 Jul 2023
121 points (95.5% liked)

Selfhosted

40438 readers
633 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

The question above for the most part, been reading up on it. Also want to it for learning purposes.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -1 points 1 year ago

I mean that, when IPv6 started filtering out to non-specialists, network security wasn't nearly as complex, and nor was the frequency of escalation what it is today. Back when IPv6 was new(ish), there weren't widespread botnets exploiting newly discovered vulnerabilities every week. The idea of maintaining a personal network of internet-accessible devices was reasonable. Now maintaining the security of a dozen different devices with different OSes is a full time job.

Firewalling off subnets and limitting the access to apps through a secured gateway of reverse proxies is bot bad networking. That's all a NAT is, and reducing your attack surface is good strategy.