Qortal Project

The future of blockchain platforms

User Tools

Site Tools


Sidebar

Qortal Project Wiki

QORT Project Model

Important Notices - MUST READ

QORT Minting

QORT Communications Plugin

QORT Trade Portal

QORT Voting System

QORT Data Hosting

QORT Hardware

Frequently Asked Questions (FAQ)

QORT How-To Guides

port_forwarding

Port Forwarding

Port forwarding is necessary for helping you node stay synced and connected to peers. This will increase connections/peers for your Qortal core node(s).

Find your router using one of the sites listed, port to forward:12392, Protocol: TCP , IP address: local lan IP of your Qortal node( as defined in your router)

https://www.noip.com/support/knowledgebase/general-port-forwarding-guide/

https://must-know-mac.blogspot.com/2008/07/how-to-port-forward-time-capsule.html

How to Set Up Port Forwarding on a Router: http://www.wikihow.com/Set-Up-Port-Forwarding-on-a-Router select your laptop and tcp port # 12392

Here you can find step by step info for specific router: https://portforward.com/

Static IP guide: https://www.coolblue.nl/en/advice/assign-fixed-ip-address-router.html

Port forwarding guide: https://www.lifewire.com/how-to-port-forward-4163829

Port forwarding for multiple nodes on 1 IP address:

To port forward multiple nodes on one (external) IP address (which is most everyone)

You will simply set your EXTERNAL port to a different port and leave the INTERNAL port at 12392 on the other INTERNAL IP address for the other node… for example:

We'll say you have 4 nodes in your house and they are on IP addresses 192.168.0.100 through .104

node 1 - 192.168.0.100 node 2 - 192.168.0.101

…and so on… (these are theoretical IP addresses, obviously you will have to find your internal IP address of the nodes on your network using either ipconfig on windows or ifconfig on linux, or a network scanner.)

We will want to setup both static assignment in the router (or set the IP address manually on each node, which is not the preferred method, but will also work) so that the nodes get the SAME INTERNAL IP every time… Then we will want to port forward from the EXTERNAL port (on varying numbers as I'll explain further below) to the INTERNAL port 12392 on each node on your network. To accomplish this, after you have set your static assignment, or assigned each node's internal IP manually, so it won't change upon reboot, etc.

You will use port forwarding with the following potential ports for each node.

The following will show the EXTERNAL-INTERNAL port numbers (you can use these ports or ANY open external port, in to 12392, it doesn't matter WHICH port, as long as it isn't an existing port forwarding rule on that external port)

node1 port forwarding setup - 12392-12392 node2 port forwarding setup - 22392-12392 node3 port forwarding setup - 32392-12392 etc.

All you're doing is using a DIFFERENT EXTERNAL PORT, forwarded in to the SAME INTERNAL PORT on a DIFFERENT INTERNAL IP ADDRESS.

you can only have ONE SERVICE on each EXTERNAL PORT, because you only have ONE EXTERNAL IP ADDRESS for your internet connection. So your router will only let you port forward one service on each port. Therefore you have to use a DIFFERENT EXTERNAL PORT forwarded in to the SAME INTERNAL PORT on each INTERNAL IP ADDRESS (your LAN IP 192.168.0.100-104 in this example)

Advanced instructions relating to Port Forwarding on more advanced set up:

It is never a good idea to add your node in DMZ. That will stop all the DPI and SPI and if you have the API enabled and white listed, you are putting your computer at risk! DMZ bypasses the SPI mechanism of the built in filters and all the internet traffic can reach your node directly. SPI (stateful packet inspection) firewall protects you by examining incoming packets against existing connections. Also add UPnP text. If a router has it then it must be enabled. UPnP or NAT-pmp opens dynamic port ranges to act as an assist for SPI. Enabling NAT/UPnP solves problem for the most but unfortunately due to the torrent p2p laws most ISPs now filter ports by default at the client side so port forward is also needed. For example:

219.88.183.49:12392 (qortal-1.2.3-2df0453), height 42318, sig: PXNoJM7W, ts 2020-07-31 17:17:24

192.168.100.83:44380 (qortal-1.2.3-2df0453), height 42318, sig: PXNoJM7W, ts 2020-07-31 17:17:24

Look at the second IP address with a dynamic port. This is UPnP working. Instead of 12392 , it has opened a 44380 port for TCP handshake / connect / ACK.

port_forwarding.txt · Last modified: 2021/08/06 22:38 by gfactor