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

[?]Nivex 🐧 đŸ“» [he/him] » 🌐
@nivex@tenforward.social

If you are an ARRL member, could you nudge them to enable their ?

$ host -t AAAA www.arrl.org
www.arrl.org has no AAAA record

    [?]Alex [he/him] » 🌐
    @alexhaydock@infosec.exchange

    No NAT November shaping up nicely this year :neocat_laptop:

    On a fresh out of the box install of Win 11 it only takes one command and a reboot to enable WinCLAT:

    ```
    netsh.exe interface clat set global permit=enabled
    ```

    Screenshot of a Powershell window showing the Windows CLAT enabled on a host. Full output below:

```
PS C:\> netsh.exe interface clat show global
------------------------------------
permit                 : enabled
pref64fromdns          : enabled
pref64fromra           : enabled
autoenable             : enabled
store                  : active

PS C:\> netsh.exe interface clat show instance interface=Wi-Fi
-----------------------------------------------------------
State                            : enabled
Is translating                   : yes
Local prefix                     : 2001:8b0:xxxx:xxxx::/64
Remote prefix                    : 2001:8b0:6464:0:66::/96
Remote prefix remaining lifetime : 27m50s
IPv6 address                     : 2001:8b0:xxxx:xxxx:a226:78fa:d01f:a295
IPv4 address                     : 192.0.0.1
```

    Alt...Screenshot of a Powershell window showing the Windows CLAT enabled on a host. Full output below: ``` PS C:\> netsh.exe interface clat show global ------------------------------------ permit : enabled pref64fromdns : enabled pref64fromra : enabled autoenable : enabled store : active PS C:\> netsh.exe interface clat show instance interface=Wi-Fi ----------------------------------------------------------- State : enabled Is translating : yes Local prefix : 2001:8b0:xxxx:xxxx::/64 Remote prefix : 2001:8b0:6464:0:66::/96 Remote prefix remaining lifetime : 27m50s IPv6 address : 2001:8b0:xxxx:xxxx:a226:78fa:d01f:a295 IPv4 address : 192.0.0.1 ```

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

      Oh my god.. why is really so so so so broken? Yes, some parts of github now have , but their container registry does not. Must be a really bad (as in complex) infra, if it takes that long to enable IPv6 everywhere.

        Tom :damnified: boosted

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

        VPS hoster with proper support and reasonable prices recommendations?

        I'm really happy with and but haven't found a similar offering in AMS region.

        Any recommendations?

        requirements:
        /64
        PTR records in management interface
        management UI with support
        <5€/month (1vCPU/1GB RAM)

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

          [?]ariel » 🌐
          @arichtman@eigenmagic.net

          AWS's IAM OIDC feature only attempts discovery over IPv4. Guess who found out after an hour of debugging?

          Really no reason for such a limitation...

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

            Wir schreiben das Jahr 2026. Ganz Europa ist ĂŒberwiegend ein Land. Die Adressen fließen in Strömen, die Netze sind stabil, die Latenzen gering. Die Welt dreht sich weiter – bis auf ein kleines, stures Dorf in den Alpen. Dort, tief in den Bergen, liegt Geizhals.

            WĂ€hrend ganz Europa auf moderne Protokolle umgestellt hat, weigert sich das Dorf, Schritt zu halten.

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

              Asterix steht im Dorfplatz, die Arme verschrĂ€nkt, und brĂŒllt: „Wir lassen uns nicht von diesen neuen Kram einlullen! Wir bleiben bei unserem bewĂ€hrten fĂŒr unsere Nameserver!“

              Obelix stampft mit dem Fuß auf und hĂ€lt einen alten Router hoch: „Und wir nutzen weder IPv6 fĂŒr gh.de noch fĂŒr gh.at! Das ist doch alles nur Schnickschnack! Wir sind das kleine gallische Dorf der digitalen UnabhĂ€ngigkeit – und wir lassen uns nicht von der Moderne abhĂ€ngen!“

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

                Mit einer SIM der in der Schweiz, also im Netz der Swisscom, kann man / haben.

                Der gemeine Schweizer darf allerdings noch nicht verreisen.
                Bei Roaming klappt dieser "Trick" nicht.

                
