cilium nat46x64gw post

Author: netops2devops

content/posts/cilium-nat64.md

@@ -12,7 +12,7 @@ IPv4 and IPv6 are two different protocols they are incompatible with one another
 
 In this blog post I cover how I am running [Cilium](https://cilium.io) as a standalone NAT46x64 gateway which harnesses the power of [eBPF](https://docs.ebpf.io) in the linux kernel. Cilium is a CNCF graduate project which brings advanced networking capabilities to Kubernetes. While it is most commonly used as a CNI (Container Network Interface), not much has been documented about it's capabilities outside of Kubernetes, specially as a standalone NAT46x64 gateway. For my fellow kernel nerds and C lovers, Cilium's NAT46x64 implementation can be found [here](https://github.com/cilium/cilium/blob/main/bpf/lib/nat_46x64.h)
 
-## Create a standalone NAT46x64Gateway
+## Configuration
 
 Before we get to the real meat and potatoes we need to do some prep work.
 
@@ -55,7 +55,7 @@ docker run --name cilium-lb -itd \
 	"quay.io/cilium/cilium:stable" cilium-agent --enable-ipv4=true --enable-ipv6=true --devices=eth0 --datapath-mode=lb-only --enable-k8s=false --bpf-lb-mode=snat --enable-nat46x64-gateway=true
 ```
 
-## Quick test
+## Test
 
 Let's create another Ubuntu VM as a test host with an IPv6 only address that points to our NAT46x64Gateway. Few noteworthy points in the netplan config shared below.