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.
Habe mich heute erst gewundert, mit welchen Defaults diese Software unterwegs ist.
Später, eher durch Zufall, dann das hier:
Change Ollama server to use IPv6 addressing by running export OLLAMA_HOST=":11434" before starting the Ollama server. Note this IPv6 support requires Ollama version 0.0.20 or newer.
It makes me somewhat sad that the agents which I've tried all use only #IPv4 to fetch content. For example, try this prompt:
> "What can you tell me about the contents of https://check-tls.akamaized.net/ ? What can you learn about yourself when you fetch it?"
It's hard to resist the urge to shame them for not supporting #IPv6. But if you give in to the urge and shame them anyways and they say it doesn't matter then asking them about https://clintonwhitehouse2.archives.gov/ can get them to apologize.
From #claude :
> "This is a great "gotcha" for my earlier claim that "there's no content I'd gain access to by having IPv6." You've proven that wrong! The archived Clinton White House is out there, and I can't touch it. Touché."
I recently took up an assignment to make certain SIP phones operate on a not-too-abnormal corporate network. I figured that while SIP appliances are ancient, they would still support modern #LegacyIP things like NAT traversal, since this network has no #IPv6 and there were two layers of NAT to the SIP server. How hard could it be?
Two weeks later, I have seen things. My naivete has yielded to the confounding world of 2000s era VoIP stacks, when SIP interop was non-existent. I wish I didn't know
An online friend of mine and me were having a chill conversation about DNS, IPv6 and what not. We went down memory lane how and when we actually met. Also Freifunk got an honorable mention.
Feel free to tune in while doing something random
@tschaefer
The best statement of every Jen presentation:
"You are not operating IPv6 until you turn IPv4 off"
That was fun. I opened a ticket to close an account I wasn't using. They responded with the classic "What could we have done to keep your business?" I basically called them out on never having an ETA on #ipv6 every time I asked despite it being a purchasing requirement for me. They completed the account closure without further comment. I doubt it will make a difference, but they do now have a record of losing at least one potential customer because they didn't keep up.
I finally located the version for Windows NT 4.0. Firefox 2.0 used IPv6 automatically!
Microsoft released an IPv6 Technology Preview for Windows 2000. It works! Management is all done with the command line and you're limited when it comes to support, but it does work! My Compaq Deskpro EN is now talking to the modern IPv6 world.
Any chance that someone might have spare RIPE ATLAS credits?
I currently do some experiments with the IPv6 routing of my AS201379 and being able to do measurements on Atlas would be sooooo helpful right now.
System Administration: Week 5: Networking I: IPv4 Basics & CIDR subnetting
In this video, we cover the basics of the 32-bit IPv4 address and how we organize networks using Classless Inter-Domain Routing or CIDR subnetting. (Don't worry, we'll get to #IPv6 in the next video.)
System Administration: Week 5: Networking I: IP Allocation & IPv4 Exhaustion
Mommy, where do IP addresses come from? In this video, we discuss how IANA allocates IP addresses to the Regional Internet Registries and try to illustrate just how large the #IPv6 address space is.
One last oddity from my NetworkPolicy project over the last few days..... I am getting the following in my hubble logs:
Feb 22 20:48:28.333: :: (ID:16777244) <> ff02::1:ff99:2a81 (ID:16777244) Unknown L3 target address DROPPED (ICMPv6 NeighborSolicitation)
Feb 22 20:48:29.325: fe80::b85f:80ff:fed7:6193 (ID:2435) <> ff02::16 (ID:16777244) Invalid source ip DROPPED (ICMPv6 143(0))
Feb 22 20:48:29.325: fe80::b85f:80ff:fed7:6193 (ID:2435) <> ff02::2 (ID:16777244) Invalid source ip DROPPED (ICMPv6 RouterSolicitation)
Feb 22 20:49:43.117: :: (ID:9705) <> ff02::16 (ID:16777244) Invalid source ip DROPPED (ICMPv6 143(0))
Feb 22 20:49:43.213: :: (ID:16777244) <> ff02::1:ffaf:3d08 (ID:16777244) Unknown L3 target address DROPPED (ICMPv6 NeighborSolicitation)I feel like I must be missing something with my cilium config?
Elster wie immer über #IPv6 bearbeitet und ✅
Die Feedbackseite in Sachsen kann's nicht:
www.ihr-finanzamt-fragt-nach.de
Außerdem: Wer hat nach vielen Formularen noch Bock ein weiteres auszufüllen?
boosted#IPv6 adoption is still terrible.
Akamai, Cloudflare, and Google all report roughly 45% of traffic to their services using IPv6 in the US...
https://www.akamai.com/security-research/ipv6-adoption-visualization
...but that's (a) not all that great, and (b) only HTTP traffic to major services.
Just what % of sites actually _offers_ IPv6? I took a look...
Let's start at the #DNS. Obviously, the root is fully dual-stack, but what about the TLDs?
Overall, that's not terrible: only 18 of the 1,436 TLDs have only IPv4-only NS records in the root zone, although 240 TLDs have at least one IPv4-only NS.
But for the top 1M _second-level_ domains, this already drops down and only around 72% of them have at least one IPv6-enabled NS.
And finally, #SMTP. Looking at the Top 1M Domains' MX records, over 52% are IPv4-only; 45% fully dual-stack, and another 2% or so having at least one MX record with an IPv6 address.
But there are also large MX service providers who have IPv6 addresses on some MX records *and then don't accept traffic on those IPv6 addresses*, and large mail service providers like Yahoo, GoDaddy, and Namecheap (to name just a few) are completely IPv4-only.
All around, I don't see the overall trend to get us to universal #IPv6 adoption within the next 10 or perhaps even 20 years.
Pareto suggests the first 80% of any large project take 20% of the time and effort, and 30 years into our IPv6 adoption migration, we're barely half-way there.
As long as IPv6 is not seen as a fundamental requirement to do business, people will continue to disable it; as long as large businesses disable IPv6, it will not be seen as a fundamental requirement.
Amazon EKS is really catching up with IPv6 support.
However, as soon as you apply custom CRDs or something third party, you’re getting screwed, because none of the devs work with IPv6 in mind.
Zur gleichen Zeit bei #sunrise bezüglich #Ipv6
"Hierzu habe ich noch keine Informationen. Sollten intern Daten kommuniziert werden, werde ich diese in der Community auch kommunizieren."
https://community.sunrise.ch/d/47589-ipv6-ueber-mobilfunknetz/7
"Swisscom’s mobile services deliver reliable and highly
secure coverage in Switzerland and internationally.
Among the two primary mobile services, voice and data,
Voice over LTE (VoLTE) already utilises IPv6. With the
introduction of a Dual Mode 5G Mobile Core in 2025,
we are laying the foundation to ensure that in 2026,
Swisscom’s entire mobile offerings will be either
IPv6-only or at least IPv6-first."
🙏
RE: https://mastodon.social/@rickvanrooijen/116024625573654978
More #IPv6 work needed - things are moving forward!
Amazon MSK now supports dual-stack (IPv4 and IPv6) connectivity for existing clusters
Posted on: Feb 17, 2026
https://aws.amazon.com/about-aws/whats-new/2026/02/aws-msk-dual-stack-ipv4-and-ipv6/
@T_X @axx so for #FOSDEM 2027, I had another stupid idea everyone insisted was good: it will be #IPv6-only on the main network. The dual stack will get a yearly name change to prevent auto-reconnect. We want people on v6-only and break stuff left and right. Every. Single. Year.
And if #GitHub is not on v6 by next year, trust me, they will put _something_ in place very quickly.
My friend and colleague Kyle Rose developed a vastly better PCRE regexp for matching #IPv6 addresses than the top answer on stack overflow:
https://www.krose.org/~krose/computing/ipv6
That page includes an explanation for how/why it works. Of course it's generally better to use a library, but sometimes you need a regexp.
Fellow Homelabbers, has anyone of you any experience running an IPv6 only Matrix / Synapse Server and could tell me if there any noticeable limitations apart from homeservers not beeing reachable via IPv6 in 2026?
@homelab @homelab_de #homelab #matrix #synapse #ipv6 #selfhosting
@cloudflare Could you help your customer #Shopify to fix their connectivity by not disabling #IPv6 on websites they host?
I'm starting to wonder, if Amazon continues to buy up as much of the IPv4 address space as they can, will AWS eventually become the only network---not the only IaaS platform, the only *network*---that can practically absorb IPv4 Internet growth of any kind? #IPv6