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.
Did you notice? The registration was temporary open today and we welcome all new users! 🥳
While we still have a plenty of free resources, we might switch from an open registration model to a recommendation / mentor model where already present users can invite new users.
This is not yet fix but a possibility to avoid misusage and abuse where our primary goal is still to provide resources for people interested into BSD based systems. Maybe also closer integrations with BSD communities like the BSD Cafe (@stefano) could be an approach.
#freevps #free #education #ipv6 #hosting #bhyve #proxmox #freebsd #netbsd #openbsd #runbsd #boxybsd @gyptazy
@Tubsta I have something for you: https://codeberg.org/IPv6-Monostack/delegacy-rpz/pulls/45
And also I would love an #IPv6 name and shame account 😈
In the last 24 hours I've been sent two links to websites that are down.
Well, they have an AAAA record but are down on #IPv6. If I schlep over to a legacy-only machine I can get to them.
iproute2 is inconsistent with its rules of showing IPv4 and #IPv6 output.
ip neighbor show - lists both address families
ip route show - defaults to IPv4, must use -6 flag to show IPv6 routes
I'd rather everything go ahead and show both families and require -4 or -6 if I want to filter. I think IPv6 first, so when I'm sitting on an IPv6-only node and 'ip route' gives no output, I get annoyed.
@daniel In some cases, lsof will show a service listening on #IPv6 when it works for both IPv6 and IPv4.
https://unix.stackexchange.com/questions/573456/why-does-lsof-indicate-my-ipv4-socket-is-ipv6
Blegh.
I remember being explained to me once before how #IPv6 SLAAC works, but I've since forgotten and I'm too NAT-pilled by IPv4 to be able to grok it on my own.
It also kind of makes my few privacy nerves itch to think that systems in an IPv6 #network just have public IPs by default instead of tucking them away privately behind a gateway with NAT. >.>
But at the same time, having a public IP by default would make spinning up self-hosted servers easy peasy, lemon squeezy.
Keine Spur von Überlast.
Die anderen drei deutschen Provider roamen wunderbar mit #IPv6
Nur bei Vodafone fällt ausschließlich IPv4 raus. Das wiederum, was Durchsatz betrifft, ganz normal.
Amazon Chime SDK now provides Internet Protocol Version 6 (IPv6) API endpoints
Posted on: Jul 31, 2025
https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-chime-sdk-ipv6-api-endpoints/
Googles KI phantasiert Sachen zusammen.
Deswegen mal meine Frage an die #Schweiz er hier.
Hat man als Nutzer von Swisscom, Sunrise oder Salt schon #IPv6 auf dem Smartphone?
(ich meine jetzt ausdrücklich keine Durchreisenden mit ausländischen SIMs sondern die Eidgenossen selbst)
einfache Testmöglichkeiten:
http://v6.de/
http://conn.internet.nl/connection/
https://test-ipv6.com/
https://bgp.tools/
https://ip.bieringer.net/
"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."
🙏
#ipv6 #aws
Amazon EventBridge now supports Internet Protocol Version 6 (IPv6)
Posted on: Jul 31, 2025
https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-eventbridge-internet-protocol-version-6/
breaking news
(I have to confess apple is sometimes good)
given a #IPv6only mobile access (like the Deutsche Telekom within Germany, not during roaming)
recent apple #iOS 18.5
makes
#IPv6mostly for clients via hotspot
#dhcpoption108 as well #pref64
I made also the windows test - in case option 108 is not provided by the client, iOS provides IPv4
#RUNBSD! But BoxyBSD now also starts to support #Linux! We're starting soon with the Linux support for already present users, offering free boxes:
* #AlmaLinux
* #Alpine
* #Debian
* #Devuan
* #CentOS
* #Fedora
* #Gentoo
* #OpenSuse
* #OpenEuler
* #RockyLinux
Just next to our core OS like #FreeBSD, #OpenBSD, #NetBSD, #MidnightBSD and #DragonflyBSD (and #illumos). This should also make the step easier to compare and test different scenarios where BSD provides a different behavior compared to Linux systems.
Thanks to @gyptazy for the implementation!
#VPS #VM #VirtualMachine #OpenSource #Hosting #IPv6 #BGP #FreeHosting #Community
I found the handwritten notes from the first #IPv6 talk I attended in June 2010 that would set me on this journey. I'm working on a blog post about it but I am out of practice in long-form writing.
This may sound like a dumb question, but with IPv6 am I supposed to ... learn the addresses like I have for IPv4?
With IPv4 I feel as if I have had a reasonable chance of learning some of the important blocks, but with IPv6... I genuinely hesitate to "adopt" because I fear having to learn the new addressing scheme.
If not, how should I ... "think" about IPv6 coming from the perspective of actually knowing IPv4-addresses?
IPv6 question:
There's a /64 subnet (using ULAs, so addresses are stable). All hosts on the subnet have static addresses, there is no SLAAC or DHCPv6. Those hosts have their addresses configured with /64 masks so they are able to communicate with each other directly.
There's also a router attached to that subnet, which provides access to other networks. That router emits RAs as a good IPv6 router should 🙂
The question is: is there any value to including this ULA prefix in the RAs themselves? Since the "M", "O", and "Autonomous" bits will all be 'false', how would the hosts benefit from the prefix being included in the RAs?
(This subnet is already alive and traffic is flowing as planned, so this question is mostly about "have I missed something", not "how do I make this work")
Spent nearly 3 hours chatting with @s3phy trying to understand the distinctions between various types of IPv6 addresses.
Networks are confusing as heck
Thanks to their patient proofreading I was also able to make this suggestion to clarify the UI in #GNOME Settings' "Network" info dialog (in gnome-control-center): https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3052#note_2505889
I'm hoping such labels can be added to make it a little bit clearer for users like me.
Fun-Fact: Our Mastodon instance "burningboard.net" doesn't just have the IPv6 address 2a01:4f8:1c1c:4d2::1 but is also reachable via 2a01:4f8:1c1c:4d2::fed1
as well as
2a01:4f8:1c1c:4d2:fed1:fed1:fed1:fed1
Might not make much sense, but it's funny :)
Amazon CloudWatch adds IPv6 support
Posted on: Jul 24, 2025
https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-cloudwatch-adds-ipv6-support/
Ahhh, how painful IPv6 still is when it comes to Kubernetes and such…
Just playing around with microk8s and dual-stack networking.
The minute I enabled IPv6, everything broke apart:
- coredns get a different IPv4 breaking service discovery
- documentation implicitly tells you to use ULA, no NAT applied
- switching to GUAs breaks other things I didn’t understand why
Now I got dual-stack in NAT mode going and I’m not sure whether I like it or not.
@timcappalli All these router/firewall appliance vendors seem to be allergic to "new" things like #IPv6, Wireguard, ACME (looking at you, WatchGuard)
What I want from #Mozilla: Overhaul their infrastructure so I can reach all[1] of their resources via #IPv6
What we get from Mozilla: AI 😔
[1] It only took them 7 years to get addons.mozilla.org working: https://bugzilla.mozilla.org/show_bug.cgi?id=1354049 . firefox.com now answers on IPv6 but links to download.mozilla.org which does not. Their infra is such a hodge-podge.