Skip to content

Commit f15408e

Browse files
committed
cilium nat464 post refactor
1 parent 8786407 commit f15408e

File tree

3 files changed

+3
-5
lines changed

3 files changed

+3
-5
lines changed

config/_default/markup.toml

-3
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,6 @@
55
[goldmark.renderer]
66
unsafe = true
77

8-
[goldmark.parser.attribute]
9-
block = true
10-
118
[highlight]
129
noClasses = false
1310
wrapperClass = 'highlight'

content/posts/cilium-ipv6only-design.md

Whitespace-only changes.

content/posts/cilium-nat64.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,8 @@ In this blog post I cover how I am running [Cilium](https://cilium.io) as a stan
1818

1919
Before we get to the real meat and potatoes we need to do some prep work.
2020

21-
- Provision a VM - I am using Ubuntu 22.04LTS with kernel version 5.15.0-138-generic in my setup.
21+
- Create a VM for the NAT46x64Gateway - I am using Ubuntu 22.04LTS with kernel version 5.15.0-138-generic in my setup.
22+
- [Install Docker](https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM
2223
- Configure networking - A `NAT46x64Gateway` must be dual stacked as it acts as a bridge between IPv4 and IPv6 networks. Here's an example netplan config I am using.
2324

2425
```yaml
@@ -80,7 +81,7 @@ root@nat64gw:~# docker exec -it cilium-lb cilium status --verbose | awk "/NAT46\
8081
A good test to check if our NAT46x64Gateway is performing the 4to6 translation correctly, we can try connecting to an application that is accessible only via IPv4. So let's provision another Ubuntu VM on our IPv6 only network with the following netplan config as shown below.
8182

8283
```yaml
83-
root@controller:/home/kagraw# cat /etc/netplan/00-installer-config.yaml
84+
root@testvm# cat /etc/netplan/00-installer-config.yaml
8485
network:
8586
version: 2
8687
renderer: networkd

0 commit comments

Comments
 (0)