Skip to content

Commit

Permalink
IPv6 progress (#461)
Browse files Browse the repository at this point in the history
  • Loading branch information
yorickdowne authored Oct 1, 2024
1 parent e0b66c8 commit de90498
Showing 1 changed file with 15 additions and 22 deletions.
37 changes: 15 additions & 22 deletions website/docs/Support/ipv6.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: IPv6
sidebar_label: IPv6 support
---

## Y tho
## Conquer network amxiety

As of mid 2024:

Expand Down Expand Up @@ -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.

0 comments on commit de90498

Please sign in to comment.