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.

Site description
Cablespaghetti's personal snac instance
Admin email
sam@cablespaghetti.dev
Admin account
@sam@cablespaghetti.dev

Search results for tag #ipv6

[?]Thomas Schäfer » 🌐
@tschaefer@ipv6.social

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.

promptfoo.dev/docs/providers/o

    [?]Thomas Schäfer » 🌐
    @tschaefer@ipv6.social

    Liebes @BMDS ,

    warum ist es so schwierig, den Betrieb dieser Webseiten sicherzustellen?

      [?]Erik Nygren :verified: » 🌐
      @nygren@hachyderm.io

      It makes me somewhat sad that the agents which I've tried all use only to fetch content. For example, try this prompt:

      > "What can you tell me about the contents of 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 . But if you give in to the urge and shame them anyways and they say it doesn't matter then asking them about clintonwhitehouse2.archives.go can get them to apologize.

      From :

      > "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é."

        [?]Litchralee_v6 » 🌐
        @litchralee_v6@ipv6.social

        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 things like NAT traversal, since this network has no 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

          [?]Chris 🏃 🐧 [he/him] » 🌐
          @cr@chaos.social

          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 :awesome:

          youtube.com/watch?v=5nd8A7h9HHY

            [?]goetz [he/him] » 🌐
            @goetz@ipv6.social

            @tschaefer
            The best statement of every Jen presentation:
            "You are not operating IPv6 until you turn IPv4 off"

            You are not operating IPv6 until you turn IPv4 off

            Alt...You are not operating IPv6 until you turn IPv4 off

              [?]Thomas Schäfer » 🌐
              @tschaefer@ipv6.social

              [?]Nivex 🐧 📻 [he/him] » 🌐
              @nivex@tenforward.social

              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 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.

                [?]voided warranty [They/them] » 🌐
                @voided@hachyderm.io

                Of course IPv6 multicast in rust embedded is a proper challenge

                  Karl Baron boosted

                  [?]Mike Roach » 🌐
                  @mroach@ublog.mroach.com

                  I finally located the version for Windows NT 4.0. Firefox 2.0 used IPv6 automatically!

                  #RetroComputing #WindowsNT #IPv6

                    Karl Baron boosted

                    [?]Mike Roach » 🌐
                    @mroach@ublog.mroach.com

                    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.

                    #ipv6 #windows2000 #retrocompuing

                      [?]Larvitz :fedora: :redhat: » 🌐
                      @Larvitz@burningboard.net

                      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.

                        [?]Jan Schaumann » 🌐
                        @jschauma@mstdn.social

                        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 in the next video.)

                        youtu.be/CxdN-TcpSk8

                          [?]Jan Schaumann » 🌐
                          @jschauma@mstdn.social

                          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 address space is.

                          youtu.be/r2GXh8uUgWc

                            [?]Rachel [She/Her] » 🌐
                            @rachel@transitory.social

                            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 haven't quite gotten to the bottom of this one, I found some cilium issues that look almost relevant, but didn't get me anywhere.

                            I feel like I must be missing something with my cilium config? ​:neocat_confused:

                              [?]Thomas Schäfer » 🌐
                              @tschaefer@ipv6.social

                              Elster wie immer über 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?

                              Ihre Einkommenssteuererklärung wurde erfolgreich versendet!

                              Alt...Ihre Einkommenssteuererklärung wurde erfolgreich versendet!

                                [?]Thomas Schäfer » 🌐
                                @tschaefer@ipv6.social

                                RevK :verified_r: boosted

                                [?]Jan Schaumann » 🌐
                                @jschauma@mstdn.social

                                adoption is still terrible.

                                Akamai, Cloudflare, and Google all report roughly 45% of traffic to their services using IPv6 in the US...

                                akamai.com/security-research/i

                                ...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...

                                  [?]Jan Schaumann » 🌐
                                  @jschauma@mstdn.social

                                  Let's start at the . 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.

                                    [?]Jan Schaumann » 🌐
                                    @jschauma@mstdn.social

                                    And finally, . 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.

                                    Total	| % of MX records

