#464xlat — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #464xlat, aggregated by home.social.
-
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.https://enigmatick.social/objects?uuid=b5cfe32e-e1ba-40da-80a1-e6f5bcfb6149
-
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.https://enigmatick.social/objects?uuid=b5cfe32e-e1ba-40da-80a1-e6f5bcfb6149
-
It seems to me, they need more testers.
-
#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.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107Huge 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.
-
@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
-
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
-
I've tried to summarize the current state of the art for IPv6-First and IPv6-Only Access Networks in my blog post here: https://blog.daknob.net/do-you-really-need-ipv4-anymore/
Let me know how it went for you, what problems you may have ran into, and whether something is missing! I'm also happy to answer questions or help with ideas.
-
@ktims at the very least I would suspect this is going to start adding customer pressure for AWS to actually provide #IPv6 support to their services that are still IPv4-only, or are missing v4/v6 parity. Don't get me wrong: I'm here for the move and you just need to make the call at some point, but that doesn't mean it's not still a bit rude to present your customer with a lower and higher priced choice on the surface, but then simply remove the lower cost choice for a non-trivial subset of your products 😝
But, the market is definitely starting to normalize (source Hilco for this screenshot). It's definitely interesting to see how different forces and stakeholders are starting to interact.
I mean, we had the big content shops like Google, FB, Netflix etc. providing v6 at their edges for a good while, with mobile picking up a good amount on the client side. The CDNs are also in there with generally making it fairly easy to turn up dual stack on their edges.
Residential seems to be trucking along and gaining better adoption, where chunks of newer RGs and such seem to actually be getting to Just Works territory and residential users who don't and shouldn't have to care are getting v6 connectivity as well.Then you have your government forces like DoD and other US fed memos and mandates, and the recently-announced Czech timeline, with e.g. the US reqs starting to push some SaaS and enterprise app providers to get their house in order.
The laggards, imho, have been the large public cloud providers, the developer space in general, and enterprise. With AWS pushing v4 pricing, we now have a more concrete business driver, imho, that will start to push developers as well as infrastructure & platform types to get IPv6 familiarity, with a possible second order of creating more IPv6 demand in the enterprise space for those devs to be able to access as well as test against their now v6-enabled service edges.
It's definitely an interesting time.
Anecdotally I'm seeing the leading edge of the conversation shift away from the earlier v6 tunnels & experimentation, and even from just dual stack, to folks poking at #IPv6-only or #IPv6-mostly, with way more conversations around #NAT64, #DNS64, and #464XLAT popping up in enthusiast spaces.