To let the Blockchain CLients communicate correctly, the ports, e.g., data communication channels, must be enabled on the node and the router. For each supported blockchain client, there are different ports to open.
Each supported client has different ports for various purposes that have to be open for a clear connection:
To discover peers of other nodes, all outbound traffic should be allowed across all UDP and TCP ports when using Prysm and Lighthouse.
| CLIENT | DESCRIPTION | PORT | TCP | UDP |
|---|---|---|---|---|
| GETH | Execution Chain Data Channel | 30303 | X | |
| GETH | Execution Chain Discovery | 30303 | X | |
| ERIGON | Execution Chain Data Channel | 30303 | X | |
| ERIGON | Execution Chain Discovery | 30303 | X | |
| LIGHTHOUSE | Beacon Communication and Data | 9000 | X | X |
| PRYSM | Beacon Gossip, Requests, and Responses | 13000 | X | |
| PRYSM | Beacon Discovery, Requests, Data Exchange | 12000 | X |
Within the monitoring section of this guide, you can find other internal communication channels that will be used for monitoring.
References: