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.
The updated control panel at @BoxyBSD by @gyptazy
@gyptazy #FreeBSD #NetBSD #OpenBSD #FreeVPS #Hosting #IPV6 #BGP #DN42 #smolBSD #RUNBSD #BSD #BSDHosting #Hosting #FreeHosting #community #opensource
Stilblüten der Falschwahrnehmung von Anbietern wenn man sich auf die Nichterreichbarkeit per #IPv6 hinweist:
> Unsere Seite ist derzeit über das weit verbreitete IPv4-Protokoll erreichbar. Dieses wird nach wie vor von nahezu allen Internetanschlüssen und Endgeräten unterstützt. Daher sollte der Zugriff in der Regel problemlos funktionieren.
1/2
> Unser aktueller Ansatz orientiert sich an den allgemeinen Wünschen und technischen Möglichkeiten der Mehrheit unserer Kunden. IPv4 ist weiterhin generell weit verbreitet, sodass für die meisten Kunden keine Einschränkungen bestehen.
2/2
We've created a large number of transition technologies for migrating from IPv4 to #IPv6 , but we still have to migrate the people. To that end I have a small proposal to help folk get used to the new way of doing things:
IPv4 addresses are 32-bit numbers, the most common representation being the dotted quad. There is, however, nothing stopping you from expressing that number in hexidecimal as in IPv6. So, if I want to ping my router's IPv4 address, this is a valid command: ping 0xac1f0301
Once you get used to seeing all your addresses in hex, expanding your mind out to more digits becomes a much easier exercise.
TIL: Wenn du #Wireguard nen #IPv6 only Tunnel bereitstellen lassen möchtest, scheinst du, zumindest auf #Android15, trotzdem ne lokale #IPv4 Adresse konfigurieren zu müssen weil sonst Android keinen IPv4 Traffic mehr raus lässt (auch wenn nur ::/0 in den Tunnel gerouted werden soll).
...fiktiven Behörde – dem „Bundesamt für Muster und Beispiele“ (kurz BAMBI)...
Ein Bambi 🤗
https://de.linkedin.com/posts/bdbos_sccon25-ipv6-protokollstandard-activity-7387353105413095424-Ncb1
New blog post! My adventures in IPv6 in the homelabhttps://blog.transitory.social/posts/2025-10-25-adventures-in-ipv6/ It covers going from an IPv4 only to Mikrotik config, all the way to getting Kubernetes running in dual stack mode with pods and services assigned IPv6 addresses (Note: I have enabled a cache middleware on the blog, so if that explodes someone give a shout and I'll disable it ;) )
finished landing the fix for this FreeBSD bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289198
this is quite fun. in one sense, it's a fairly serious bug: inet_net_pton() is completely broken for IPv6; it simply doesn't work and returns garbage output. but this bug has been present since 2006, when this function was first imported into libc, and no one noticed until August of this year when the PR was filed.
what i conclude this from is that literally no one uses these functions, and they should probably have never been imported in the first place. but, well, we can't remove them without breaking ABI compatibility, so now they're here forever, like an obnoxious uninvited party guest.
@goetz @ungleich All of it is running inside #kubernetes, all #ipv6 based and using #bird as the software. Quite some fun.
What I really hate on #IPv6 #SLACC that it will kill Users and Enterprises in the same way.
If a system has a IPv4 RFC Addy assigned, but gets a public IPv6 via SLAcc then this is the dead of most systems.
Admins and users mostly do not even know that they have this public IP address and that thy are fully open to the internet.
This definitely should be opt in.
Ich bin mir inzwischen ziemlich sicher, dass das Problem mit #NextDNS und Apple #PrivateRelay am #IPv6 der Mobilfunkanbieter liegt.
Mit #IPv4 geht es ohne Probleme und IPv6 geht mit und ohne Private Relay nicht.
Also entweder eine Änderung in #iOS26 in Bezug auf #Mobilfunk und IPv6, oder NextDNS hat mit IPv6 im Mobilfunk ein Problem.
Gestão promete que outras plataformas e sistemas também vão migrar para o novo protocolo internet.
Let me share how happy I am. Since this evening I've my self managed routed #ipv6 connectivity at my new home. Not only does surfing via #IPv6 feel much better (it's like driving an EV), but additionally the servers in the cellar are routed in a different network with their own uplinks. It's a beauty. Have a good evening everyone.
@rvstaveren What does your autocomplete defaults to when you start to type IPv. ? #ipv4 #ipv6
| IPv4: | 1 |
| IPv6: | 6 |
| Varies: | 1 |
| Doesn’t autocomplete: | 2 |
#NetworkManager #dnsmasq now listens to #IPv6 localhost for #DNS querying. About time!
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1504
@apalrd Have you been facing issues with #WiFiCalling while running #IPv6mostly in #OPNsense ?
I can't figure out exactly why it breaks in my home network, since there are no misconfigured rules nor anything related - if I disable DHCP option 108 and assign old addresses to each client, it works; when passing through #tayga #nat64, it stops entirely.
All this because the carrier's servers are stuck in the last millenium, of course they are: https://www.netify.ai/resources/mobile-gateways/country/br
"You appear to be able to browse the IPv6 Internet only. You have no access to IPv4. That's pretty bold!"
At this point it really shouldn't be all that bold.
@homelab
Today I followed @jwildeboer Blogposts and finally set proper internal #ipv6 and #dns in my homelab.
Once I get that clusterfuck, that is ipv6 on IONOS under control my blog will also supports IPv6
Lots of small and easy things, that I still never bothered to touch.
Technically my IPv6 journey isn't done, but it'll be a good part 1. Part two I still need to do the work for. The parts left are: * Local Kubernetes load balancer IPv6 support: I need to get ipv6 bgp working, and I need that to be serving IPs in both ULA GUA pools. More explanation on my questions and hangups with the second point there: Ok so everything gets a GUA, neat except.... What happens if my prefix changes? Normally that isn't supposed to happen at all. It isn't likely to happen for me unless I move. Ok fine except ... Then what? Manually update every firewall and maybe routing rule? (Not as worried about DNS side of things) I think I found a Mikrotik script that does this so maybe that is the play? I'm just using ULAs for now for everything at the moment (except those remote nodes do have ipv6 GUAs)
* I need to figure out how to handle GUA and firewalls.
Amazon DocumentDB now supports Internet Protocol Version 6 (IPv6)
Posted on: Oct 16, 2025
https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-documentdb-ipv6-support/
Jemand in einem österreichischen Forum behauptet, dass #Drei #at #IPv6 #5G hätte.
Hier sehe ich leider nichts dergleichen:
https://stats.labs.apnic.net/ipv6/AS25255?a=25255&c=AT&x=0&s=0&p=0&w=3
Der Screenshot der RTR Netztest App hat IPv6 gelb statt grün gekennzeichnet.
https://www.lteforum.at/mobilfunk/ipv6-bei-drei.25514/
Kann jemand dazu eine belastbare Aussage dazu machen?
Amazon DynamoDB now supports Internet Protocol version 6 (IPv6)
Posted on: Oct 9, 2025
https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-dynamodb-ipv6/