@xmpp FYI providers.xmpp.net/ is not answering on #IPv6 . This is making it difficult to reach you for those of us without a clean fallback to legacy IP.
IPv6 Adoption: A Global Shift
Since its standardization in the late 1990s, IPv6 has steadily gained traction. The last 15 years, especially since World IPv6 Launch Day in 2011, have seen significant progress.
I really wish that Atlassian's status page service was dual-stacked and enabled #IPv6.
Community forum thread, or if you're a customer you can encourage them through a support ticket and reference "STATUS-512" (which I assume is a Jira ticket 😉).
Since services like akamaistatus.com/ and cloudflarestatus.com/ explicitly don't want to use their own CDNs for this (to allow status reporting during outages) this results in these status pages being IPv4-only resources outside of their control.
I guess I should post a link to the recording of my #DENOG17 talk, in case anyone needs a downer with the poor state of #IPv6 multihoming 😅 media.ccc.de/v/denog17-78841-i…
Interesting post by Cloudflare on detecting #CGNAT as well as the performance and availability impacts to users behind it: blog.cloudflare.com/detecting-…
This re-enforces the importance for both: 1) content providers to dual-stack sites (so that #IPv6 end-users can bypass CGNAT) 2) the importance for networks to deploy IPv6 alongside CGNAT so that only a shrinking subset of traffic needs to go through CGNAT
Of particular concern is the concentration of CGNAT in the developing world, creating even more risk of a multi-tier Internet with an IPv6-centric modern internet but with other parts of the world being stuck in the past with IPv4 CGNAT.
IPv4 scarcity drives widespread use of Carrier-Grade Network Address Translation, a practice in ISPs and mobile networks that places many users behind each IP address, along with their collected activity and volumes of traffic.
this is quite fun. in one sense, it's a fairly serious bug: inet_net_pton() is completely broken for IPv6; it simply doesn't work and returns garbage output. but this bug has been present since 2006, when this function was first imported into libc, and no one noticed until August of this year when the PR was filed.
what i conclude this from is that literally no one uses these functions, and they should probably have never been imported in the first place. but, well, we can't remove them without breaking ABI compatibility, so now they're here forever, like an obnoxious uninvited party guest.
breaking news (I have to confess apple is sometimes good) given a #IPv6only mobile access (like the Deutsche Telekom within Germany, not during roaming) recent apple #iOS 18.5 makes #IPv6mostly for clients via hotspot
@Tuxi ⁂ @Rainer "friendica" Sokoll Du kannst meine Einstellungen hier finden: f.haeder.net/sysctl.zip Entpacke sie nach /etc/sysctl.d/ (falls dein System so arbeitet), bzw. natuerlich darfst du sie dir erstmal ansehen. #IPv6 ist bewusst deaktiviert.
Už jen pár posledních dnů je možné přihlásit přednášku na letošní Den #IPv6, který se uskuteční v tradičním termínu 6. června 2025 v NTK v Praze. denipv6.cz/cs/
Select Topic Area Product Feedback Body Summary Our OSS project is running into difficulties with users and community members that are accessing GitHub via IPv6-only networks/services. People are l...
o stupínek lepší je "Například vy pravděpodobně čtete tento článek na mobilním telefonu a k internetu přistupujete z IP adresy 2001:470:..., která je registrovaná v obci Hlavní město Praha, Česko" 😁 #IPv6
Is deploying #IPv6 one of your New Year's resolutions for 2025? Get started with our free, open webinars. You will learn: ✅ The basics of IPv6 address notation ✅ How to request IPv6 address space from the RIPE NCC ✅ How IPv6 allocation and assignment policies work ✅ How to register IPv6-related data in the RIPE Database
Congratulations to the awesome Jen Linkova, winner of the 2024 Itojun Service Award for her work on #IPv6!
She has played a key role in blazing a path towards IPv6-mostly deployments in Enterprise environments, including bringing the Google network to IPv6-mostly. It has been a great pleasure working with her over the years and this award is very well deserved!
"IPv6 Mostly" is an alternative to the dual-stack approach of transitioning to IPv6. On today's podcast we discuss the practical challenges and security considerations of strategy for moving to an IPv6-centric network while retaining IPv4 for legacy …
“A Short IPv6 Guide for Home IPv4 Admins” - taught me a bunch of useful things I didn't know that I didn't know about IPv6 in practice. Good stuff! gist.github.com/timothyham/dd0…
CZ.NIC set an end to #IPv4 on June 06, 2032 in the Czech Republic. This leaves operators about 3000 days to go #IPv6. As a German, I hope that this puts pressure on all European ISPs.
More details about the end of #IPv4 in state services: On 18th of December 2013 Czech #government decided that every service provided by Czech state has to be available on #IPv6 and be protected by #DNSSEC by 30th of June 2015. Yesterday a followed up action has been agreed on. On 6th of June 2032, IPv4 will be disabled on all services offered by Czech republic and they will be only available on IPv6 from that day on. Apart from that, every June starting from 2025, Czech government will get a report on how are the preparations.
Overall seems like a bold move, but I totally support it! IT sends a message, that #IPv4 is over and everybody should move to #IPv6 already. And even government - the definition of conservative and bureaucratic institution - gets it. Then why shouldn't you embrace it 😉
Vláda ČR včera přijala významné usnesení, které se týká infrastruktury Internetu, když projednala materiál s názvem „Restart zavádění technologie DNSSEC a protokolu IPv6 ve státní správě“.
This article (cited on Slashdot) suggests that the policy decision by Amazon Web Services to charge for IPv4 addresses could accelerate migration to IPv6. My ISPs (both cable and mobile) support IPv6, as does my server's hosting provider, so I personally made the switch to a dual-stack configuration quite some time ago. Those who haven't (and who use AWS) now have an additional financial incentive. supabase.com/blog/ipv6 #IPv6 #networking
Whereas the Czech government hasn't yet met its own mandatory #IPv6 requirements with a 2010 deadline. Even the ministry of finance launched multiple brand new ISes not supporting IPv6.
Dual stack is the most common way of deploying IPv6 in access networks. A recent standard defines IPv6-mostly access networks, providing IPv4 connectivity only for legacy devices while allowing modern devices to run IPv6-only.
An outline of the different IP settings a ModemManager bearer object may expose, and the expected actions the host would require to perform to set up the IP addressing in the modem.
ip6_managed_setup(NMDevice *self) in src/core/devices/nm-device.c forcibly disables IPv6 forwarding for the device. This basically invalidates the global IPv6 forwarding setting (net.ipv6.conf.all.forwarding) for devices managed by NetworkManager.
Lorenzo Colitti (main driver of not including #DHCPv6 on #Android) has now proposed a compromise for all big networks who want to use DHCPv6 to assign #IPv6 addresses:
This looks like a solid compromise to me for huge networks. It does require at least a /48 per site to support 65k devices but additionally solves other issues as well (NDP cache ex. attack)
