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.
eat your hearts out, IPv6 nerds - HE sent me my Sage t-shirt as a lil surprise. excuse me while I *flex* a bit... 💪
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.
I recently discovered RFC 9131 that is supposed to make #IPv6 attachment work much faster and reliable. It is already supported in Linux, but off by default.
What would be the best way to convince at least desktop-oriented distributions like @fedora to have this one particular sysctl `ndisc_notify=1` turned on by default?
https://datatracker.ietf.org/doc/html/rfc9131#name-nodes-sending-gratuitous-ne
At #CHINOG13, @forwardingplane explained why #IPv6 matters beyond address exhaustion.
The presentation covered the limits of #NAT, the operational cost of permanent dual-stack, and the case for moving toward #IPv6only networks with translation for legacy #IPv4 services.
📄 https://chinog.org/wp-content/uploads/2026/06/nick_buraglio_ipv6_why_should_you_care.pdf
🎥 https://www.youtube.com/watch?v=dWO-bgcoU1s
When you have a #Fairphone6 and experience very long loading time in some #WiFi networks then you hit most like this bug [1]. Sadly, It is related to #IPv6 and most likely a #driver #bug which needs to be fixed.
Luckily, there is a temporary workaround, see [2] which at least "reduces the pain".
Called my ISP to remove CGNAT and they said „no problem we will call you tomorrow to update you“. If I had known earlier that it would be that easy I would have done that in the first place and wouldn’t have bothered with IPv6. Well at least I learned a bit about IPv6.
@LineageOS I see your OTA update server (mirrorbits) is hosted on Hetzner. Might I persuade you to enable #IPv6 on it?
RE: https://social.numerique.gouv.fr/@arcep/116928560975019877
🇬🇧 For our dear English-speaking subscribers, the 2026 report on the state of the internet in France is now also available in English!
📣 The press release: en.arcep.fr/news/press-r...
📊 The report: en.arcep.fr/uploads/tx_g...
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.
Nick Buraglio opened his CHI-NOG 13 talk with “one of my jobs is taking IPv4 out of the network.” ESnet has run IPv6-only in production since 2018, and Google's adoption graph crosses 50% on weekends now, when everyone's home on residential broadband. My writeup of the talk that finally made the v6 pitch land: https://routerjockey.com/buraglio-ipv6-why-you-should-care-chi-nog-13/ #IPv6 #networking
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
Did some coding on SixSpotting over the last couple days. It's all backend changes, not the least of which is moving from Postgres to SQLite since it's such a tiny little app. Nothing should be user visible, but if I did goof something please let me know.
A Farewell to ARPs: IPv4 Service on IPv6-Only Networks
https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/
A new article at the RIPE blog explains the current state of running IPv4 services over IPv6-only networks.
The three pieces are RFC 8950 (IPv6 next-hops for IPv4 prefixes), a draft about IPv6 next-hops for IPv4 routes, and a draft for solving the IPv4 gateway problem that systems running IPv4 services in these kind of networks typically have.
It’s cool to see this gateway thing in such an informed piece, I’ve been wondering about that bit for a while. You might have seen different service providers solving this in different ways, with a /32 on either a regular interface or a loopback, and a strange default route pointing to just an interface (with no destination IP), or a destination IP in a prefix that the given machine doesn’t know about.
Linux seems to support a couple of different ways to go about this (of course), and FreeBSD and OpenBSD each support a single, different solution AFAIK. I don’t believe illumos even has a way to solve this problem at the moment, but I might have that one wrong.
Anyway, do have a look at the article:
https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/
"A Farewell to ARPs: IPv4 Service on IPv6-Only Networks": https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/
i really like this idea. it defines 192.0.0.11 as a special value for IPv4 default gateway meaning "use the IPv6 gateway" (as in IPv4-over-IPv6 routing), for routed networks that assign /32s to each client.
it's backward compatible with existing hosts as long as the router replies to ARPs for 192.0.0.11. but if the host supports this proposed standard, no ARP is required at all.
it doesn't let you do anything you can't do today, but it makes things neater and simpler.
Wondering how and why? With @BoxyBSD@bsd.cafe and @BoxedTux@mastodon.social, I’m already running platforms that provide free VPS instances for educational purposes, learning and testing for years now. I guess, providing real AS and peering services (maybe even sponsoring LIR in cooperation [but this would cost money]) could also be very interesting for several ones, apart from the DN42 network. Happily looking for feedback…
#isp #network #networking #ipv6 #as #autonomoussystem #ipv4 #free #opensource #devops