From de90498c7ef5f5fd89ce0b02015b322132488d09 Mon Sep 17 00:00:00 2001
From: yorickdowne <71337066+yorickdowne@users.noreply.github.com>
Date: Mon, 30 Sep 2024 20:23:43 -0400
Subject: [PATCH] IPv6 progress (#461)

---
 website/docs/Support/ipv6.md | 37 +++++++++++++++---------------------
 1 file changed, 15 insertions(+), 22 deletions(-)

diff --git a/website/docs/Support/ipv6.md b/website/docs/Support/ipv6.md
index bfa7a02c..81a7f8c2 100644
--- a/website/docs/Support/ipv6.md
+++ b/website/docs/Support/ipv6.md
@@ -4,7 +4,7 @@ title: IPv6
 sidebar_label: IPv6 support
 ---
 
-## Y tho
+## Conquer network amxiety
 
 As of mid 2024:
 
@@ -34,31 +34,24 @@ If you previously had IPv6-specific settings in `/etc/docker/daemon.json`, you c
 
 ### Configure Eth Docker
 
-`nano .env` and set `IPV6=true`, which will tell Compose to enable v6 for the networks it creates.
+`nano .env` and set `IPV6=true`, which will tell Docker Compose to enable v6 for the networks it creates. Then
+`./ethd restart` to recreate the bridge network Eth Docker uses.
 
-## Safu?
+### Verify
 
-Maybe. I still have to test ufw integration.  
-On your LAN firewall, if this is in a LAN, you'd need rules to allow the P2P ports incoming to the v6 address of your
-node.
+Look at Eth Docker's default network with `docker network ls` and then `docker network inspect eth-docker_default`,
+or whatever network it actually is. If IPv6 is enabled, you'll see that and you will see assigned IPv4 and IPv6
+addresses.
 
-## Which clients?
+## Security
 
-CL
+`ufw` integration works; ports mapped to host can be blocked by a v6 deny rule. As with v4, ufw needs to be
+["in front of Docker"](../Support/Cloud.md) for this to work.
 
-- [x] Lighthouse
-- [x] Lodestar
-- [x] Nimbus
-- [ ] Teku: Unsure, advertisement not tested
-- [ ] Prysm: Maybe, `--p2p-local-ip ::`, but [not dual-stack](https://github.com/prysmaticlabs/prysm/issues/12303)
-- [ ] Grandine: Unsure
-- [ ] Lambda: Unsure
+On your LAN firewall, if this is in a LAN, you'd need rules to allow the P2P ports incoming to the v6 address of your
+node.
 
-EL
+## Which clients?
 
-- [ ] Besu: not fully tested
-- [ ] Geth: not fully tested
-- [ ] Erigon: not fully tested
-- [ ] Nethermind: Possibly no advertisement, no explicit discv5 option
-- [ ] Reth: No IPv6 connectivity on `main` as of mid Nov 2023
-- [ ] Nimbus: Unsure
+This is a moving target and best tracked by [Sonic's site](https://ipv6eth.info). As of mid 2024, all CLs with
+the exception of Prysm support a v4/v6 dual stack, and ELs have added support as well.