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

Enigmatick

@tschaefer

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?

#nat64

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/

#ipv6 #ipv6only (public) #nat64

Global Anycast NAT64 Well-Known Prefix

This document defines a globally routable, anycast NAT64 service using the IPv6 prefix 2600:6464::/96 as a standardized translation substrate for IPv6-to-IPv4 connectivity. The goal of this specification is to eliminate per-network NAT64 configuration complexity by introducing a single globally consistent NAT64 translation prefix operated as a distributed anycast service by participating Internet Service Providers, cloud providers, and content delivery networks. The model assumes an IPv6-only client environment with mandatory IPv4 reachability via NAT64 translation. IPv4-only services remain reachable without modification. IPv4 is not modified. IPv6 is not modified. Only translation placement and routing semantics are standardized. This document defines: * A globally shared NAT64 prefix (2600:6464::/96) * Anycast-based NAT64 edge behavior * Stateless IPv6-to-IPv4 synthesis rules * Optional reverse mapping constraints (IPv4->IPv6 blocked) * Operational requirements for participating networks

IETF Datatracker
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
Look ma, no IPv4. 🙂
#nat64 #ipv6
[RFC net-next 00/15] Introducing ipxlat: a stateless IPv4/IPv6 translation device

Jool(stateful and stateless), NAT46 (OpenWRT only), CLAT with eBPF, now ipxlat within Kernel, tayga outside....

I am getting confused.

#nat64 #linux

#1107302 - New upstream fork - Debian Bug report logs

Nice! NAT64 in action, My IPv6-only jail can successfully talk with Github. No tayga, just the new "af-to" feature, that the "pf" firewall got in 15.0-RELEASE:

pass in quick on bastille0 inet6 from $jail_net to 64:ff9b::/96 \
af-to inet from ($ext_if) keep state

This is genuinly nice! 🙂

#freebsd #networking #pf #nat64 #ipv6