#legacyip — Public Fediverse posts

@phils
Yes totally agree and appreciate #webres6

For nameservers and resolvers we now have #RFC10001 by @tfiebig and co authors.
Which should work without glue records.

But I assume we all look towards the day where #RFC10001bis is ready and one can drop #LegacyIP support.

@jtk

@jtk
Thank you.
I was trying to point out why
the #webres6 testing does not pick them up due to #IPv6-only-strict preset of the testing resolver.
As confirmed by Philipp.

To add, one needs a #legacyip resolver for #fastly until this is fixed.
Tooling like #webres6 helps finding those issues.

@YvanDaSilva
Just cancelled my mobile contract due to #CGNAT and #legacyip only.

@chaz6 Thank you for the recommendation.

Unfortunately that site is #LegacyIP only.
https://webres6.dev.sap/#report:6a81551d-e116aff66569977f45df56706d18c335c6af8fa1ca3ef26dc479aeecf34a7f83-10d0895b605d

BTW @Hasso_Plattner_Institute

You TLS cert of the mastodon instance is expired.

@wutti
Viel Erfolg bei der Portierung.

Ich hoffe du hast keinen Bedarf an aktuellem Internet. #IPv6 ist dort nicht vorhanden.

#CGNAT #LegacyIP

#Mozilla assets on GCP #LegacyIP only.

```
dig +short assets-prod.sumo.prod.webservices.mozgcp.net
34.110.220.139
```

@vicorva
Maybe ditch Stripe altogether, as they still live in 1998

All your customers hide behind CGNAT and such at least in Europe.

#LegacyIP
#NoIPv6

@mailbox_org @heinleinsupport

Jetzt kommt auch noch eine deutliche Preissteigerung hinzu.

Schade!

#LegacyIP
#ipv6

4/4

Hotel in AT, Wifi #LegacyIP only.
Schaut man nach dem ISP #AS8445 bei Cloudflare oder APNIC

#IPv6 < 0,1%

Schade

https://radar.cloudflare.com/as8445#adoption-usage
https://stats.labs.apnic.net/ipv6/AS8445?c=AT&p=1&v=1&w=30&x=1

@miyuru

Their management is still #LegacyIP therefore still a no go for me.

My FR to this topic has been open since ....

https://github.com/issues/created?issue=ovh%7Chosting-domain-names-roadmap%7C84

#OVH #IPv6 #S3 #objectstorage

@funz
Mailbox hat ein #LegacyIP Problem.
Ich habe kein/will kein LegacyIP benutzen. Als ich Kunde geworden bin, war ausser KnowledgeBase alles #IPv6.
Heute ist nur noch IMAP und SMTP darüber erreichbar. Alles andere relevante ist #LegacyIP es ist entsprechnd schlecht erreichbar. Den bei deutschen ISP gibt es das nur noch as-a-Service. Wir sind bei >75% #IPv6 in DE und damit unter den TOP5 Länder weltweit. Ein letztes Thema wo wir noch vorne sind.
@mailbox_org

My router lost its #legacyip connectivity for a couple of hours. No one noticed, only when my partners #PaloAlto VPN would not connect it popped up because it only uses #legacyip.

#Fediverse
I checked 4160 fediverse instances for their connectivity.

- A / AAAA record persent
- Reachabliltiy over #IPv6 if AAAA present.

107 Instances announce AAAA records but have broken inbound IPv6

1909 are #LegacyIP #IPv4only

2141 are #DualStack and have working inbound #IPv6

Way to go.

Unterkunft mit #Hotsplots #WLAN
Dreimal dürft ihr raten was es nicht gibt? ... Richtig Zugang zum Internet. Es wird nur #LegacyNet Zugang angeboten.

Schade! Den da man nicht mal eine Allocation hat. Scheint man das nicht für wichtig zu halten.

#AS210070 #LegacyIP #NoIPv6

> From 2014 to 2018, he allegedly arranged for more than 250 metric tonnes of networking equipment to be illegally sent to Iran.

