Skip to content

Private Network Setting, Port Forwarding

qcdll edited this page Dec 10, 2018 · 5 revisions

If your computer is connected to the Internet via a router (most likely the case if on a laptop/desktop at home or in office), ports that are open on your computer need to be mapped to ports on the router so that the outside world can communicate with your computer via those ports on your public IP.

Note that some VPS services provide public IP for your hosts, and if you have correctly set firewall (eg. security groups in AWS), there is no additional port forwarding needed.

Port Forwarding

There are two ways to setup port forwarding. You can either choose the provided upnp module or setup port forwarding manually. If you are on a private network (e.g. running QuarkChain cluster from a laptop which connects to a router and then internet), you can:

  1. Turns on UPnP module which automatically searches for a router that supports UPnP and set up appropriate port forwarding using UPnP protocol.

Run with --upnp to set up the port forwarding automatically, but there are chances that your router does not support UPnP. Please read the log messages from to see if the module has successfully set port forwarding.

  1. We recommend to set up port forwarding manually according to the router's instructions. In this case, you will need access to the router control. Like Ethereum, QuarkChain requires a UDP port for node discovery and a TCP port for peer connections, normally they would be the same port number. You can see the following video to learn how to setup port forwarding manually.

Both TCP and UDP for port 39291 need to be open. Here is an example of port forwarding.

NOTE if you run QuarkChain on AWS, you don't need this, because AWS assigns public IP to its instances.

Read for details on the command line flags of networking.

Tools is a good tool to test your settings