Background
...
RNode supports the UPnP protocol, which is commonly available on retail routers today. When RNode 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 RNode as a validator without having to reconfigure their network.
Note - Node operators running Docker on Mac OS X will not be successful running RNode with UPnP. If you want to run with Docker on Mac OS X, you must configure static NAT and port forwarding manually. See "Routers without UPnP Support" below.
Routers without UPnP Support
...
- The machine that is running RNode has to be connected to the router and turned on.
- In the router configuration interface, configure static NAT for the machine.
- Configure port forwarding for ports 30300 40400 - 3033040430
When configuration is complete, it should look something like this:
| Device | Allowed Applications | Protocol | Port Number |
|---|---|---|---|
| My_RNode_server | RChain | tcp | 3030040400-3033040430 |
Running Docker
If you wish to run rNode from within Docker, you must still configure your network settings to match the supported network configuration. Additionally, you must run Docker with explicit port mapping options. By default, Docker runs in network bridge mode.
...
| Code Block |
|---|
docker run -it -p 3030440400:3030440400 --name my_rnode_server -v "$HOME/var":/var rchain/rnode:latest run --default-timeout 6000 --no-upnp -b rnode://address_of_bootstrap_node |
Note - Node operators running Docker on Mac OS X will not be successful running RNode with UPnP. If you want to run with Docker on Mac OS X, you must configure static NAT and port forwarding manually. See "Routers without UPnP Support" below.
Successful Connection
You will know if that your node has connected successfully if you see connection messages in the console. Example:
...