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.
Every time I encounter somebody talking down #IPv6, saying how it is unnecessary or flawed or never going to work, I feel sad. Briefly. Briefly, I feel sad. Sad for that person. And then I go back to the long, slow, important work of transforming all the networks I touch to use IPv6.
I still don't understand the advantage, for me as a user, of enabling IPv6. The privacy angle concerns me. IPv6 SLAAC addresses can embed your MAC address and make devices uniquely trackable across networks, and while privacy extensions exist they're inconsistently implemented across devices (especially IoT). It feels like a headache for marginal user benefit that only benefits those with extremely large data footprints (datacenters).
@flameeyes
Thank you for sharing this insight.
Please tell your instance admin, to fix their IPv6 as well. As federation for IPv6 is broken/not possible due to their #K8S setup.
I've been reading IETF draft-martin-retry-over-ipv6-02 which proposes serving a HTTP 566 error code over IPv4 to indicate that a site is only available over IPv6.
I've thought about this before since I've been looking for a way to signal to IPv4-only clients that a site is not "broken", but that their endpoint is missing connectivity.
Needing to maintain a whole IPv4 stack to do it means it's good for transition, but maybe less useful longer-term.
I don't really see why browsers don't already gracefully handle the IPv6-only-site-on-IPv4-only-network situation. I wonder if it'd need a standard to exist before any would adopt it. And where that standard would live.
As noted elsewhere, it looks like Google's token #IPv6 person has returned from their vacation and once again updated the company's stats page, which now shows a new run of four consecutive Saturdays above 50%:
@tschaefer
Ab 12 Uhr ging es. War aber ein nettes Selbstexperiment. Gelitten habe ich vor allem unter fehlendem #DuckDuckGo, die Familie vermisste auch #Pinterest und allgemein halt die #Microslop-Cloud (für die Arbeit).
Längerfristig dann natürlich auch #GitHub (#NixOS hostet alle Pakete dort), und beim Suchen (mit Google 😖) und Browsen tauchen immer wieder Seiten auf, die nicht mehr laden, wie zum Beispiel social.bund.de. (cc @itteam)
#ipv6only #ipv6
Can anyone out there who knows #IPv6, #dnsmasq and #OPNsense help me?
I’m trying to figure out why DHCP clients on my LAN are respecting Option 6 to force IPv4 DNS servers, but not Option 23 for DNS over IPv6
Much more detail here:
https://forum.opnsense.org/index.php?topic=52230.msg269245
https://tf.nist.gov/tf-cgi/servers.cgi
> The generic name time.nist.gov will continue to point to all of our servers on a round-robin basis, and users are encouraged to access the service using this name.
Except that it doesn't any more. That name now points to a load balancer that is only reachable via legacy IP.
#IPv6 is *so* ready!
https://core.telegram.org/bots/webhooks
> You'll need a server that:
>
> Supports IPv4, IPv6 is currently not supported for webhooks.
I mean, it's nearly 10 years since they started half-assing IPv6… you can't expect them to have solved it…
https://flameeyes.blog/2017/08/06/ipv6-horror-story-telegram/?mtm_campaign=social&mtm_kwd=mastodon
Wiedermal eine kaputte Seite entdeckt.
#dualstack hides errors
Werde wohl in Kürze eine E-Mail hinschicken.
Wie seht ihr die Chancen, dass es repariert wird?
https://www.swm-infrastruktur.de/online-services/stoerungsauskunft
| gut: | 3 |
| schlecht: | 9 |
Closed
#IPv6 readiness of streaming services:
#Spotify 42,1%
#Deezer 17.5 %
#Qobuz 31.7%
#Soundcloud 21.7%
Everyone who is a customer and lives in Germany or France should tell them.
Your ISP prices are influenced by this.
They have to buy larger and larger NAT boxes.
boostedWährend meiner Recherche nach Anbietern für BGP Tunnel (oder zumindest VPS mit BGP Access), die an der US-Ostküste und Sydney / Australien verfügbar sind...
... Und nur mit Ökostrom laufen, bin ich hart gescheitert. Das scheint es schlichtweg nicht zu geben. Nur in Europa. Aber das Thema "100 % Ökostrom" scheint im Rest der Welt einfach nicht relevant zu sein.
Außer bei Hetzner. Aber die haben keine BGP Tunnel und deren VPS können es auch nicht. Nur Colo. Und in Australien sind sie auch nicht - nur Singapur.
Uff.
Also wenn jemand einen Tipp hat - gerne her damit!
* USA / Australien
* Ökostrom
* BGP
@MaddieM4 That last point is why I still keep fighting. At this moment I can hit a webserver running in a VM/container on my home network (this could just as easily be a cheap SBC) while I'm on my cell network via #IPv6 with no VPN. Throw an entry in DNS, Let's Encrypt Just Works™. I want everyone to have this seamless of an experience. But as long as The Industry keeps treating IPv4 addresses like real estate, folk aren't going to know about the easy path. It's not profitable.
I get so frustrated because it's been "a ways off" for 15 years now (± depending on who you ask). The current "AI" crisis has blown up in the last 2-4 years. Infrastructure isn't "sexy", but I find fulfillment in making it work.
Huge props to the https://climate.us/ team for standing up a brand new site in challenging conditions and including #IPv6 support from go.
@nivex
@paulv how can we help to get this fixed?
Link Oregon supplies #IPv6 prefixes to customers
Back in September I asked That Guy if he could make one of the SFC websites available over #IPv6. I got a lecture disguised as a question basically telling me his priorities were the only right ones.
It appears he has no concept of intersectionality. All of the things we're fighting for matter, and we could lift each other up. But that argument fell on deaf ears.
For those who want the receipts, here's the thread starting at my request: https://tenforward.social/@nivex/115129973828133884
As others have stated about the current discourse: Please don't dogpile him. I have no interest in re-litigating this one. I'm digging this up to establish a pattern, nothing more.
Something else worth noting: He speaks as the organization. As such, the SFC is now dead to me. I suspect others feel the same way after the current discourse. Good luck getting donations.
@tschaefer
Das dauert dann doch länger zu resolven, als der Vertrag noch läuft. In 9 Tagen endet hier der Service von Vodkafone und #Cable4 übernimmt. (Nebenbei: Ist irgendwas zu #IPv6 bei denen bekannt?)
Had another "check out my new site" post come across my timeline. Site is legacy-IP only. Dug in a bit to see what hosting they're using. "AI" this and "agentic" that. No particular desire to try and evangelize that rabbit hole. And no I'm not naming them. Don't want to give them any notoriety.
RE: https://tldr.nettime.org/@tante/116776900682624107
#IPv6 is documented Internet best practice (RFC 6540 / BCP 177) but we still have ~50% deployment after decades, so we see how much "best practice" actually means.
How do I configure my #IPv6 #firewall rules when the delegated prefix from my ISP keeps changing? Is it safe to match the interface identifier (lower 64 bits) only? That feels risky since anyone could legitimately use the same lower 64 bits in their own prefix.
I guess I can configure things to use the ULA prefix when connecting internally, and the delegated prefix only for the internet?
✅️ Sent application for my first own AS to RIPE :)
Wish me luck! Hopefully they'll accept my application in a few days.
@shanselman Can you add the AAAA records too?
2606:50c0:8000::153
2606:50c0:8001::153
2606:50c0:8002::153
2606:50c0:8003::153
Been a while since I posted a blogpost so this is a quick one.
Raspberry Pi OS can cloud-init now for pre-boot config which is awesome.
But there's not many guides out there that cover the right syntax for static IPv6 networking with it, so I threw together my working config and notes in case it helps anyone.
I still periodically drop onto one of my #IPv6-only networks and do routine browsing just to see how much is still inaccessible. It's unfortunate the owners of those dead links have no clue that there is traffic _not_ reaching them.
A website I frequent sends a server string of "Cloudflare (WP Engine)", so I head over to the WP Engine website to see if I can ask why they don't have #IPv6 on any of their hosts. I am immediately accosted by their AI chat bot popup causing me to reflexively close the tab. I hate this reality.
Prices for dedicated servers and VPS instances are raising more and more! Guess what…
#BoxyBSD still provides free VMs to people who want to learn #FreeBSD, #OpenBSD, #NetBSD or even #Illumos / #opensolaris - all with full #ipv6 support - of course! #LearnBSD & #RUNBSD
#opensource #community @gyptazy #BSD #hosting #isp #provider
@MaddieM4 What's really sad is that was about the time I was sitting in a community college classroom listening to the instructor tell us all we had to remain adaptable to change to thrive in this industry. Well here I am a quarter century later having adopted the hell out of this "newfangled" #IPv6 thing and once again I'm the oddball.