@pcdog @jana @merlin
Running #IPv6only and #IPv6mostly in my home since 2 years now.
Currently playing with RFC9762 for Android, which just works if you have enough address space.
Even experimented with #NAT64 off-site to disable legacy protocol on my CPE.
Currently contributing to upcoming RFCs on this topic. As well as iron out bugs in odhcpd and luci #OpenWrt
Work laptop (Win11) sits in a #IPv6only subnet. Only needed some tricks for the VPN to work correctly. 😄 Looking forward to CLAT.
Das WLAN des Hotels/der Konferenz kann's nicht. ☹️
Wer #IPv6mostly hier ausprobieren möchte, einfach in meine Nähe stellen 🤗
464XLAT, CLAT, PLAT are transition technologies.
It is nice that Win will get CLAT support sooner or later in the mainstream.
Therefore access networks should convert to #IPv6mostly with PLAT and PREF64.
No need for #DNS64 there.
Managed networks need DNS64 and NAT64 to access legacy endpoints. Otherwise they need to run #IPv6only
The main topic is now to tell services providers to enable #IPv6
We should get scheduled legacy protocol brownouts. Starting with 1h/week
@sorah
Thank you for this report. Very interesting to read.
@chrysn
So far, my experience on Windows #IPv6only was more not available services with #IPv6 support like the famous example github.
Broken apps that need an IPv4 socket haven't been an issue for me.
But the clat support allows for more and easier #ipv6mostly deployments as well as the need for #dns64.
There corresponding RFCs where finalized recently.
@apalrd Have you been facing issues with #WiFiCalling while running #IPv6mostly in #OPNsense ?
I can't figure out exactly why it breaks in my home network, since there are no misconfigured rules nor anything related - if I disable DHCP option 108 and assign old addresses to each client, it works; when passing through #tayga #nat64, it stops entirely.
All this because the carrier's servers are stuck in the last millenium, of course they are: https://www.netify.ai/resources/mobile-gateways/country/br
for the record:
#macOS behaves as expected
it doesn't use IPv4-lease from the iPhone,
instead it does clat (464xlat)
@sysop "For the sake of it" counts? =D
Actually, I wanted to switch my home network to #IPv6mostly some time ago, giving the next step towards a simpler, easier & up-to-date environment, and I followed this guide by the awesome @apalrd : https://piped.privacytools.click/watch?v=WZSdpY_VgyY
@samd There are three main issues with going IPv6 only:
- Legacy clients won’t be able to reach you.
- You won’t be able to reach some services.
- Some software may not work well with IPv6.
It’s technically possible to use only IPv6 for a lot of stuff, but if you care about being reachable from anywhere you would still in 2025 probably need some sort of translation layer at your network’s edge.
Check out #IPV6Mostly for a softer approach that is less likely to break things: https://www.ietf.org/archive/id/draft-link-v6ops-6mops-00.html
@apalrd #IPv6mostly Wi-Fi, please 🙂
@apalrd Did you notice something weird by using DHCP option 108 in #OPNsense for #IPv6mostly deployment? In my setup, most Wi-Fi devices in my network lose connectivity - link is established but they lose IP addressing thus making them unusable. Turning Wi-Fi OFF and ON on the device get them back but eventually get lost again.
For the devices who won't understand 108, they work completely fine; removing 108 from DHCP settings (rather ISC or Kea) makes them work again but by giving old IP back.
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
#dhcpoption108 as well #pref64
I made also the windows test - in case option 108 is not provided by the client, iOS provides IPv4
Openwrt ist schon irgendwie genial, auf der einen Seite kann man 464xlat (CLAT) nutzen (in der Paketliste immer ganz oben 🙃) und auf der anderen Seite #ipv6mostly 👍
Das hat bisher nicht mal Android geschafft.
[Перевод] Развёртывание сетей доступа преимущественно на основе IPv6
Изначальной моей задачей было получить сеть на базе протокола IPv6, где клиенты могли по желанию отказаться от использовать IPv4. Задача оказалась не самой тривиальной. В процессе поиска решения наткнулся на очень полезную заметку, которая по сути вобрала в себя всё то, что мне удалось выяснить. Представляю вашему внимаю перевод этой статьи с моими дополнениями по поводу настройки подобной сети на практике. Читать
@Tubsta Anyone who want to try #IPv6only can just disable IPv4 with any ISP that provides native IPv6. So there is no appetite for such an ISP. It is more the ISPs that reject dual stack and switch to #464xlat and #IPv6mostly
How I feel when dealing with DHCP scope exhaustion, propose the ideal solution, and am forced to drop the DHCPv4 lease time even further.
@goetz @ffhl I needed a while to figure out what practical benefit we would have. One thing that came to my mind: Avoiding #ARP on supporting devices completely if I understand #ipv6mostly correctly. We do have a DHT for ARP in #batman_adv. And could reduce broadcasts a lot with it. But it's still not zero. #IPv6 is so much smarter for Neighbor Discovery as it uses #multicast properly with its solicited mcast addresses and not like broadcasts. And we have #MLD snooping in our #mesh.
