Skip to content

docs: clarify ipv6 details in networking page #8368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
philknows merged 2 commits into from
Sep 11, 2025
Merged

docs: clarify ipv6 details in networking page #8368

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fef2fc8
docs: clarify ipv6 on networking page
philknows Sep 10, 2025
a059ede
lint
philknows Sep 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions docs/pages/run/beacon-management/networking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,12 +41,18 @@ The primary purpose of ENRs is to facilitate node discovery and connectivity in

Note that bootnodes are announced via ENR.

Lodestar prints out its own ENR on startup, the logs will show something similar to the following
Lodestar prints out its own ENR on startup, the logs will show something similar to the following for IPv4 nodes:

```txt
info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr4=/ip4/0.0.0.0/udp/9000
```

Or similar to the following for IPv6 dual-stack nodes (when enabled):

```txt
info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr4=/ip4/0.0.0.0/udp/9000, bindAddr6=/ip6/::/udp/9000
```
Comment on lines +50 to +54
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Sep 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This clarification for dual-stack nodes is helpful. To make the documentation more comprehensive, it would be beneficial to also include an example for an IPv6-only node. This would provide better guidance for users running in different network configurations.

Suggested change
Or similar to the following for IPv6 dual-stack nodes (when enabled):
```txt
info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr4=/ip4/0.0.0.0/udp/9000, bindAddr6=/ip6/::/udp/9000
```
Or similar to the following for nodes with IPv6 enabled.
A dual-stack node will show both IPv4 and IPv6 addresses:
```txt
info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr4=/ip4/0.0.0.0/udp/9000, bindAddr6=/ip6/::/udp/9000

An IPv6-only node will only show the IPv6 address:

info: discv5 worker started peerId=16Uiu...t9LQ3, initialENR=enr:-Iu4QGE...WRwgiMo, bindAddr6=/ip6/::/udp/9000


Alternatively, the ENR can also be retrieved from the beacon node API by querying the [getNetworkIdentity](https://ethereum.github.io/beacon-APIs/#/Node/getNetworkIdentity) endpoint.

[ENR Viewer](https://enr-viewer.com/) provides a simple and convenient option to decode and inspect ENRs.
Expand Down Expand Up @@ -80,8 +86,7 @@ If your setup is behind a firewall there are a few ports that will need to be op
Ports that must be opened:

- 30303/TCP+UDP - Execution layer P2P communication port
- 9000/TCP+UDP - Beacon node IPv4 P2P communication port
- 9090/TCP+UDP - Beacon node IPv6 P2P communication port
- 9000/TCP+UDP - Beacon node IPv4 and IPv6 P2P communication port

Ports that must be protected:

Expand Down
Loading