Never in my life have I thought that the *mass* of networking equipment needed to be totaled up, except maybe to load a moving vehicle.

How do I convert metric tonnes to Tbps? Does #IPv6 weigh more than #LegacyIP ? /s

Asked the other day, now the first one is trying it out on the services side:

https://pacific.ipv6forum.com/

Using the Czech IPv6-Only Day of the year as a reference.

#ietf

#LegacyIP #DENOG #RIPE #LegacyIP

@mho @daniel

Man sieht deinen Account bzw. social.heise.de nicht aus den Internet mit aktuellem Protokoll. Damit kann man mit deinem Account nicht interagieren.

Denn social.heise.de ist nur auf #LegacyIP erreichbar.

Viel schlimmer sind Instanzen wie @Mastodon denn diese sieht man zwar, aber man kann nicht mit ihnen Interagieren z.B. Folgen weil der Request (Ausgehende IPv6 Verbindung) nicht möglich.

1/2
@[email protected]

If I understand #SCTP multihoming correctly, in a multi-WAN scenario, it would likely suck on #LegacyIP because internal hosts usually don't have a NAT44 address routed through each ISP.

But on #IPv6, multiple addresses is the norm and I think an RA could advertise every ISP's IPv6 prefix, allowing hosts to be aware of their public IPs, thus do sensible SCTP multihoming.

That sounds awesome! What am I missing, besides application support for SCTP?

Today's #IPv6 tip: try pinging ff02::1 on an interface to get responses from every host on that network. Really useful for point-to-point links, where it can be used to discover the remote end's link-local address, and then SSH into it.

In the context of "getting an IP to SSH in", this is categorically better than the #LegacyIP approach of writing down an IP or trying to memorize it.

That's right, it goes into the IPv4 hole!

#ipv6 #legacyIP

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

Wieso zeigt einem denn die FritzBox die Ipv4 Einstellung von Heimgeräten nicht immer an, selbst wenn eine Mac-Adresse bekannt ist :blobcatwhat:

#FritzBox #Networking #IPv4 #LegacyIP

Why is this turned OFF by default?! :blobcattableflip:

#OPNSense #IPv6 #IPv4 #LegacyIP #DynDNS

it drives me crazy: Error: Get "https://github.com/kubernetes/ingress-nginx/releases/download/helm-chart-4.13.3/ingress-nginx-4.13.3.tgz": dial tcp 140.82.121.4:443: connect: network is unreachable Stupid #github still #legacyip - so annoying.

The worst film I've seen this year -- War Of The Worlds (2025) -- also only uses #LegacyIP addresses rather than #IPv6 . But truth be told, that wouldn't have salvaged the cringe-fest which my poor ears and eyes had to suffer through.

I am not left trembling in shock and fear like H.G. Wells' original work would have done, but rather I'm stunned by the bad cinematography and poorly-done "modern day" framing.

Then to make it even worse, the Teams notification sound plays throughout the film...

NAT NAT #NAT64 for #GPN23 #AS 215185

#IPv6 #LegacyIP #IPvLegacy

What Docker did was to intellectually limit the creativity that users could have had with containers, funneling everyone into the most trivial of network use-cases. When everything is server-client, it's really hard to develop peer-to-peer or avant guard applications.

The parallels to #LegacyIP and #NAT are staggering, as they too stymied progress in other, not-yet imagined scenarios. #IPv6 should have been the go-to for hyperscalar from day-one. That it wasn't is forever a travesty.

7/n

Not ready for primetime.

+ messengers (iMessage, Signal, Threema, Matrix) work fine
+ most bigger websites work

- other daily used websites are not working (e.g. GitHub)
- some apps are not working
- #Viessman ViCare App (Heatpump)
- #Tibber
- #SMA (PV)
- some streaming apps on AppleTV are not working

#LegacyIP #IPv4 #IPv6 #HomeLab #OPNsense