home.social

#464xlat — Public Fediverse posts

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

fetched live
  1. @hiker @xrobau @lispi314

    My DSL/DOCIS as well as my MOBILE are #IPv6only networks.
    Have a #NAT64 offsite to reach the #legacyinternet .

    #464XLAT for the subnet with stuff that does not work #IPv6only

    Removes so much maintenance burden and simplifies management so much.

  2. @hiker @xrobau @lispi314

    My DSL/DOCIS as well as my MOBILE are #IPv6only networks.
    Have a #NAT64 offsite to reach the #legacyinternet .

    #464XLAT for the subnet with stuff that does not work #IPv6only

    Removes so much maintenance burden and simplifies management so much.

  3. @hiker @xrobau @lispi314

    My DSL/DOCIS as well as my MOBILE are #IPv6only networks.
    Have a #NAT64 offsite to reach the #legacyinternet .

    #464XLAT for the subnet with stuff that does not work #IPv6only

    Removes so much maintenance burden and simplifies management so much.

  4. @hiker @xrobau @lispi314

    My DSL/DOCIS as well as my MOBILE are #IPv6only networks.
    Have a #NAT64 offsite to reach the #legacyinternet .

    #464XLAT for the subnet with stuff that does not work #IPv6only

    Removes so much maintenance burden and simplifies management so much.

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

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

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

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

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

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

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

  12. #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)

  13. #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)

  14. #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)

  15. Extending the Vector Packet Processing Engine

    I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

    enigmatick.social/objects?uuid

  16. Extending the Vector Packet Processing Engine

    I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

    enigmatick.social/objects?uuid

  17. Extending the Vector Packet Processing Engine

    I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

    enigmatick.social/objects?uuid

  18. Extending the Vector Packet Processing Engine

    I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

    enigmatick.social/objects?uuid

  19. Extending the Vector Packet Processing Engine

    I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

    enigmatick.social/objects?uuid

  20. Update:
    Während ich kurz telefonieren war, hat @jana ein CLAT-Container gebaut, der in meinem v6only Kubernetes tut. codeberg.org/itz_jana/tundra-n

    Einziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat

  21. Update:
    Während ich kurz telefonieren war, hat @jana ein CLAT-Container gebaut, der in meinem v6only Kubernetes tut. codeberg.org/itz_jana/tundra-n

    Einziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat

  22. Update:
    Während ich kurz telefonieren war, hat @jana ein CLAT-Container gebaut, der in meinem v6only Kubernetes tut. codeberg.org/itz_jana/tundra-n

    Einziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat

  23. Update:
    Während ich kurz telefonieren war, hat @jana ein CLAT-Container gebaut, der in meinem v6only Kubernetes tut. codeberg.org/itz_jana/tundra-n

    Einziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat

  24. Update:
    Während ich kurz telefonieren war, hat @jana ein CLAT-Container gebaut, der in meinem v6only Kubernetes tut. codeberg.org/itz_jana/tundra-n

    Einziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat

  25. #NetworkManager just got #464XLAT CLAT support merged in.
    IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
    gitlab.freedesktop.org/Network

    Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

  26. #NetworkManager just got #464XLAT CLAT support merged in.
    IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
    gitlab.freedesktop.org/Network

    Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

  27. #NetworkManager just got #464XLAT CLAT support merged in.
    IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
    gitlab.freedesktop.org/Network

    Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

  28. #NetworkManager just got #464XLAT CLAT support merged in.
    IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
    gitlab.freedesktop.org/Network

    Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

  29. #NetworkManager just got #464XLAT CLAT support merged in.
    IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
    gitlab.freedesktop.org/Network

    Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

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

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

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

  33. Kinda fun poking around with some nat64 things while prepping a small internal IPv6-related presentation. I'd been using the automatic CLAT that macOS just runs in the background, but it was a nice surprise to install clatd for a demo on an Ubuntu VM and have it Just Work.

    #IPv6 #NAT64 #464XLAT

  34. Kinda fun poking around with some nat64 things while prepping a small internal IPv6-related presentation. I'd been using the automatic CLAT that macOS just runs in the background, but it was a nice surprise to install clatd for a demo on an Ubuntu VM and have it Just Work.

    #IPv6 #NAT64 #464XLAT

  35. Kinda fun poking around with some nat64 things while prepping a small internal IPv6-related presentation. I'd been using the automatic CLAT that macOS just runs in the background, but it was a nice surprise to install clatd for a demo on an Ubuntu VM and have it Just Work.

    #IPv6 #NAT64 #464XLAT

  36. Kinda fun poking around with some nat64 things while prepping a small internal IPv6-related presentation. I'd been using the automatic CLAT that macOS just runs in the background, but it was a nice surprise to install clatd for a demo on an Ubuntu VM and have it Just Work.

    #IPv6 #NAT64 #464XLAT

  37. Kinda fun poking around with some nat64 things while prepping a small internal IPv6-related presentation. I'd been using the automatic CLAT that macOS just runs in the background, but it was a nice surprise to install clatd for a demo on an Ubuntu VM and have it Just Work.

    #IPv6 #NAT64 #464XLAT

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

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

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

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

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

  43. also available in English:
    Microsoft extends Windows 11 464XLAT support to include fixed-line networks -- New phase in changeover from IPv4 to IPv6 requires appropriate transition mechanisms
    sidn.nl/en/news-and-blogs/micr

    Windows 11 supports only CLAT for mobile networks, but a future version will also provide support for other network interfaces. It will then be possible to enable #464XLAT on fixed-line networks as well.

    #IPv6

  44. also available in English:
    Microsoft extends Windows 11 464XLAT support to include fixed-line networks -- New phase in changeover from IPv4 to IPv6 requires appropriate transition mechanisms
    sidn.nl/en/news-and-blogs/micr

    Windows 11 supports only CLAT for mobile networks, but a future version will also provide support for other network interfaces. It will then be possible to enable #464XLAT on fixed-line networks as well.

    #IPv6

  45. also available in English:
    Microsoft extends Windows 11 464XLAT support to include fixed-line networks -- New phase in changeover from IPv4 to IPv6 requires appropriate transition mechanisms
    sidn.nl/en/news-and-blogs/micr

    Windows 11 supports only CLAT for mobile networks, but a future version will also provide support for other network interfaces. It will then be possible to enable #464XLAT on fixed-line networks as well.

    #IPv6

  46. op SIDN.nl:
    Microsoft breidt 464XLAT-ondersteuning in Windows 11 uit naar vaste netwerken -- Nieuwe fase in overgang van IPv4 naar IPv6 vraagt om specifieke transitiemechanismen
    sidn.nl/nieuws-en-blogs/micros

    Waar Windows 11 nu alleen CLAT ondersteunt voor mobiele netwerken, komt deze mogelijkheid in een toekomstige versie ook voor andere netwerkinterfaces beschikbaar. Dat maakt het straks mogelijk om #464XLAT ook op vaste netwerken in te schakelen.

    #IPv6

  47. op SIDN.nl:
    Microsoft breidt 464XLAT-ondersteuning in Windows 11 uit naar vaste netwerken -- Nieuwe fase in overgang van IPv4 naar IPv6 vraagt om specifieke transitiemechanismen
    sidn.nl/nieuws-en-blogs/micros

    Waar Windows 11 nu alleen CLAT ondersteunt voor mobiele netwerken, komt deze mogelijkheid in een toekomstige versie ook voor andere netwerkinterfaces beschikbaar. Dat maakt het straks mogelijk om #464XLAT ook op vaste netwerken in te schakelen.

    #IPv6

  48. op SIDN.nl:
    Microsoft breidt 464XLAT-ondersteuning in Windows 11 uit naar vaste netwerken -- Nieuwe fase in overgang van IPv4 naar IPv6 vraagt om specifieke transitiemechanismen
    sidn.nl/nieuws-en-blogs/micros

    Waar Windows 11 nu alleen CLAT ondersteunt voor mobiele netwerken, komt deze mogelijkheid in een toekomstige versie ook voor andere netwerkinterfaces beschikbaar. Dat maakt het straks mogelijk om #464XLAT ook op vaste netwerken in te schakelen.

    #IPv6

  49. op SIDN.nl:
    Microsoft breidt 464XLAT-ondersteuning in Windows 11 uit naar vaste netwerken -- Nieuwe fase in overgang van IPv4 naar IPv6 vraagt om specifieke transitiemechanismen
    sidn.nl/nieuws-en-blogs/micros

    Waar Windows 11 nu alleen CLAT ondersteunt voor mobiele netwerken, komt deze mogelijkheid in een toekomstige versie ook voor andere netwerkinterfaces beschikbaar. Dat maakt het straks mogelijk om #464XLAT ook op vaste netwerken in te schakelen.

    #IPv6

  50. @thatnateguy Is the question about carrier-grade NAT66 or carrier-grade NAT44? Or even #464XLAT ?