home.social

#clat — Public Fediverse posts

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

fetched live
  1. It seems to me, that Microsoft has #clat better implemented than NetworkManager.

    In my test NM reduced the outgoing MTU to 1280 while windows uses the full available MTU.

    #ipv6 #ipv6only #ipv4rip #464xlat

  2. At the brink of #CLAT on the desktop, this allows for #IPv6mostly access networks.

    But on the other hand it will mask over #IPv6 issues as there is the Legacy IP fall back.

    How do you think about this?

  3. #ipv6 #ipv4rip #ipv4 #clat #windows #464xlat #ipv6mostly #ipv6only #ripe92

    slide 13/14/15 by Wilhelm Boeddinghaus

    pretalx.ripe.net/media/ripe-92

    now corrected by Microsoft as promised two weeks ago

    It is still a experimental version, not released yet. (Build 29599.1000 )

    (now you can use several windows hosts in one network segment with clat)

  4. @alexhaydock #CLAT needs SLAAC or DHCPv6-PD for the host as it needs to generate CLAT source address(es).

    So if you set a static address and have no SLAAC in RAs than it will not work.

    If SLAAC is available one should be able to obtain a CLAT address in addition to the static configured.

    datatracker.ietf.org/doc/draft

  5. Some statements won't be true anymore within the next three weeks. 🤗

    pretalx.ripe.net/media/ripe-92

    Microsoft announced fixes for their #clat implementation 👍

    "We should have a build available to test within 2-3 weeks".

    #ipv6only #ipv6 #ripe92

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

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

  8. Nach dem Vortrag von Wilhelm Boeddinghaus zu CLAT für Windows auf dem Berliner Adminstammtisch stellt sich mir jetzt die Frage, wo nehme ich 9 Windows11-Kisten mit aktivierten Beta-Insider-Preview her?

    #ipv6only #ipv6 #clat #windows11

    After the talk by Wilhelm Boeddinghaus about CLAT for Windows at the Berliner Admin Stammtisch I am wondering how to get 9 windows 11 boxes with beta-insider-preview?

  9. Tested the #clat implementation of NetworkManager, there seems to be a issue when multiple interfaces are up and connected, but otherwise it's working quite well:
    gitlab.freedesktop.org/Network

    #ipv6

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

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