Supported Network Configuration


Background

The Node software runs as a server on the CasperLabs network. The CasperLabs network is a peer to peer network. For a Node server instance to properly communicate with the rest of the network, secure bi-directional communication must be possible. Validators must be able to send queries to each other and must be able to receive connections from other validators.

Supported Network Configuration

The communications software supports this network configuration.

Server → Router → Internet

The Node server needs to be directly connected to the router.  The router needs to either support UPnP or have static NAT with port forwarding configured for ports 40400 - 40404.  If you wish to use a different set of ports, specify those at runtime with the corresponding flags. See the node's help file for more details on the required flags.


Ports Used
DescriptionDefault ValueOpen
Network port to use for intra-node gRPC
communication
40400Required
Port used for external gRPC API, e.g.
deployments
40401Optional
Port used for internal gRPC API, e.g.
diagnostics.
40402Optional
HTTP port for utility services: /metrics,
/version and /status
40403Optional
Kademlia port used for node discovery40404Required

How Universal Plug and Play (UPnP) Works

Node supports the UPnP protocol, commonly available on retail routers today. When the system detects a UPnP gateway device, such as your wireless router, the node software will configure the router's firewall rules automatically. In many small business and home networks, this allows the user to run the node as a validator without having to reconfigure their network.


Test your network

A success message means your configuration should be successful connecting to the network.

An error message means your network configuration may not be successful connecting to the network. You need to investigate your configuration and possibly make changes.