this post was submitted on 11 May 2026
59 points (96.8% liked)

Selfhosted

60526 readers
1367 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
59
What does your IPv6 setup look like? (feddit.org)
submitted 1 month ago by marius@feddit.org to c/selfhosted@lemmy.world
60 comments fedilink hide all child comments
 

except for nor using it at all, of course.

So I want to make my homelab IPv6 ready, because I have too much free time, i guess. There are two decisions that I'm currently unsure about:

  1. ULA or not. Do you have local only addresses or do your clients communicate using the global IPv6 address? Does not using ULAs work without a static IP from the ISP?
  2. DHCPv6 or is SLAAC enough?

For each question both options seem to be possible and I'm interested in your experience

Cheers

you are viewing a single comment's thread
view the rest of the comments
[–] tburkhol@slrpnk.net 8 points 1 month ago (1 children)

My setup is a pile of kludges built on top of each other over the last two decades.

I started with ULAs distributed through DHCP, connected to named, which allows hosts do declare their own name and let me access local services as though I had a real domain.

My ISP eventually started supporting IPV6, but only assigned /128, so the ULAs got NAT-6ed out to the real world.

I eventually learned how to request prefix delegation from the ISP and set up SLAAC.

So now, my PIv6 clients have a) their link-local address, b) the ULA, c) a "privacy" SLAAC, and d) a unique SLAAC. All my internal services still refer to the ULAs.

I don't think I'd recommend this system for someone setting up from scratch. The easiest thing would be to go with SLAAC, if you can get prefix delegation, and set your DNS/pihole to send the unique-SLAAC address of any servers you run.

[–] felbane@lemmy.world 8 points 1 month ago (1 children)

My ISP eventually started supporting IPV6, but only assigned /128

This is hilarious to me.

"We've got 7.9 septillion addresses to play with in each of our v6/32 LIR allocations... if we follow the standard and give each customer a whole network prefix, that caps us at 4 billion customers per LIR! Nonsense, let's just give every household a single v6 address."

It's like these people don't understand what IPv6 is for.

[–] vividspecter@aussie.zone 1 points 1 month ago

Almost as annoying is if they give you a single /64. Here's an absurd amount of IPs but you only get one subnet. Thankfully, I've had nothing smaller than a /56.