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.
There are unattended Debian stable updates, but I doubt that broke it. Maybe something broken at Netcup? I have no idea how to even diagnose this... I do not exactly know how long it has been broken, but at max a week. If anyone knows where I could start here, do tell me please. I am using Firewalld, but again - did not change anything recently.
Some day I'm going to give an Intro to Networking talk using just #IPv6 and when somebody inevitably presses me to talk about IPv4 I'll be like "Well, yeah, that's how we did it when I was a kid."
@tschaefer Ja, die haben kein #IPv6.
Siehe https://ipv6.social/@goetz/116935881289423439
Hotel in AT, Wifi #LegacyIP only.
Schaut man nach dem ISP #AS8445 bei Cloudflare oder APNIC#IPv6 < 0,1%
Schade
https://radar.cloudflare.com/as8445#adoption-usage
https://stats.labs.apnic.net/ipv6/AS8445?c=AT&p=1&v=1&w=30&x=1
Silly mozilla:
[ERROR crashreporter::glean::uploader] failed to send glean ping: process failed (exit status exit status: 7) with stderr: curl: (7) Failed to connect to incoming.telemetry.mozilla.org port 443 after 2 ms: Could not connect to server
I guess the ultimate way to avoid being tracked is to go #IPv6-only.
Hello #Fosstodon! Our instance now supports both IPv4 and #IPv6! This should also include federation with IPv6-only instances. This has been our most requested feature on Fosstodon, so we’re super excited to add this support to our community.
OK, for better or worse, AMPRNet is still really hanging on to those 44Net IPv4 addresses. Now I know that 6to4 as a wider concept has been largely set aside primarily because of the anycast gateway issues, but I'm wondering if it could still be used to help this specific audience get familiar with the underlying concepts before graduating to real IPv6 addresses.
So, 2002::/16 isn't announced anymore because of aforementioned anycast issues, but could a subset of it still be announced? Consider, 44Net consists of
44.0.0.0/9
44.128.0.0/10
This translates into 6to4 prefixes of
2002:2c00::/25
2002:2c80::/26
Since ARDC already announces those v4 prefixes largely for the purpose of encapsulating them (44Connect, IPIP, etc), could they announce those v6 prefixes in the same vein? It seems quite feasible, so what weird edge cases am I missing?
Nice!
Our Mastodon instance burningboard.net has almost 60% of total traffic using the current generation of the Internet Protocol (IPv6) and only arround 40% still using the legacy-protocol from the 1980s (IPv4).
Measured on the PF firewall of our Mastodon webserver over the last 48 hours.
Crazy that IPV4 blocks are still so valuable while they should already have been relegated to the trash.
🗑️
Reverse DNS (PTR) is where a lot of people give up on IPv6.
The addresses are long. The nibble format is fiddly. Mail servers still check it.
The fix isn't cleverness. It's delegation done once, correctly. Point the zone at your own nameservers, then generate the reversed-nibble records instead of counting them by hand.
Good reverse DNS is invisible. That's the whole point.
A /44 is sixteen /48s and one reverse zone. Eleven nibbles, not twelve.
5 of my 6 most recently filed issues on GitHub are "Please turn on IPv6 on your Github Pages hosted site":
https://github.com/cbor/cbor.github.io/issues/115
https://github.com/SeaGL/seagl.github.io/issues/495
https://github.com/coredotradio/core.radio/issues/1
https://github.com/lynn/hello/issues/152
https://github.com/glowing-bear/glowing-bear/issues/1300
4 of those have been crickets 🦗. 1 responded with "Patches welcome" to a repo that didn't actually have the code that supposedly needed patched.
This shouldn't be so difficult.
It's amusing to me that the first responses to FOSDEM announcing their WiFi will be #IPv6 only were that people will just tether to their cellphones to get out. Here in the US, if you're fortunate enough to get venue WiFi that doesn't cost a day's wages, it will almost assuredly not have any IPv6. This means I have to tether to my phone which does have IPv6 to reach my services.
Also, to anyone complaining about a network that can't reach the legacy Internet: What? 15 years lead time wasn't enough for you? (I refer to RFC 6540 and World IPv6 Launch Day in Q2 2012.)
Jemand von euch ne #Fritzbox mit Mobilfunk und #IPv6 im Einsatz? Ist das normal, dass die Fritzbox das /64 der Telekom nicht an die Clients im lokalen Netz weiterverteilt, sondern nur eine ULA? Also die Box hat eine eigene GUA der Telekom und es wird auch das entsprechende /64 in der UI angezeigt. Alle Clients im Netz haben jedoch nur eine ULA und natives IPv6 ist entsprechend nicht möglich.
They still set wrong priorities 🤦
https://docs.google.com/document/d/1RZWbM8taOIp9TMlk4Ftrq5Ku6bDm0x9sp6DJibtC3wA/mobilebasic
I spent more time than I care to admit doing dual-stack IP detection in a way that works on modern browsers and all the way back to Internet Explorer 6.
I learned that IE6 will refuse to do XHR unless the host+port are identical to the current URL, and it doesn't support CORS. So, the workaround was using JSONP.
I wonder how many other people in the world have IE6 running with IPv6 support...
@Codeberg so, about /me threatening to switch off #IPv4 during #FOSDEM and thus taking down #GitHub... Look what they did two days after my toot...
https://bgp.tools/prefix/2606:50c0:c0de::/48#whois
They're not reachable yet, but that's progress. No matter what, I will only have #IPv6 on the @fosdem default network.
Ubuntu can't internet.
https://atlas.ripe.net/measurements/196196161/results
They provide five dns entries.
host releases.ubuntu.com
releases.ubuntu.com has IPv6 address 2620:2d:4000:1::17
releases.ubuntu.com has IPv6 address 2620:2d:4002:1::109
releases.ubuntu.com has IPv6 address 2620:2d:4002:1::108
releases.ubuntu.com has IPv6 address 2620:2d:4000:1::1a
releases.ubuntu.com has IPv6 address 2620:2d:4002:1::107
But only two of them work ( at my working place and my home network )
I really don’t need any more peers for my AS201379! (Okay, maybe a few more...)
Started back in December 2025, and now this "little" infrastructure is running:
14 individual eBGP sessions
3 Internet Exchanges
Multiple transit providers
110+ direct peers
All 100% IPv6 (2a06:9801:1c::/48) because legacy IP belongs in the last century.
Powered entirely by FreeBSD
: 4 routers on 15.1-RELEASE running FRR and PF.
@silverwizard @nuintari Good gawd.
I'm going to chock this down as yet another reason to switch to #IPv6only, because colons do not overlap with the separator for DNS names.
Although I can now imagine an extremely cursed setup where such "pseudo Legacy IP" DNS names are used to aid the transition to #IPv6... Please, no more transitional mechanisms lol
RE: https://thecanadian.social/@action_jay/116987371329094746
I'm on board with the label.
I can't find contact information for the site owner. If someone can find any, please pass https://help.dreamhost.com/hc/en-us/articles/216510458-IPv6 along to them. Thanks!
Just stumbled across another website hosted on Vercel.
FreeBSD call for testing: PREFSRC route attribute support <https://lists.freebsd.org/archives/freebsd-net/2026-July/009137.html>
this lets you set the preferred source IP address for outgoing packets via a particular route, overriding the default source selection logic.
it's particularly useful for IPv4-over-IPv6 routing; previously, BSD required assigning an IPv4 /32 to every interface for this to work properly; now, you can simply set the IPv4 loopback address as the preferred source.
it's also useful in situation where the router has multiple IPv6 addresses and you want to select which is used, similar to the "net.inet.icmp.reply_src=lo0" sysctl for IPv4 (but it affects all outgoing connections, not just ICMP errors).
it's also useful for IPv4 when you want to control this per-route rather than globally, especially if you're routing in multiple FIBs.
basically, it's really useful for a lot of situations and i'd love to see it land, so please help test it.
it is compatible with the Linux netlink API and works out of the box with BIRD (krt_prefsrc attribute).
the main patch is this one: https://reviews.freebsd.org/D58294 - either use the 'download raw diff' link, or use 'git arc patch D58294' to apply it to a tree.
you can send feedback directly to Pouria, or just reply to me and i'll forward it.
@LineageOS I see your OTA update server (mirrorbits) is hosted on Hetzner. Might I persuade you to enable #IPv6 on it?
Tell me you don't know how IPv6 addresses work without saying you don't know how IPv6 addresses work.
This is the most unique failure mode I've gotten in my #ipv6-only drill today. Message from the site, not the browser. Works fine when legacy is available.
When did amazon.com enable #IPv6? I avoid shopping with them if I can help it, but on a lark I clicked on an Amazon link to look up some info because the manufacturer site isn't reachable on IPv6.
Had to break the #IPv6-only drill for a moment by VNCing back to a dual-stack desktop so I could check the local team's schedule on milb.com. That and mlb.com are both hosted on GCP, who *still* have this hurdle:
Note: IPv6 functionality is available only in Premium Tier.
Major League Baseball probably sprang for the Premium Tier so it shouldn't be too much of an issue for them to enable it, but this is the opposite of table stakes. Shame on Google!
And the damndest thing is Automattic (AS2635) is announcing #IPv6 prefixes! C'mon, where's your AAAA records?!
That's a "fun" anti-pattern: Main domain is reachable on #IPv6 because Cloudflare but images are hosted on wp.com which isn't.
RE: https://toot.majorshouse.com/@majorlinux/116959618205197985
Doing an #IPv6-only drill this afternoon.
polygon.com has no AAAA records but is hosted in AWS. Can someone nudge them about rectifying this?