#legacyip — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #legacyip, aggregated by home.social.
-
Jetzt kommt auch noch eine deutliche Preissteigerung hinzu.
Schade!
4/4
-
Jetzt kommt auch noch eine deutliche Preissteigerung hinzu.
Schade!
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 -
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 -
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
-
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
-
@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 -
@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 -
#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
2141 are #DualStack and have working inbound #IPv6
Way to go.
-
#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
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.
-
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.
-
> 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
-
> 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
-
A bold suggestion for the carriers/ISPs and website operators that care about the internet:
Communicated BROWNOUTs for #LegacyIP connectivity?
Starting with 1h/week during off peak and moving from week to week and increasing in frequency and length.
-
A bold suggestion for the carriers/ISPs and website operators that care about the internet:
Communicated BROWNOUTs for #LegacyIP connectivity?
Starting with 1h/week during off peak and moving from week to week and increasing in frequency and length.
-
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.
-
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.
-
@mho
Sieht halt nur das Fediverse mit #LegacyIPDas Fediverse ist viel grösser!
-
@mho
Sieht halt nur das Fediverse mit #LegacyIPDas Fediverse ist viel grösser!
-
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?
-
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?
-
@rapha3l @kuketzblog
Es wird definitv besser und IoT welches nur #LegacyIP spricht, darf bei mir nicht rein. 😉Leider nutzen die IoT Geräte mit #IPv6 oft die #EUI64 Address Generations Methode und senden damit einen eineindeutigen Identifier.
Ich hatte bei einigen Herstellen, welche ich selbst verwende, Erfolg und sie haben nachgebessert.
Selbst #Nintendo kann es mittlerweile.
Wie könnte man hier ein generelles Requirement in EU daraus machen?
Es steht nicht explizit in der #GDPR drin. -
@rapha3l @kuketzblog
Es wird definitv besser und IoT welches nur #LegacyIP spricht, darf bei mir nicht rein. 😉Leider nutzen die IoT Geräte mit #IPv6 oft die #EUI64 Address Generations Methode und senden damit einen eineindeutigen Identifier.
Ich hatte bei einigen Herstellen, welche ich selbst verwende, Erfolg und sie haben nachgebessert.
Selbst #Nintendo kann es mittlerweile.
Wie könnte man hier ein generelles Requirement in EU daraus machen?
Es steht nicht explizit in der #GDPR drin. -
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.
-
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.
-
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
-
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:
-
Wieso zeigt einem denn die FritzBox die Ipv4 Einstellung von Heimgeräten nicht immer an, selbst wenn eine Mac-Adresse bekannt ist :blobcatwhat:
-
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.
-
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...
-
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...
-
-
-
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
-
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
-
Why #github sucks: Error: Get "https://github.com/kubernetes/ingress-nginx/releases/download/helm-chart-4.9.0/ingress-nginx-4.9.0.tgz": dial tcp 140.82.121.3:443: connect: network is unreachable #LegacyIP
