Just for grins I stood up nginx in my #FreeBSD test VM to see how it played. The stock config only has a "listen 80;" which means IPv4 only. Would be nice if they'd add a "listen [::]:80;" as other distros have done so it answers on the modern Internet out of the box.

#ipv6

@FoxVK
I have to respectfully disagree.
IPv6 is easier, yes different, performing better and give one end to end connectivity.
Furthermore it enables things which are not possible with legacy IP.
Living in a #IPv6 first country, this is obviously to me.
@nivex

At the brink of #CLAT on the desktop, this allows for #IPv6mostly access networks.

But on the other hand it will mask over #IPv6 issues as there is the Legacy IP fall back.

How do you think about this?

Using the #hotel #wifi powered by m3connect. What is not working is the current Internet protocol. #IPv6
Therefore I cannot access most of the services I would like to use.

#hotelwifi #fail

Alt...

Herzlich willkommen im ... Hotel. kostenloses Premium WLAN powered by m3connect

@goetz So far I can count on ONE FINGER the number of Public Wi-Fi Hotspots that are using actual Internet standards a.k.a. #IPv6 , which is the United Airlines' In-flight Wi-Fi service powered by Starlink.

If the commercial airline industry, which is not synonymous to cutting-edge technology adoption (even though we're talking about a 30-year-old Internet standard), are already figuring this out... that's something network administrators need to think about.

@nivex
Thanks for the post.
You may want to use/add https://webres6.dev.sap the next time you do this.

#IPv6

#swisscom #ipv6 #5g #mobile #internet #schweiz

IPv6-Umstellung für ein stabileres und schnelleres Mobilnetz

(es wird konkret)

https://www.swisscom.ch/de/privatkunden/hilfe/mobile/ipv6.html
https://www.swisscom.ch/en/residential/help/mobile/ipv6.html
https://www.swisscom.ch/fr/clients-prives/aide/mobile/ipv6.html
https://www.swisscom.ch/it/clienti-privati/aiuto/mobile/ipv6.html

#ipv6
#Switzerland
#swisscom
#paper
#46pages ( 4 6 😉)

https://www.swisscom.ch/en/business/enterprise/downloads/IoT/essentials-for-it-and-business.html

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

🙏

#swisscom #ipv6 #internet

https://documents.swisscom.com/product/filestore/lib/f54387a7-c678-4d10-a947-297cda4b1611/20250224_whitepaper_soc_stand_20250320_1.pdf

https://community.swisscom.ch/de/d/861354-ipv6-via-5g

#IPv6 bei der #Swisscom :

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

🙏

https://community.swisscom.ch/d/861354-ipv6-via-5g/17

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 Before anyone asks "well, why don't you simply get your employer to deploy #IPv6?":

I barely started[1] reading about #IPv6 (thanks to https://burningboard.net/@Larvitz/116715786158271334) and I already have a question:

I handle the DHCP server in my local network. It assigns IPv4 addresses based on MAC address (yes, I know they're spoofable). So even if they managed to get into the network, it would be slightly hard to guess the IP range and default gateway (no, it's not X.Y.Z.254 or .1 :)

[1] technically, I read about it a loooong time ago, and never used it, so I don't remember anything.

1/

@mdione @goetz @claushc Here's my #IPv6 primer for people with a technical background:

https://nygren.org/projects/ipv6/inessential-ipv6.pdf

(also at https://docs.google.com/document/d/1WohukYWdlFcEaSm-SQtX5Zgrkr-FZiZnfhlvoFi5Bl0/edit?tab=t.0#)

Some year I'll move it to some other format.

@packetcat heh, I closed my account with them in February and made sure to let them know it was because they don't do #IPv6.

New FPT blog post: No IPv4 Day Revisited
https://blog.flyingpenguintech.org/2026/07/no-ipv4-day-revisited.html

#IPv6

@FoxVK I respectfully disagree. To start over would be to throw away the years it has taken to get the #IPv6 stack tested and integrated into countless operating systems.

After every talk I have given at a conference nearly everyone who speaks with me afterward says it was less difficult than they anticipated. IPv6 is no less confusing than any other protocol. It is just different than the IPv4 some people are used to.

IPv6 is practical today. I already use it on my mobile to communicate with servers running at my house without any extra layers.

The solution is not to start over. The solution is to finish the job.

@Unlikelylass Hopefully USI having been bought out by T-Mobile means the latter will be bringing their #IPv6 resources to the table.

https://www.internetsociety.org/blog/2013/12/campaign-turn-off-ipv4-on-6-june-2014-for-one-day/

We need to do this again. Next year will be the 15th anniversary of World IPv6 Launch day and the 10th anniversary of RFC 8200 making #IPv6 a formal standard.

@tschaefer As I'm in the process of setting up my own Auth Nameserver
I say yes. If one wants to know the PTR record of my #IPv6 addresses, it should be IPv6 capable.

Is It Time for IPv6-Only Authoritative DNS?

https://datatracker.ietf.org/meeting/124/materials/slides-124-iepg-sessa-ipv4-and-ipv6-only-root-servers-00

https://m.youtube.com/watch?v=tUth7lFrlIA

He works for the same company ( IBM NS1 Connect ) that still doesn't talk to its customers about silly AAAA records.

#ripe91 #ietf124 #internet #dns #ipv6 #ibm #aaaa

Alt...

fastly-tls12-bam.nr-data.net. TTL=1654 AAAA ::ffff:162.247.243.29 (not authoritative)

Alt...

nr-data.net. TTL=14400 NS dns2.p07.nsone.net. (not authoritative) nr-data.net. TTL=14400 NS ns03.nr-dns.net. (not authoritative) nr-data.net. TTL=14400 NS dns3.p07.nsone.net. (not authoritative) nr-data.net. TTL=14400 NS ns04.nr-dns.net. (not authoritative)

I was chasing down the host of a website and came across this document: https://www.liquidweb.com/vps/ipv6-vs-ipv4/

This feels pretty poorly written. It basically says you only need IPv6 under certain circumstances rather than indicating it's a transition in progress. Perhaps someone who is a more prolific writer could engage them to refine this document.

#IPv6

@UnderEu Probably better to focus on websites and hosters themselves and perhaps validation tools they use. We can circle back to test-ipv6.com itself once being #IPv6-only is considered less bold.

If you use https://aaaa.test-ipv6.com/ to run a test from an #IPv6-only network you receive the message:

> You appear to be able to browse the IPv6 Internet only. You have no access to IPv4. That's pretty bold!

14 years after World IPv6 Launch, I say it's time to flip that narrative. "Your site is only available on the Legacy Internet? That's pretty bold!"

@Mojeek Wonderful! I look forward to your service being reachable on #IPv6.

$ host -t AAAA mojeek.com
mojeek.com has no AAAA record
$ host -t AAAA www.mojeek.com
www.mojeek.com has no AAAA record

My final #IETF draft submission for the day -- this one being #IPv6 related!

"Indicating IPv6-only SVCB Endpoints and IPv4 Deprecation in the DNS"

https://datatracker.ietf.org/doc/html/draft-nygren-dnsop-ipv6only-indicator-00

(Likely for @ietf_wg_dnsop given it is extending #DNS #SVCB, although it ties into v6ops and happy as well.)

Abstract: As the DNS is the primary mechanism for translating from hostnames to IP addresses, it is a logical place to signal that endpoints are IPv6-only. It is thus also a logical place to signal that legacy endpoints supporting IPv4 are being deprecated. This specification introduces two SvcParams for SVCB-compatible RR types that signal IPv6-only endpoints ("ipv6only") as well as deprecated endpoints ("deprecated").

#sunset4 #ToTheUniversalDeprecationOfIPv4

@nuintari I'm trying to be charitable, since I think it's something worthwhile to develop and use, precisely because it's bringing new blood and ideas. All the same though, they're not going to rival IEEE 802.3 anytime soon.

That said, I wish 802.11ah HaLow hardware was more available, because that could probably support a full-and-proper #IPv6 mesh network. On nodes running a POSIX-compatible RTOS. With blackjack and OS-hooks!

@existentialcomics Any chance we can get #IPv6 enabled on existentialcomics.com? I see it's hosted on DigitalOcean, which I know supports it, but I don't know if there's another service between you and them.

@thomas looks great from my vantage point.

But ns2.core-networks.eu is not responding on #IPv6 UDP?

There's something a bit ironic about a site called Futurism not having #IPv6.

What happened to kame.net?

There's no 🐢

#IPv6

Enshittified search is letting me down. I'm trying to find a reference to a quote that's something like "You don't really run #IPv6 until you turn off IPv4."

https://cfp.tuebix.org/tuebix-2026/talk/KE83VF/

#ipv6 #tubix2026

@M0YNG Getting a connection refused on the #IPv6 side (v4 is working).

How many times has #NAT actually died because of #IPv6 by now? 🤔😁
https://packetpushers.net/podcasts/ipv6-buzz/ipb203-the-death-of-nat/

Alt...

https://packetpushers.net/podcasts/ipv6-buzz/ipb203-the-death-of-nat/

Was will mir diese Firma mitteilen?

Kann mir das jemand in Saarländer umrechnen?

#ipv6 #blödsinn

https://zalman-it.de/partner

Alt...

Feste IP-Adressen DA: 48 × IPv4 + 0,5 Septillionen IPv6. RE: 170 × IPv4 + 1,4 Septillionen IPv6. Alle DDoS-geschützt.

For the first time in my life, my home internet is faster than the connection on my datacenter servers. For once, the bottleneck isn't here, it's there.

Meaning, I can self-host stuff right here at the same speed as over there.

And I already have a couple of ideas on WHAT to host, on top of what I'm already running (and more efficient backups, obviously).

It's just a shame about the quality of the installation work. Seriously, unbelievable. Outside, the fiber cable wasn't even properly secured; it's just dangling off the wall with a couple of zip ties in the most pathetic way. If someone walks by on the inner pavement, they could easily snap it.

I'll have to take some time and try to fix it myself... but overall, the outcome is still extremely positive.

And finally, I have native IPv6, without needing any more Tunnel Brokers.

#FTTH #ipv6 #WeNeedMooarIPV6