home.social

#ipv6mostly — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ipv6mostly, aggregated by home.social.

  1. Checked it the afternoon again. Nobody else seems to run the windows preview here 😩

    #ipv6mostly

  2. An diesem langen Wochenende habe ich mal wieder mir Zeit genommen, um etwas an meinem Heimnetz herumzuspielen und den #RaspberryPi mal wieder anzuwerfen. #IPv6mostly war diesmal mein Testgebiet. Mit CoreDNS, Tayga und KEA DHCP-Server hat das ganze dann irgendwann doch recht gut funktioniert. Ich war überrascht wie stark an einem die KI (hier Gemini) weiterhelfen und ein Tutorial für ein doch spezielles Thema erstellen konnte. Nach etwas gebastel hat es dann doch funktioniert. #DNS64 #NAT64

  3. @nuintari My (admittedly cursory) understanding is that it's a transition aid, to smooth the path from #dualstack to #ipv6mostly. ̶A̶n̶ ̶O̶S̶ ̶n̶e̶t̶w̶o̶r̶k̶ ̶s̶t̶a̶c̶k̶ ̶m̶i̶g̶h̶t̶ ̶b̶e̶ ̶r̶e̶l̶u̶c̶t̶a̶n̶t̶ ̶t̶o̶ ̶t̶a̶k̶e̶ ̶t̶h̶e̶ ̶f̶i̶r̶s̶t̶ ̶l̶e̶a̶p̶-̶o̶f̶-̶f̶a̶i̶t̶h̶ ̶t̶o̶ ̶I̶P̶v̶6̶-̶m̶o̶s̶t̶l̶y̶,̶ ̶s̶o̶ ̶t̶h̶e̶ ̶R̶F̶C̶ ̶l̶e̶t̶s̶ ̶t̶h̶e̶ ̶n̶e̶t̶w̶o̶r̶k̶ ̶m̶a̶k̶e̶ ̶t̶h̶e̶ ̶f̶i̶r̶s̶t̶ ̶m̶o̶v̶e̶,̶ ̶p̶o̶s̶i̶t̶i̶v̶e̶l̶y̶ ̶d̶e̶c̶l̶a̶r̶i̶n̶g̶ ̶t̶h̶a̶t̶ ̶I̶P̶v̶6̶ ̶s̶i̶n̶g̶l̶e̶ ̶s̶t̶a̶c̶k̶ ̶s̶h̶o̶u̶l̶d̶ ̶w̶o̶r̶k̶ ̶f̶i̶n̶e̶.̶ ̶A̶ ̶d̶u̶a̶l̶ ̶s̶t̶a̶c̶k̶ ̶n̶e̶t̶w̶o̶r̶k̶ ̶w̶o̶u̶l̶d̶ ̶l̶a̶c̶k̶ ̶t̶h̶a̶t̶ ̶s̶i̶g̶n̶a̶l̶,̶ ̶a̶n̶d̶ ̶t̶h̶e̶ ̶O̶S̶ ̶w̶o̶u̶l̶d̶ ̶b̶e̶h̶a̶v̶e̶ ̶a̶c̶c̶o̶r̶d̶i̶n̶g̶l̶y̶

    Essentially, it's like "positive affirmations", but for the next phase of IPv6 transition

  4. @kasperd

    DAD works, but nothing more.

    Or in other words: At the moment it is not possible to use more than one Windows-PC with IPv6-mostly-support (Preview only ) in a IPv6-mostly or IPv6-only Network.

    By accident a host may use one of the other mapped IPv4 addresses (out of 192.0.0.0/29) . But in general it takes the first one anywhere.

    and W.B. is right: MS has to fix that problem before it gets released for the masses

    #ipv6mostly #ipv6only #ipv6 #clat #windowspreview

  5. Falls jemand in München und Umgebung (habe d-ticket) einen Rechner mit dem Betakanal des Windows-Insider-Programm am Laufen hat, ich wäre über einen CLAT Test (via WLAN) mit zwei Rechnern sehr erfreut. Ein mobiler IPv6-mostly Hotspot und mein Rechner stehen zur Verfügung.
    Bitte privat antworten.

    #windows11 #clat #ipv6 #ipv6mostly #ipv6only

  6. This draft has now been officially adopted by the v6ops IETF working group and renamed to:
    draft-ietf-v6ops-6mops

    datatracker.ietf.org/doc/draft

    Also, a related 464XLAT / CLAT draft to keep an eye on:
    datatracker.ietf.org/doc/draft

    #IPv6 #IPv6Mostly #CLAT

  7. I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.

    Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.

    #Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter

  8. Rejoice, network operators. Windows 11 will be joining the rest of the world soon in supporting CLAT, #NAT64, and #DNS64 natively. (Currently, CLAT only works on cellular connections.)

    Supporting two IP versions has been a pain we’ve had to live with for over a decade, but this will allow network operators to forcibly disable clients’ IPv4 stacks via DHCP/RA, finish #IPv6 switchovers, and run true #IPv6mostly or #IPv6only networks.

    We’re one big step closer to killing “legacy IP” for good. :ipv6:

    techcommunity.microsoft.com/t5

  9. After explaining the current state of affairs with #IPv6 transition mechanisms, I published a tutorial on how to apply all of that in a real network with @news (#VyOS):

    blog.daknob.net/ipv6-first-wit

    #IPv6First #IPv6Mostly #PPPoE #DHCPv6PD
    mastodon.social/@antonis/11224

  10. @nSonic kannst Du genaueres sagen? Welche Dienste? Nutze #Azure / MS in einem #IPv6mostly setup und sehe keine Probs.
    #Android hat IPv6only addressing.

  11. @tschaefer
    The best statement of every Jen presentation:
    "You are not operating IPv6 until you turn IPv4 off"

    #IPv6mostly #IPv6only #IPv6 #enterprise

  12. RE: ipv6.social/@tschaefer/1157936

    I have seen #39c3 provides #ipv6 #ipv6mostly #ipv6only

    Please try it with windows 11 preview version, if you can!

    These instructions should help.

  13. @treysis

    "On the wireless network we are experimenting with ipv6-mostly, this means that if your wireless client supports it it will only have a IPv6 Address and access to IPv4 hosts will automaticly be routed trough our NAT64 gateways."

    events.ccc.de/congress/2025/in

    #ipv6mostly #39c3 #ipv6 #ipv6only

    👍👍👍

  14. Das WLAN des Hotels/der Konferenz kann's nicht. ☹️

    Wer #IPv6mostly hier ausprobieren möchte, einfach in meine Nähe stellen 🤗

    #ipv6programm
    #expertenkonferenz2025
    #ipv6

  15. for the record:
    #macOS behaves as expected

    it doesn't use IPv4-lease from the iPhone,
    instead it does clat (464xlat)

    #IPv6mostly #ipv6only

  16. @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: ietf.org/archive/id/draft-link

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

    #ipv6

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

  19. [Перевод] Развёртывание сетей доступа преимущественно на основе IPv6

    Изначальной моей задачей было получить сеть на базе протокола IPv6, где клиенты могли по желанию отказаться от использовать IPv4. Задача оказалась не самой тривиальной. В процессе поиска решения наткнулся на очень полезную заметку, которая по сути вобрала в себя всё то, что мне удалось выяснить. Представляю вашему внимаю перевод этой статьи с моими дополнениями по поводу настройки подобной сети на практике. Читать

    habr.com/ru/articles/886760/

    #ipv6 #ipv6mostly

  20. @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

  21. How I feel when dealing with DHCP scope exhaustion, propose the ideal solution, and am forced to drop the DHCPv4 lease time even further.

    #IPv6 #IPv6Only #IPv6Mostly #IPv6IsNow #sysadmin

  22. I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.

    Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.

    #Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter

  23. I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.

    Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.

    #Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter

  24. I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.

    Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.

    #Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter

  25. I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.

    Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.

    #Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter