#nat64 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nat64, 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
-
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
-
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
-
The Upstream for Ubuntu is not updated yet.
I would spend time to get this update
Unfortunately #Debian contributions work so much differently to what I'm used to today.
@Zugschlus could you help to get started with Debian Maintenance? -
Ubuntu 26.04 LTS is still delivering the old tayga 😩
#nat64 -
I like the idea of global anycast NAT64 gateways.
Maybe we shouldn't invent another prefix for it.
https://datatracker.ietf.org/doc/draft-matolin-global-nat64-anycast/
-
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
-
Just got a ping about ipxlat being proposed to the linux kernel (in kernel and mainline NAT64/NAT46):
https://lore.kernel.org/netdev/2026031[email protected]/T/#m6b6603d690f9bd7f85cce6307be7821100d98de0
-
Just got a ping about ipxlat being proposed to the linux kernel (in kernel and mainline NAT64/NAT46):
https://lore.kernel.org/netdev/2026031[email protected]/T/#m6b6603d690f9bd7f85cce6307be7821100d98de0
-
Just got a ping about ipxlat being proposed to the linux kernel (in kernel and mainline NAT64/NAT46):
https://lore.kernel.org/netdev/2026031[email protected]/T/#m6b6603d690f9bd7f85cce6307be7821100d98de0
-
Just got a ping about ipxlat being proposed to the linux kernel (in kernel and mainline NAT64/NAT46):
https://lore.kernel.org/netdev/2026031[email protected]/T/#m6b6603d690f9bd7f85cce6307be7821100d98de0
-
Just got a ping about ipxlat being proposed to the linux kernel (in kernel and mainline NAT64/NAT46):
https://lore.kernel.org/netdev/2026031[email protected]/T/#m6b6603d690f9bd7f85cce6307be7821100d98de0
-
Jool(stateful and stateless), NAT46 (OpenWRT only), CLAT with eBPF, now ipxlat within Kernel, tayga outside....
I am getting confused.
-
still without the recent version of tayga
-
still without the recent version of tayga
-
still without the recent version of tayga
-
still without the recent version of tayga
-
still without the recent version of tayga
-
@T_X @axx I made the switch to #NAT64-only on the default network of #FOSDEM 13(?) years ago. It broke So. Much. Stuff.
I knew the former maintainer of the network tooling from the Linux Kernel Summit, and ran into him by chance that year. #Ubuntu was completely broken on NAT64-only, it did not even bring up the network interfaces, and we sent people who came to the NOC to their booth.
I also sent that former maintainer over there.
They fixed things very quickly.
-
Nachdem unser IPv6-Mostly Setup endlich halbwegs rund läuft, sind unsere NAT64 Server regelmäßig ans Limit der möglichen Verbindungen gekommen, die sie übersetzten können.
Wir haben deswegen noch, pro Server, 8 weitere IPv4 Adressen in unseren Pool geholt.
Da diese Adressen exklusiv für das das NAT64 sind, steigt die Kapazität auf fast das 10-fache.So ist auch Stoßzeiten nun mehr als genug Luft nach oben und ihr könnt ohne Probleme weiter surfen!
-
Nachdem unser IPv6-Mostly Setup endlich halbwegs rund läuft, sind unsere NAT64 Server regelmäßig ans Limit der möglichen Verbindungen gekommen, die sie übersetzten können.
Wir haben deswegen noch, pro Server, 8 weitere IPv4 Adressen in unseren Pool geholt.
Da diese Adressen exklusiv für das das NAT64 sind, steigt die Kapazität auf fast das 10-fache.So ist auch Stoßzeiten nun mehr als genug Luft nach oben und ihr könnt ohne Probleme weiter surfen!
-
Nachdem unser IPv6-Mostly Setup endlich halbwegs rund läuft, sind unsere NAT64 Server regelmäßig ans Limit der möglichen Verbindungen gekommen, die sie übersetzten können.
Wir haben deswegen noch, pro Server, 8 weitere IPv4 Adressen in unseren Pool geholt.
Da diese Adressen exklusiv für das das NAT64 sind, steigt die Kapazität auf fast das 10-fache.So ist auch Stoßzeiten nun mehr als genug Luft nach oben und ihr könnt ohne Probleme weiter surfen!
-
Nachdem unser IPv6-Mostly Setup endlich halbwegs rund läuft, sind unsere NAT64 Server regelmäßig ans Limit der möglichen Verbindungen gekommen, die sie übersetzten können.
Wir haben deswegen noch, pro Server, 8 weitere IPv4 Adressen in unseren Pool geholt.
Da diese Adressen exklusiv für das das NAT64 sind, steigt die Kapazität auf fast das 10-fache.So ist auch Stoßzeiten nun mehr als genug Luft nach oben und ihr könnt ohne Probleme weiter surfen!
-
Nachdem unser IPv6-Mostly Setup endlich halbwegs rund läuft, sind unsere NAT64 Server regelmäßig ans Limit der möglichen Verbindungen gekommen, die sie übersetzten können.
Wir haben deswegen noch, pro Server, 8 weitere IPv4 Adressen in unseren Pool geholt.
Da diese Adressen exklusiv für das das NAT64 sind, steigt die Kapazität auf fast das 10-fache.So ist auch Stoßzeiten nun mehr als genug Luft nach oben und ihr könnt ohne Probleme weiter surfen!
-
@tschaefer
1&1 with Roaming #VodafoneNL #Dualstack works. #IPv6only without #NAT64 works too. -
@adrian @internet_nl @ipv6.social #Netherlands falling further behind in this key #technology (even sliding backwards?)...
Regarding the "overlaid IPv4 #infrastructure" over #IPv6, hopefully https://fck-nat.dev 1.4 with #NAT64 support is released soon.
Though ideally NAT64 would become a #Linux kernel feature (like #OpenBSD). -
-
Wait, there is a new #nat64 implementation for linux besides jool and the very old tayga?
And it only consists out of some network namespaces and a ebpf tc filter?
Looks quite interesting.
https://github.com/kubernetes-sigs/nat64/blob/main/tests/integration/e2e.bats
-
The #BoxyBSD project is taking a pause from provisioning completely free #vps instances / #vserver. For further questions, reach out to @gyptazy or in our Matrix chat.
After publishing the new self-service portal and making it easier to use and get a free VPS instance, we got a lot more new users who requested an instance than usual. We’re not out of resources but we want to provide a great and reliable service and have a buffer for upcoming things.
We’re already restocking the resources and adding new nodes to the project but temporary stop provisioning new instances. In the meantime, we will provide new services that will make the overall experience for users much better and easier.
We already started this with the new #NAT64 gateways and the new free #loadbalancing service that allows you to serve your website also on #IPv4, even your box is #IPv6 only.
We’re addicted to the #BSD community and hope to provide your quickly more #FreeBSD, #NetBSD, #OpenBSD, #DragonflyBSD and all the other bsd based systems again. In the meantime - have fun and #RUNBSD
#free #hosting #bhyve #zfs #firewall #networking #community #opensource #fediverse #services
-
We just added a free #loadbalancing service to #BoxyBSD!
This new feature got added by @gyptazy in addition to the newly introduced #NAT64 gateways to make your life easier and is currently tested with a few users! This provides you the ability to make your website also reachable by #IPv4 even your box is only running on #IPv6. This feature can be managed from your self-service portal and simply requires you to add a DNS name that should be balanced and to point the DNS A record to a given IPv4.
Making the legacy internet life easier, we hope for a higher #BSD adaption where people might be more motivated to try #FreeBSD, #NetBSD, #OpenBSD or even #opensolaris with #illumos.
#hosting #opensource #runbsd #hosting #free #service #saas #community #vps #vserver #server #vm
-
@alexhaydock Oh wow, I guess I know what I'll be doing during the holidays. I've wanted to play with #OpenBSD and also revamp my fairly fragile containerized #Jool #NAT64 setup that does questionable things with kernel versions.
I've long been comfortable with "ip" in Linux, but maybe the BSD world has even nicer things.
-
No NAT November: My Month Without IPv4
Link
📌 Summary: 本文探討了作者在11月的「無NAT十一月」挑戰中，關閉IPv4並僅使用IPv6的經歷。雖然在這段期間發現了許多挑戰和問題，特別是對於一些設備和應用程式的支持不佳，但作者認可轉向「IPv6-大多數」的概念，這樣可以同時利用IPv6和必要時仍然允許IPv4的路徑。最終，雖然作者的經驗顯示完全關閉IPv4還不成熟，但提議在未來的網路部署中考慮「IPv6-大多數」的方式，這將有助於平滑過渡。
🎯 Key Points:
- 作者接受了「無NAT十一月」的挑戰，評估僅依賴IPv6的可行性。
- 關閉IPv4時遇到許多技術問題，包括桌面操作系統與移動設備的支持情況。
- 一些嵌入式設備如Nintendo Switch未能在IPv6-only環境下正常工作。
- 討論了NAT64和DNS64等過渡技術，這些技術能幫助處理僅支持IPv4的服務。
- 最終建議推行「IPv6-大多數」的策略，以便在未來完全可行的情況下逐步淘汰IPv4。
🔖 Keywords: #IPv6 #NAT64 #DNS64 #無NAT #網路轉型 -
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.
-
A good #dualstack network should still run #dns64 and #nat64, so that it can fully support #ipv6 only devices and allow them a way to connect to legacy (ipv4) internet sites. https://sgryphon.gamertheory.net/2022/12/running-nat64-in-a-dual-stack-network/
-
@issackelly @tyler I rather like #NAT64 ; it's clever. So is #DNS64. Even the custom Bowtie routing is rather neat in its operation. That said, putting all three together does seem to be a lot of moving parts.
There will indeed be situations where the need is to access a legacy private IP network, but there will also be cases when enabling #IPv6 for that private network would reduce complexity for all its users. Native IPv6 could still leverage the Bowtie routing for multiple disparate subnets.
-
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.
-
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.
-
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.
-
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.
-
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.
