cablespaghetti.dev is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
@Tubsta They "ISP"s applied the logic of dynamic IPv4 assignments via PPPoE to #IPv6. Thats why we have #RFC9096
Secondly there was a recommendation to give customers the option to get a new prefix delegation easily or on request. -> Every redial, because easy.
Thirdly privacy concerns.
Lastly business decision -> static assignment = business contract/product
Remember when in December I had a bit of a debug session why I couldn't reach my monitoring server via #IPv6 from a DTAG internet line?
Well, this later motivated @domi to dig a bit deeper and it ended up with @q3k sending some emails to EPIX, DTAG and Lumen about it, as it was obviously a bigger issue of an entire /32 IPv6 prefix from Lumen not being accepted by DTAG.
The issue ended up being escalated multiple times and it seemed to take them quite a while to figure out what was wrong.
But as of today (or recently, today is when I got note of it), it works!
DTAG now accepts the 2a0d:eb00::/32 prefix, which they previously rejected due to, supposedly, an incorrectly documented Lumen AS-SET in the RIPE DB.
This is certainly not the escalation I expected after I connect to my server back then 
OK, so, turns out my weird #IPv6 problem wasn't a weird IPv6 problem afterall. It was a weird #thunderbird problem. I deleted all it's config and cache on one machine, reconfigured my account details in a fresh new profile and the problem seems to be gone.
What the f*ck, what kind of software does this to its users? I don't even...
Ah well, I guess it's now usable again. Except I need to spend some time restoring all settings and accounts etc. And do the same on the other machines where I use thunderbird.
#IPv6 was defined in RFC1883 in December of 1995.
That's right, IPv6 is now *30* frickin' years old. I've spent at least 25 of those yelling at people, companies, service providers, and many engineers who really should know better that they need to enable it.
Doesn't look like 2026 is going to change that. Le sigh.
I have this weird #IPv6 problem and it's driving me crazy.
So, hear me out.
I have a #wireguard tunnel set up to a VPS because my ISP doesn't offer IPv6. So all IPv6 traffic is routed over the tunnel. Obviously, this means the MTU should be reduced, so I've configured radvd to broadcast an MTU of 1420.
All fine. IPv6 works. I can visit websites, stream audio and video, ssh all over the place, all over IPv6.
Except for #thunderbird. It'll take ages trying to send an email, then complain the server timed out. It'll be unable to save drafts or sent mail to the imap server, complaining about server timeouts.
So I try sending mail with msmtp from the same machine, all is well, no timeouts whatsoever. It's just thunderbird that's being difficult.
I've been staring at this problem for weeks now, done all sorts of tcpdumps along the path from my computer to my mail server. Double-checked that ICMP6 type 2 is passed along neatly across all firewalls involved.
It's got me stumped.
I'm not expecting anyone reading this to be able to provide a solution, I just wanted to share that it's driving me crazy!
Nice article about the nuances of IPv6 local addressing
https://blog.apnic.net/2020/05/20/getting-ipv6-private-addressing-right/
I noticed I can pull #IPv6 ratio from my AS stats. And I can only say:
Fucking #Fastly 🤬 (and no, it's not a lot of Github)
(Also I just noticed CDNEXT and CDN77 are the same network, they use a different AS for v6 for whatever reason?)
It only says "SHAME" if there was no IPv6 packet at all. If it says "0%" there was something, just too low to count.
Also, CCC (mostly media.ccc.de, but maybe also some e-mails?) delivered not a single IPv4 packet 
Well, that escalated quickly.
My primary network at home is now running IPv6-mostly. I followed this guide up until they made their own Tayga container:
https://forum.mikrotik.com/t/nat64-and-464xlat-on-ros-how-to/267046
Because it turns out there's an officially supported Tayga container for NAT64:
https://forum.mikrotik.com/t/tayga-nat64-official-support-for-routeros/267504
I added the appropriate DHCP option 108 following this thread: https://forum.mikrotik.com/t/dhcp-option-108-gets-incorrect/175831
For DNS64 I just added the bundled plugin to my CoreDNS config.
None of that was simple, but I'm kind of astonished how well it all works together. There's no reason why Mikrotik or whoever couldn't make that just happen automatically, either.
Now the next trick is to teach all of the servers how to update static DNS entries in the router so local stuff won't go through NAT64.
So, heute den Wireguardtunnel mit zwei Adressen pro Inteface (GUA+ULA) konfiguriert. Jetzt komm ich gleichzeitig ungenattet raus als auch durch das ULA-vpn-Geflecht meiner Fritzboxen.
Dieser Pluspunkt geht an wg, mit openvpn musste ich mich entscheiden - entweder GUA oder ULA.
Bleibt nur noch das hässliche Präfixupdateproblem - vor allem auf dem Client. 🤔
PS: Nachricht an mich selbst: sollte ich vielleicht öffentlich beschreiben, damit mehr IPv6-Beispiele existieren.
TIL that #simyo (mobile provider) actually supports #ipv6 on their network, but it does not seem to be enabled by default in the APN config (which lives on the SIM, right?).
This 4y old forum thread (https://forum.simyo.nl/internet-4g-en-5g-62/wat-is-de-status-van-de-ipv6-uitrol-44316) said the same, assuming it was only enabled for new customers, but I only subscribed a few months ago.
To enable ipv6 on Simyo: Settings -> Network & Internet -> SIMs -> Select SIM -> Access Point Names -> Select APN -> APN (roaming) protocol: IPV4/IPV6. Then reboot.
I don’t know much about Hytale, but I love the fact that they have a FAQ on hosting peer-to-peer games which includes suggestions for both IPv6 and Tailscale 
https://support.hytale.com/hc/en-us/articles/45324238811291-Joining-Friends
Another locked issue, no possibility of follow-up questions, and a threat:
I'm not quite sure what to say about this.
Just because you lock an issue doesn't mean you're right and my arguments count for less...
It's wrong to say that IPv6 won't be essential in 2026...
The last time I had such an issue drama was with Ansible...
https://github.com/meshtastic/Meshtastic-Android/issues/4156
https://github.com/meshtastic/Meshtastic-Android/issues/4157
https://github.com/meshtastic/Meshtastic-Android/issues/4189
https://github.com/meshtastic/Meshtastic-Android/issues/4190
@moreentropy do you know what the state is of #ipv6 only stack on the esp32? Last time I checked, the network stack required legacy IP.
My website (https://www.rainskit.com/) now works over #IPv6! And boy is my razor dull!
- VPS address delegation
- registrar glue (via support ticket)
- djbdns doesn't support v6
- djbdns v6-compatible fork won't install via pkgin with djbdns-run
- switch to (and configure) nsd
- ditto dnscache -> unbound
- configure nginx
It works!
But apparently @fastmail doesn't have IPv6 support 😿 https://www.reddit.com/r/fastmail/comments/1nvuho3/ipv6_support/
breaking news
(I have to confess apple is sometimes good)
given a #IPv6only mobile access (like the Deutsche Telekom within Germany, not during roaming)
recent apple #iOS 18.5
makes
#IPv6mostly for clients via hotspot
#dhcpoption108 as well #pref64
I made also the windows test - in case option 108 is not provided by the client, iOS provides IPv4
Von zuhause aus Dinge zu hosten, wäre so viel einfacher mit IPv6-only. Aktuell muss ich (zusätzlich!) irgendwelche IPv4-Krücken mit Portweiterleitungen konfigurieren, die nur im Ansatz was von ordentlichem Hosting haben. :-(
And as always, we value your input, see "For Upcoming PF Tutorials, We Welcome Your Questions" https://nxdomain.no/~peter/pf_tutorial_upcoming_questions_welcome.html (tracked https://bsdly.blogspot.com/2025/05/for-upcoming-pf-tutorials-we-welcome.html) #pf #firewall #tutorial #openbsd #freebsd #networking #security #ipv6 #ipv4 @stucchimax
Ohne #IPv6 !
Das ist jetzt nicht euer Ernst?
Beim ersten großen Link auf dieser Seite - zu Elster - geht es doch auch, und das schon seit Jahren!
https://www.linkedin.com/posts/nicolewajer_ipv6-ciscolive-activity-7413489510895927296-MjnL
Hitchhiker’s Guide to Troubleshooting IPv6” — a fast-paced, practical, and slightly irreverent tour through the weird, wonderful, and occasionally panic-inducing realities of IPv6 troubleshooting.
By @vlinder
#IPv6 Fundamentals Training Course
Location:
Amman, Jordan
https://www.ripe.net/training/in-person-training-courses/upcoming-training-courses/9feb26/
By @ripencc