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.
Something to consider about all of the efforts to sustain #IPv4 so far beyond its original shelf life. #NAT and #IPv6 were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.
This brings us to #platforms. It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.
Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?
@ipv6dad The biggest problem with "backward compatibility" I see is at the application layer. If my code still calls gethostbyname() and tries to open sockets as AF_INET, that will fail in an IPv6-only environment. This is why CLAT exists.
The hope was giving the app devs yet another crutch would give admins time to set up the missing v6 infrastructure _and_ the app devs time to port their code. Instead large numbers of those folk are saying "My stuff still works, why mess with it?" This ignores the effort needed to maintain the PLATs as well as the operating systems that still don't have CLAT (Windows 11 only just got it this year).
So at what point do we say "Enough backward compatibility. Write modern code. Deploy modern networks." ? Yes, IPv6 is different, but how long do you need to learn it? Why are we still teaching the old stuff in schools except as a historical footnote? The first IPv6 RFC was released >25 years ago.
boostedNew post: Part 4 of running my own AS.
A direct BGP session with Hetzner on FogIXP, a fourth FreeBSD edge in Zürich, and a MikroTik at home speaking iBGP into the /48 - so my home LAN now has provider-independent IPv6 and exits AS201379 like any other site.
Plus a two-condition route-map that steers DTAG-bound traffic over Vultr.
I like the idea of global anycast NAT64 gateways.
Maybe we shouldn't invent another prefix for it.
https://datatracker.ietf.org/doc/draft-matolin-global-nat64-anycast/
That one?
https://www.google.com/intl/en/ipv6/statistics.html
#IPv6 first time >50% by Google statistics
Yet another notebook of mine is now properly reachable via DNS. I am currently sitting in front and working on nb2.ge.nau.so, feel free to ping it! #ipv6 #fun #becauseican #alsogoodforfindingstuffwhenyouareontheroadunsavedonyourmachine
AWS Elastic Disaster Recovery now supports IPv6
Posted on: Apr 13, 2026
AWS Elastic Disaster Recovery (AWS DRS) now supports IPv6 for both data replication and control plane connections. Customers operating in IPv6-only or dual-stack network environments can now configure AWS DRS to replicate using IPv6, eliminating the need for IPv4 addresses in their disaster recovery setup.
https://aws.amazon.com/about-aws/whats-new/2026/04/aws-elastic-disaster-recovery-ipv6/
It seems like the peer to peer aspect of IPv6 may offer a way to thwart some of these age requirements. There's no central authority in control. There's not silver bullet but if we're forced into civil disobedience this is an avenue to investigate.
@mayintoronto Is 5 minutes meant to be the upper or lower bound? 😁
For me that would be Internet architecture, specifically #ipv6 .
@N2DYI Good to see #IPv6 is on the roadmap. I look forward to testing that out.
Nice to see more folk talking about wideband audio. I wrote a bit about it some years back [https://www.nivex.net/ham-dvhd/]. The linked paper from Polycom is especially convincing. I got into a discussion with the repeater guy at one of the local club meetings, but he had done his whole career in telecom and was not going to budge on needing to go above 4KHz audio.
Opus would be useful even with the lower audio bandwidth. The network savings of both the lower base bitrate and it being a variable bitrate codec, encoding silence at next to nothing, would be a gain on constrained links.
I had forgotten about the extra hoops Asterisk makes you go through to get Opus, as it's labeled an "external" codec. Back when Debian still packaged it, they included it as an additional package in the repo. I still think it would be nice if ASL would tick the box in the build process to include the module so we could at least try it out.
#IPv6 test as as German Telefonica roaming customer in the Belgian "Orange" network: [insert sad face here]
how do i convince Alpine Linux that it doesn't have IPv4 connectivity? when i run e.g. "ping bbc.co.uk", it picks the IPv4 address first, even though it doesn't have a default route.
i can't disable IPv4 because i need it for Wireguard.
i can't use /etc/gai.conf because musl libc doesn't support that.
this makes e.g. apk very slow because it waits for IPv4 to time out before it tries IPv6. i don't understand why it doesn't immediately get "no route to host" over IPv4...
any ideas?
AWS Transfer Family now supports IPv6 for connectors and web apps
Posted on: Apr 7, 2026
https://aws.amazon.com/about-aws/whats-new/2026/04/aws-transfer-family-ipv6-connectors-web-apps/
🎉 Look, it's 2026 and we're still banging on about #IPv6 like it's the second coming! 🤣 Apparently, the entire internet is going to collapse under the weight of #NAT unless we make the switch to IPv6, because hosting your website from your mom's basement was the pinnacle of #innovation. 🙄
https://ankshilp.in/posts/for-the-love-of-internet/ #InternetCollapse #HackerNews #ngated
I hate, that I have to explain again and again that EUI64 address generation is the worst feature of #IPv6 in terms of tracking and privacy.
Nevertheless nearly all #IoT devices us #lwIP which lacks RFC7217 or RFC4941/8981 support and leaks GUIDs to everyone listening.
When is everyone taking this serious?
Even a famous German CPE vendor uses this method.
Have a look here if you do not understand what I mean:
DAD works, but nothing more.
Or in other words: At the moment it is not possible to use more than one Windows-PC with IPv6-mostly-support (Preview only ) in a IPv6-mostly or IPv6-only Network.
By accident a host may use one of the other mapped IPv4 addresses (out of 192.0.0.0/29) . But in general it takes the first one anywhere.
and W.B. is right: MS has to fix that problem before it gets released for the masses
RE: https://ipv6.social/@goetz/116341020777057706
Linux is getting "modern"! #ipv6
@nico first patch series for #LegacyIP deprecation in the kernel merged to net-next:
https://lore.kernel.org/all/20260401172400.41df7edf@kernel.org/#t
Amazon ElastiCache Serverless now supports IPv6 and dual stack connectivity
Posted on: Apr 2, 2026
https://aws.amazon.com/about-aws/whats-new/2026/04/amazon-elasticache-serverless-ipv6-dual-stack/
Falls jemand in München und Umgebung (habe d-ticket) einen Rechner mit dem Betakanal des Windows-Insider-Programm am Laufen hat, ich wäre über einen CLAT Test (via WLAN) mit zwei Rechnern sehr erfreut. Ein mobiler IPv6-mostly Hotspot und mein Rechner stehen zur Verfügung.
Bitte privat antworten.
Nach dem Vortrag von Wilhelm Boeddinghaus zu CLAT für Windows auf dem Berliner Adminstammtisch stellt sich mir jetzt die Frage, wo nehme ich 9 Windows11-Kisten mit aktivierten Beta-Insider-Preview her?
#ipv6only #ipv6 #clat #windows11
After the talk by Wilhelm Boeddinghaus about CLAT for Windows at the Berliner Admin Stammtisch I am wondering how to get 9 windows 11 boxes with beta-insider-preview?
Ah, nothing screams "forward-thinking tech" like cutting-edge patches to ditch "legacy" IPv4 in favor of shiny #IPv6. 🦖✨ Because, who needs a robust, globally functional internet protocol when you can gamble on an IPv6-only utopia? 😅 #LivingOnTheEdge
https://www.phoronix.com/news/Linux-IPv6-IPv4-Legacy-Knobs #forwardthinkingtech #legacyprotocol #internetinnovation #techtrends #HackerNews #ngated