this post was submitted on 18 Jun 2024
360 points (98.6% liked)

Selfhosted

40329 readers
419 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] skittlebrau@lemmy.world 22 points 5 months ago* (last edited 5 months ago) (17 children)

Each year I seem to think “this will be the year I set up IPv6 in my homelab” - but then I never get around to it.

If I have to run both v4 and v6 concurrently, there isn’t much incentive/motivation for me to use v6 locally.

Maybe I’ll get around to it when there’s a net benefit for me for my use case, or when I’m forced to.

Am I just imagining it to be more complicated than it actually is?

My router runs pfsense and I have 6 VLANs each with its own subnet - Management, Trusted, IoT, Cameras, Guest, and Web Facing Servers.

[–] Album@lemmy.ca 10 points 5 months ago (13 children)

It's honestly super simple to set up. Outside of your ISP config it's almost all autoconfig. 100% of the complication (at least for me) comes from knowing ipv4 first for 20 years and then trying to incorrectly map those concepts to V6.

As soon as I "let go" it was fine.

There's not a huge net benefit you're right. I mostly wanted to learn and I hope to be at the front edge of disabling ipv4 in the near distant future.

[–] cmnybo@discuss.tchncs.de 3 points 5 months ago (7 children)

The benefit is being able to easily access devices from the internet. The same address works on the LAN and WAN. There's no port forwarding, so multiple devices can have the same port open. You also don't need to mess with a VPN if your IPv4 connection uses CGNAT.

[–] Album@lemmy.ca 2 points 5 months ago (2 children)

Yeah dropping Nat is the biggest net benefit I agree but I think the avg person won't really find that much value in it when Nat works ok

[–] Auli@lemmy.ca 2 points 5 months ago (1 children)

And the average person is going to be using it without knowing. And never complain or anything.

[–] Album@lemmy.ca 1 points 5 months ago

Yea, prolly already using it.

[–] cmnybo@discuss.tchncs.de 1 points 5 months ago (2 children)

NAT works fine until you get stuck on CGNAT and can't host anything on IPv4 without using a VPN.

[–] Album@lemmy.ca 1 points 5 months ago (1 children)

I thankfully have never had the misfortune of cgnat

[–] deadbeef79000@lemmy.nz 2 points 5 months ago

Yet.

As IPv4 blocks get scarcer and ISP's get more customers, they'll all eventually have to move to IPv4 CGNAT.

And that's completely fine for most people.

If you're not one of those people, then IPv6 is your saviour.

[–] Tja@programming.dev 1 points 5 months ago

Meh, nothing a VPN and a 3 bucks a month VPS can't solve...

yells at cloud in IPv4

load more comments (4 replies)
load more comments (9 replies)
load more comments (12 replies)