All MX IPv4 only	334,696	52.03
All MX IPv6 only	74	0.01
All MX dual-stack	288,849	44.91
At least one MX dual-stack	301,273	46.84
At least one MX IPv4-only	347,119	53.96
At least one MX IPv6-only	271	0.04
Only IPv4-only and IPv6-only MXs	89	0.01
Dual-stack with at least one IPv4-only MX	12,334	1.92
Dual-stack with at least one IPv6-only MX	108	0.01
Dual-stack + IPv4-only + IPv6-only MX	18	0.002
Dual-stack + only IPv4-only MX	12,316	1.91
Dual-stack + only IPv6-only MX	90	0.01
At least one MX IPv6 enabled (dual-stack or IPv6-only)	301,436	46.86

                                    Alt...Total | % of MX records All MX IPv4 only 334,696 52.03 All MX IPv6 only 74 0.01 All MX dual-stack 288,849 44.91 At least one MX dual-stack 301,273 46.84 At least one MX IPv4-only 347,119 53.96 At least one MX IPv6-only 271 0.04 Only IPv4-only and IPv6-only MXs 89 0.01 Dual-stack with at least one IPv4-only MX 12,334 1.92 Dual-stack with at least one IPv6-only MX 108 0.01 Dual-stack + IPv4-only + IPv6-only MX 18 0.002 Dual-stack + only IPv4-only MX 12,316 1.91 Dual-stack + only IPv6-only MX 90 0.01 At least one MX IPv6 enabled (dual-stack or IPv6-only) 301,436 46.86

                                      [?]Jan Schaumann » 🌐
                                      @jschauma@mstdn.social

                                      All around, I don't see the overall trend to get us to universal 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.

                                        [?]Chris 🏃 🐧 [he/him] » 🌐
                                        @cr@chaos.social

                                        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.

                                          [?]Thomas Schäfer » 🌐
                                          @tschaefer@ipv6.social

                                          Zur gleichen Zeit bei bezüglich

                                          "Hierzu habe ich noch keine Informationen. Sollten intern Daten kommuniziert werden, werde ich diese in der Community auch kommunizieren."

                                          community.sunrise.ch/d/47589-i

                                            [?]Thomas Schäfer » 🌐
                                            @tschaefer@ipv6.social

                                            [?]Thomas Schäfer » 🌐
                                            @tschaefer@ipv6.social

                                            "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."

                                            🙏

                                            documents.swisscom.com/product

                                            community.swisscom.ch/de/d/861

                                              [?]Thomas Schäfer » 🌐
                                              @tschaefer@ipv6.social

                                              bei der :

                                              ...Start für die breite Kundenbasis ist aktuell für die zweite Hälfte 2026 geplant.

                                              🙏

                                              community.swisscom.ch/d/861354

                                              Hallo zusammen

Danke für die spannende Diskussion und eure aufmerksamen Beobachtungen zu den Device-Konfigurationen. Ich habe bei unseren Netzwerkspezialisten nachgefragt:

"Die technische Basis: Mit dem neuen 5G Core legen wir das Fundament für IPv6. Damit wird unser Mobile-Angebot mittelfristig “IPv6-first” – die Weichen sind gestellt.

Was ihr beobachtet habt: Einige von euch haben die Änderungen in den APN-Einstellungen (IPv4v6) schon bemerkt. Das sind Vorbereitungen auf die Migration, die schrittweise erfolgt – Angebot für Angebot. Start für die breite Kundenbasis ist aktuell für die zweite Hälfte 2026 geplant.

Warum IPv4 vorerst “preferred” bleibt: Obwohl der neue Core und die Geräte IPv6 beherrschen (Dual Stack), hat die Stabilität Vorrang. In internen Tests haben wir gesehen, dass gewisse Business-Applikationen (z.B. ältere VPN-Clients) Probleme machen, wenn IPv6 priorisiert wird. Deshalb starten wir mit IPv4 als “preferred”. Euer Gerät kann beide Adressfamilien nutzen, erhält aber bevorzugt IPv4 – ausser ihr forciert IPv6 von der Geräteseite her. Langfristig wollen wir den Traffic auf IPv6 heben, aber nur wenn die Kompatibilität im Feld stimmt.

Kurz: Die Technik ist ready, wir rollen 2026 gestaffelt aus, bleiben aber bei der Priorisierung konservativ"

Gruss

