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.
#Fediverse
I checked 4160 fediverse instances for their connectivity.
- A / AAAA record persent
- Reachabliltiy over #IPv6 if AAAA present.
107 Instances announce AAAA records but have broken inbound IPv6
2141 are #DualStack and have working inbound #IPv6
Way to go.
Geringer Fortschritt mit einer quick&dirty Lösung - und noch immer Beantragung notwendig.
"Der IPv6-Zugriff muss über den STACKIT-Support angefordert werden. Bitte öffnen Sie ein Support-Ticket mit dem Titel „NAT64“ oder „IPv6-Zugriff“ und geben Sie alle IPv4-Adressen aus Ihren Projekten an, die für den IPv6-Zugriff aktiviert werden müssen."
I resisted setting up TURN because both I and the person I called for the test are using IPv6, so we shouldn't need any NAT traversal. Once connected I checked the packet flow and of course it's using IPv4 through the relay. I don't know for certain where the fault is yet, though I'm inclined to think it's with Conversations given it actively resisted using #IPv6 for the XMPP connection until I forced the issue with SRV priorities.
Installer improvements
The installer (setup-alpine) now supports the Limine boot loader and has gained #IPv6 support. When installing from a serial console, the boot loader and kernel will automatically be configured with serial console support, making headless setups smoother.
https://www.alpinelinux.org/posts/Alpine-3.24.0-released.html
Je fais une formation #IPv6 demain et après-demain. Qu'est-ce qui vous semble les choses RÉCENTES les plus intéressantes dans le monde IPv6 ?
I keep flipping between enabling and disabling #IPv6. Last issue encountered yesterday, in fact, when Youtube playback getting stuck… on a symmetric gigabit connection. Happened many times before too.
I don't get native IPv6, it's a 6in4 tunnel to a nearby VPS, so not through a common tunnel broker. Debugging this is the last thing I want to do when chilling, so I totally understand not wanting to bother. Especially with CDNs/large entities it's a thankless job.
cc @geerlingguy
@geerlingguy the fact that my #ISP refuses to provide me with proper configuration details (despite laws mandating them to do so!) alongside a shitton of issues with programs and services are the reason why my LAN will remain #IPv4-only for the foreseeable future.
- And that's not even accounting for the cursed #CGNAT on the #LTE-Fallback which has no #IPv6 to begin with despite explicitly requesting and setting up #DualStack…
TBH, the #IPv8 shitpost really sums up the problems of IPv6…
Discord really don't want to be reminded of how behind they are:
https://support.discord.com/hc/en-us/community/posts/360047840052-Add-IPv6-support?page=3
Been running this config for 3 weeks now and haven't had an issue. Went onto my guest network using the standard Quad9 resolvers and immediately started seeing issues with the CDN backing this Mastodon instance. Switched it to the ECS resolver and it seems to have cleaned right up.
So if you're using Quad9 with #IPv6, be sure to use the ECS resolvers.
RE: https://tenforward.social/@nivex/114989387484945100
Happy 14th Launchiversary #IPv6
https://www.worldipv6launch.org/
@goetz Doing this is strongly counter recommended and may result in traffic getting blocked or broken. There are also a bunch of subtle issues. I haven't had a chance to watch the video but I suspect it is similar to Jordi's proposal in draft-palet-v6ops-464xlat-opt-cdn-caches-04 ? Here's one of the comments I wrote on that a few years back:
https://mailarchive.ietf.org/arch/msg/v6ops/F9wB6dIqZtIDXqDejui_L7iA3NE/
Really the solution is to convince content providers to dualstack to enable #IPv6. Those who haven't have often done so for reasons.
Service Hinweis: nutzt bitte sie Credentials
gpn6 / gpn6 für die GPN SSID
Dann habt ihr ein #ipv6mostly Netzwerk.
#ipv6 #ipv4rip #ipv4 #clat #windows #464xlat #ipv6mostly #ipv6only #ripe92
slide 13/14/15 by Wilhelm Boeddinghaus
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_MmzPXy4.pdf
now corrected by Microsoft as promised two weeks ago
It is still a experimental version, not released yet. (Build 29599.1000 )
(now you can use several windows hosts in one network segment with clat)
boostedThe @ietf #v6ops draft on #IPv6 Prefix Assignment to End-Sites by Jordi Palet Martinez gives practical guidance for IPv6 access networks.
https://datatracker.ietf.org/doc/draft-ietf-v6ops-prefix-to-end-sites/
It recommends persistent prefix delegation, preferably /48 per end-site, and delegations longer than /56 should be avoided. A single /64 is not enough for an end-site.
As heard in Packet Pushers IPv6 buzz with Ed Horley, Tom Coffeen and Nick Buraglio: https://packetpushers.net/podcasts/ipv6-buzz/ipb201-the-never-ending-prefix-debate-revisiting-best-current-practices/
@MastodonEngineering
#IPv6 as a first class citizen?
Still mastodon.social does not federate and breaks interop promises.
@kistel maintains #Netiscope. Not to be confused with Netskope. 😁
https://github.com/robert-kisteleki/netiscope
It's a small #OpenSource tool for checking network connectivity from the #CLI or through an optional local #GUI. It runs checks for local interfaces, #DNS resolvers, open resolvers, root DNS servers, port filtering, #DoH, #SSH host keys and #IPv6 path MTU.
Wow, what a wrong default!
How NOT to implement #IPv6 !
"FortiGate Enables NAT for IPv6 by Default 🤦"
https://weberblog.net/fortigate-enables-nat-for-ipv6-by-default-%f0%9f%a4%a6/