IP-Adresse
2a02:1217:50b8:fc00:eb5e:1
452:799b:900b
192.0.0.4

                Alt... IP-Adresse 2a02:1217:50b8:fc00:eb5e:1 452:799b:900b 192.0.0.4

                APN Einstellungen sind manuell auf IPv6 zu stellen

                Alt...APN Einstellungen sind manuell auf IPv6 zu stellen

                  [?]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

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

                      [?]Florian 'floe' Echtler » 🌐
                      @floe@hci.social

                      It has been __0__ days since I had to fix a networking issue by disabling IPv6. In 2026. 🙄

                        [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                        @nivex@tenforward.social

                        @streetcomplete Can you please enable on your website streetcomplete.app/ ?

                          [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                          @nivex@tenforward.social

                          @becomingwisest The registration process is largely the same for IPv4 and IPv6 nowadays. You, the officer of some organization (ARIN at least won't "sell" to individuals), call up your RIR, jump through some hoops, and pay them money every year for the pleasure. ARDC seems like the best fit to do this for IPv6 since they have already done this for 44Net.

                          The trouble is IPv6 space would be an _additional_ cost on top of the existing IPv4 registration. The other elephant in the room is with most of the commercial Internet moving to encrypted protocols by default, having a direct interface with a radio network where such is not permitted (at least here in the US) seems kinda pointless. As such I wonder about the future of 44Net, let alone trying to get a modern allocation.

                          Since most ham radio networks thus tend to be islands connected by tunnels, if there is any actual interest in IPv6, it probably makes sense to use ULA space. Between 44Net, RFC1918, and a lot of legacy gear there's little incentive to move. Which is kinda sad since we used to be drivers of technology, but I digress.

                          This is merely my opinion, so if someone wants to try to work with ARDC (or some other group) to do it anyway, please don't let me stop you.

                            [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                            @nivex@tenforward.social

                            The headline on the 44Net Connect website is "Next-Generation Digital Amateur Radio Infrastructure". How can it be next generation when it's still using a protocol from 40 years ago and the replacement protocol was first specified 30 years ago?

                            It's especially mind-boggling for me because I was using 44Net over the air back then. It's how I learned TCP/IP, and in some ways I owe that my career. But how is rehashing all of this an advancement of the state of the art?

                              [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                              @nivex@tenforward.social

                              For whatever reason I think of RFC 2460 as the first spec and forget about RFC 1883.

                                [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                                @nivex@tenforward.social

                                My state board of elections serves its sample ballots in Amazon S3, so the link is to s3.amazonaws.com. This endpoint is legacy-only. If I manually change it to s3.dualstack.us-east-1.amazonaws.com I get the desired object.

                                Why is the default endpoint not dualstack?Âč RFC 6540 was 16 years ago!

                                docs.aws.amazon.com/AmazonS3/l

                                Âč This is a rhetorical question. I don't want it answered, I want it fixed.

                                  [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                                  @nivex@tenforward.social

                                  I know the-powers-that-be have been pushing away from DNS64 for awhile now, but this change forces the use of CLAT on NAT64 networks. I don't like having my hand forced like this. NetworkManager's BPF CLAT won't hit until the next release so now I gotta manually start my Jool based CLAT for everything. Also Happy Eyeballs will paper over configuration issues I've been finding and reporting.

                                    [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                                    @nivex@tenforward.social

                                    Oh this is no bueno: Firefox 153 is detecting some (but not all) of my ULA NAT64 as "Local network device access", which of course I click block on because I'm paranoid. The weird thing is it seems to only be doing it if the main site is coming in on but other resources are legacy.

                                      [?]Chris 🏃 🐧 🔜 #40c3 » 🌐
                                      @cr@chaos.social

                                      Someone gonna be at RIPE 93 in Sofia? I’m not really into RIPE these days – still have address space and use it – so I’m sitting on the fence whether I should get tickets or not.
                                      Either way, happy to meet up for a coffee or dinner!

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

                                        @nivex
                                        @miyuru cloud you remove all dyndny hosts please e.g., *.ipv64.* duckdns.org

                                          [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                                          @nivex@tenforward.social

                                          This list is getting longer not shorter v6check.miyuru.lk/failed

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

                                            Is someone at the

                                            5th IPv6 Council Meeting
                                            8th - 9th October 2026 ‱ New Delhi, India

                                            Their website is still not reachable consistently over

                                            I have mailed the sysadmins and info address multiple times but to no result.

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

                                              @plzupgrademe Mobile and/or land service?

                                              Bell Mobile has but not their broadband land service, for some reason;
                                              EBOX & Cogeco claim to have v6 working but I can't check on them atm;
                                              In QC, Videotron has v6 but, for some another reason, you have to file a ticket and ask them to fix it not working out-of-the-box.

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

                                                Notiz an mich selbst:

                                                Es heißt >Traffic Rules< in openwrt. Traffic Rules nichts anderes!

                                                Nicht bei Port Forward hÀngen bleiben!

                                                  [?]Nivex 🐧 đŸ“» [he/him] » 🌐
                                                  @nivex@tenforward.social

                                                  RE: social.coop/@cwebber/117326833

                                                  The problem is what I've been focused on, , is something people have been fighting me on for 15+ years now. So the latest attacks on anything else I enjoy in tech just saps what little energy remains.

                                                  [?]Christine Lemmer-Webber » 🌐
                                                  @cwebber@social.coop

                                                  I actually think there are a lot of reasons to be optimistic about technology, if you ignore the latest trends and focus on what you would be doing if all the things that weren't making you depressed weren't flooding your windshield

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

                                                    Amazon EMR on EKS now supports IPv6 Amazon EKS clusters
                                                    Posted on: Sep 23, 2026

                                                    aws.amazon.com/about-aws/whats

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

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

                                                      Sitze gerade in einem neuen WLAN, im neuen Gewerkschaftshaus von MĂŒnchen.

                                                      Service ist irgendwas mit
                                                      "Sodexo", die Technik kommt wohl von "Rohde & Schwarz Networks and Cybersecurity GmbH" (ehemals lancom)

                                                      Die IPv4 Adresse aus dem AS3320.
                                                      Und was ist nicht da?
                                                      Ich könnte 😡

                                                        [?]:loup: Shalien » 🌐
                                                        @shalien@mastodon.projetretro.io

                                                        I really love that enabling on the server also broke all android apps I use to access mastodon

                                                          [?]equinox [he/him] » 🌐
                                                          @equinox@chaos.social

                                                          codeberg.org/eqvinox/nss_dns64

                                                          DNS64 / in glibc's NSS


                                                          
why did I have to hack this together? It seems so obvious
 but I couldn't find anything

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

                                                            Back to top - More...