StefanP

                                              Alt...Hallo zusammen Danke für die spannende Diskussion und eure aufmerksamen Beobachtungen zu den Device-Konfigurationen. Ich habe bei unseren Netzwerkspezialisten nachgefragt: "Die technische Basis: Mit dem neuen 5G Core legen wir das Fundament für IPv6. Damit wird unser Mobile-Angebot mittelfristig “IPv6-first” – die Weichen sind gestellt. Was ihr beobachtet habt: Einige von euch haben die Änderungen in den APN-Einstellungen (IPv4v6) schon bemerkt. Das sind Vorbereitungen auf die Migration, die schrittweise erfolgt – Angebot für Angebot. Start für die breite Kundenbasis ist aktuell für die zweite Hälfte 2026 geplant. Warum IPv4 vorerst “preferred” bleibt: Obwohl der neue Core und die Geräte IPv6 beherrschen (Dual Stack), hat die Stabilität Vorrang. In internen Tests haben wir gesehen, dass gewisse Business-Applikationen (z.B. ältere VPN-Clients) Probleme machen, wenn IPv6 priorisiert wird. Deshalb starten wir mit IPv4 als “preferred”. Euer Gerät kann beide Adressfamilien nutzen, erhält aber bevorzugt IPv4 – ausser ihr forciert IPv6 von der Geräteseite her. Langfristig wollen wir den Traffic auf IPv6 heben, aber nur wenn die Kompatibilität im Feld stimmt. Kurz: Die Technik ist ready, wir rollen 2026 gestaffelt aus, bleiben aber bei der Priorisierung konservativ" Gruss StefanP

                                                [?]Nivex 🐧 📻 [he/him] » 🌐
                                                @nivex@tenforward.social

                                                Just had to manually enter a mirror with working since @armbian 's automatic redirector still sends me to mirrors that have AAAA records but don't answer.

                                                  [?]Nico -telmich- Schottelius » 🌐
                                                  @nico@ipv6.social

                                                  RE: mastodon.social/@rickvanrooije

                                                  More work needed - things are moving forward!

                                                    [?]Thomas Schäfer » 🌐
                                                    @tschaefer@ipv6.social

                                                    Amazon MSK now supports dual-stack (IPv4 and IPv6) connectivity for existing clusters
                                                    Posted on: Feb 17, 2026

                                                    aws.amazon.com/about-aws/whats

                                                      [?]Richard "RichiH" Hartmann » 🌐
                                                      @RichiH@chaos.social

                                                      @T_X @axx so for 2027, I had another stupid idea everyone insisted was good: it will be -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 is not on v6 by next year, trust me, they will put _something_ in place very quickly.

                                                        [?]Richard "RichiH" Hartmann » 🌐
                                                        @RichiH@chaos.social

                                                        @tschaefer @T_X @axx rumor has it, saw my announcement. Including the helpful offer to CNAME to which supports

                                                          [?]Pete Keen » 🌐
                                                          @zrail@hachyderm.io

                                                          Very quietly I have transitioned substantially all of my services to exclusively over the past few days.

                                                          No drama. No performance regressions. Just a lot more flexible and resilient.

                                                          I think the next big-ish project is upgrading all of the devices and enabling ipv6.

                                                          @homelab

                                                            [?]Erik Nygren :verified: » 🌐
                                                            @nygren@hachyderm.io

                                                            My friend and colleague Kyle Rose developed a vastly better PCRE regexp for matching addresses than the top answer on stack overflow:

                                                            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.

                                                            Code containing:

ipv6_valid_re = \
    r'^(?!.*?(::.*?::|:::))' + \
    r'(?!:[^:])' + \
    r'(?!.*[^:]:$)' + \
    r'(?=(:?[^:]*?(:[^:]*?){7}:?|' + \
    r'(?=.*?::)[^:]*?(:[^:]*?){2,6})$)' + \
    r'([0-9A-Fa-f]{0,4}::?){0,7}([0-9A-Fa-f]{0,4})$'

                                                            Alt...Code containing: ipv6_valid_re = \ r'^(?!.*?(::.*?::|:::))' + \ r'(?!:[^:])' + \ r'(?!.*[^:]:$)' + \ r'(?=(:?[^:]*?(:[^:]*?){7}:?|' + \ r'(?=.*?::)[^:]*?(:[^:]*?){2,6})$)' + \ r'([0-9A-Fa-f]{0,4}::?){0,7}([0-9A-Fa-f]{0,4})$'

                                                              [?]hallunke23 🇺🇦:nona: » 🌐
                                                              @hallunke23@troet.cafe

                                                              I have to admit that I'm not fluent in regex.

                                                              As you may know, the last four bytes of an IPv6 address can be written in decimal.

                                                              I have to admit that I'm not fully fluent in regex but I would like to point out that to me, it looks like your regex doesn't include that option.

                                                              @nygren

                                                                [?]Nivex 🐧 📻 [he/him] » 🌐
                                                                @nivex@tenforward.social

                                                                I really wish @matrix would go ahead and kill their Bifrost instance rather than leaving it in its current zombie state where it's keeping an s2s connection (over legacy IP no less) open to me but not doing any actual bridging.

                                                                  [?]BjoernAusGE » 🌐
                                                                  @bjoern@social.sengotta.net

                                                                  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

                                                                    [?]Anderson Silva » 🌐
                                                                    @UnderEu@mas.to

                                                                    @cloudflare Could you help your customer to fix their connectivity by not disabling on websites they host?

                                                                      [?]John W. O'Brien [he/him/his] » 🌐
                                                                      @neirbowj@mastodon.online

                                                                      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?

                                                                        Back to top - More...