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.
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.
Following some discussions during #IETF last week (in the hallway and on various mailing lists), the awesome #IPvFoo extension now shows in Mozilla #FireFox if connections used H1, H2, or H3, not just IPv4-vs-IPv6! This is helpful for seeing how that angle of Happy Eyeballs works.
(It would work in the Chrome version as well but the interface for getting at this info is broken and always returns H1.)
Note that if the connection starts with H2 but then switches to H3 for later objects on the hostname (eg, if you have an Alt-Svc record) then it will show H3 rather than H2.
@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?
@volpeon @MaddieM4 Yes, the Internet¹ is changing. We're migrating from IPv4 to #IPv6, something Mozilla doesn't seem to want to do. There was a bug open for 8 years to get addons.mozilla.org. Many of the rest of their subdomains, notably download.mozilla.org, are still not enabled. (I was surprised when to find support.mozilla.org enabled. It wasn't the last time I checked.)
¹ The Internet, as in the thing where you put packets on the wire and they come out the other end. The thing the open web that Mozilla espouses the virtue of is built atop.
RE: https://chaos.social/@RichiH/116958290141827888
As someone who runs fairly frequent #IPv6-only drills, this event should be fun to watch.
Wherein I get snarky with a support bot:
Me:
When will you be making linktr.ee available on IPv6?
Linktree Support joined the conversation
I don't have any information about IPv6 support for linktr.ee in our knowledge base, so I can't give you a timeline or details on this. I've passed your question to our team, who will follow up with you directly.
Jem joined the conversation
Hello! Thank you so much for reaching out with your question about when Linktree will be available on IPv6. At the moment, Linktree has not yet announced a public timeline for full, native IPv6 support on its main domains. Currently, the platform uses IPv4 connections along with Content Delivery Network (CDN) routing to deliver its services. You can find more details on the Linktree Homepage. If you have any other questions, please don’t hesitate to ask. We’re here to help!
Me:
Hello! Thank you so much for the same non-answer I get from every company I have asked this question of for the last 15 years. I cannot, in fact, find more details about this on the Linktree Homepage. If you have any actual concrete information, please don't hesitate to provide it.
https://developers.redhat.com/articles/2026/07/08/networkmanager-supports-ipv6-mostly
NetworkManager 1.58 is currently sitting in Debian experimental. Hope this makes it into forky.
#cfp #callforpapers #ipv6
3. IPv6 Expertenkonferenz
https://www.bdbos.bund.de/DE/Aufgaben/IPv6/expertenkonferenz/expertenkonferenz.html