Allowing outbound TCP/UDP traffic from any port will help Prysm find peers.Īfter we discover peers, we dial them through this port to establish an ongoing connection for libp2p and through which all gossip/p2p request and responses will flow. To discover peers, Prysm's beacon node dials out through random ports. Inbound and outbound traffic should be allowed through this port only if your local validator is connecting to a remote beacon node. Your validator uses this port to connect to your beacon node via gRPC. Inbound and outbound traffic should be allowed through this port only if your local beacon node is connecting to a remote execution node. Your beacon node connects to your execution node's Engine API using this port. This port generally shouldn't be exposed to the outside world. You (and apps) can use this port to check beacon node status and query consensus-layer chain data. This is the JSON-RPC port for your beacon node's Query API. You (and apps) can use this port to check execution node status, query execution-layer chain data, and even submit transactions. This is the JSON-RPC port for your execution node's Query API. The following firewall rules should be configured on any local operating system, third-party software, or hardware firewalls between your nodes and their internet connection: Port/protocol As a security best practice, we recommend blocking inbound traffic across all local ports, allowing inbound traffic on a port-by-port basis. To establish these connections, your client software needs to be able to send and receive messages through specific ports. Execution nodes try to connect to many peer execution nodes.Beacon nodes try to connect to many peer beacon nodes.This execution node can be local or remote. Beacon nodes try to connect to a single, dedicated execution node.Validator nodes try to connect to a single, dedicated beacon node. Your node and validator will try to establish several types of connections: These are optimizations targeted at power users. Note that as long as you can complete the Status checklist without error, this isn't required. Verify your node's discoverability by using a TCP lookup tool.Configure your beacon node to broadcast your public IP address.Configure your router for improved peer-to-peer connectivity.Determine your IP addresses so you can configure your router and beacon node.Configure your firewall for improved peer-to-peer connectivity.In this how-to, we'll walk through the following tasks: Improved peer-to-peer connectivity benefits the broader Ethereum ecosystem by making blockchain data more available, and it can also help your validator find more work (and earn a little more ETH). In some cases, small changes to your port and firewall configuration can significantly improve your node's peer-to-peer connectivity. Not familiar with nodes, networks, and related terminology? Consider reading Nodes and networks before proceeding.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |