Qortal Project

The future of blockchain platforms

User Tools

Site Tools

Trace:
port_forwarding_upnp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
Last revisionBoth sides next revision
port_forwarding_upnp [07/17/2022 09:26] – created gfactorport_forwarding_upnp [07/21/2022 10:07] – caldescent
Line 2: Line 2:
 {{:qortal_official_logo_transparent_.png?400|}} {{:qortal_official_logo_transparent_.png?400|}}
  
-**We need as many people as possible to be sure they have port forwarding setup on as many of their nodes as possible! This will ensure the network growth doesn't hit a point where there aren't enough peers allowing incoming connections.**+**We need as many people as possible to be sure they have port forwarding setup on as many of their nodes as possible!** This will ensure the network growth doesn't hit a point where there aren't enough peers allowing incoming connections.
  
-We expect there to be significant growth over the next 6-12 months, so we need everyone to be aware of this, and to help us as much as possible with [[Port Forwarding]] and sharing the newly port forwarded internet IP and port connections with the rest of the network by adding a peer with that information.+We expect there to be significant growth over the next 6-12 months, so we need everyone to be aware of this, and to help us as much as possible with port forwarding and sharing the new internet IP and port connections with the rest of the network by adding a peer with that information.
  
-**Port Forwarding** - is the act of allowing INCOMING connections to your Qortal Node. This act greatly benefits the entire network, by having more overall nodes that can be connected IN to. By default most routers only allow OUTBOUND connections, therefore if you do NOT specifically allow incoming connections on a specific port, you can only connect OUT to computers on the Internet.+**Port Forwarding:** a router setting to allow INCOMING connections to your Qortal Node. This greatly benefits the entire network, by having more overall nodes that can be connected IN to. By default most routers only allow OUTBOUND connections, therefore if you do NOT specifically allow incoming connections on a specific port, you can only connect OUT to computers on the Internet.
  
 Recently, we have made a change in the Qortal Core, that will allow the use of what's called uPnP or (Universal Plug and Play). What this means, is that if uPnP is enabled on your router (which by default most home routers have it enabled) it will allow the Qortal Core to automatically attempt to Port Forward the Qortal P2P port (12392 by default) into your node. Recently, we have made a change in the Qortal Core, that will allow the use of what's called uPnP or (Universal Plug and Play). What this means, is that if uPnP is enabled on your router (which by default most home routers have it enabled) it will allow the Qortal Core to automatically attempt to Port Forward the Qortal P2P port (12392 by default) into your node.
Line 22: Line 22:
 For example, with port 22392, Qortal will NOT by default know this UNLESS you ADD PEER from another node AND add the peer with your external **internet IP** (which you can find easily by going to https://canhazip.com or doing ```curl https://canhazip.com``` from terminal). For example, with port 22392, Qortal will NOT by default know this UNLESS you ADD PEER from another node AND add the peer with your external **internet IP** (which you can find easily by going to https://canhazip.com or doing ```curl https://canhazip.com``` from terminal).
  
-Let’s say my home's external IP is 1.2.3.4 and I have 3 nodes on my home LAN on 192.x.x.x with correct port forwarding and ports 12392, 22392, and 32392. I would then go to another node and **ADD PEER** and add **1.2.3.4:22392** and **1.2.3.4:32392** in my node, which will then broadcast to the rest of the Qortal network that there is an available peer that can be connected to on those ports. Then the rest of the network will be aware of it automatically, and you'll get full peers on your nodes.+Let’s say your home's external IP is 1.2.3.4 and you have 3 nodes on my your LAN on 192.x.x.x with correct port forwarding and ports 12392, 22392, and 32392. You would then go to another node and **ADD PEER** and add **1.2.3.4:22392** and **1.2.3.4:32392** in your node, which will then broadcast to the rest of the Qortal network that there is an available peer that can be connected to on those ports. Then the rest of the network will be aware of it automatically, and you'll get full peers on your nodes.
  
-Hopefully this announcement has enough detail for everyone to understand, if you have any questions please feel free to reach out, there are many brilliant techs in our community who understand port forwarding and can assist you. (and I'm not so bad at it myself, heh.)+"Add Peer" has always been a bit hit and miss, particularly in knowing if it has worked or not. If you find that the entry doesn’t appear in the peer list, you only need to worry about this if you are getting less than 32 connections on the laptop node though. If you have 32 connections then everything is set up correctly and there's no need to add the peer. 
  
-I think even some of our more techie members may not have known about the **need to add the other non-default port forwarded nodes, in 'add peers'** so I wanted to make sure everyone was aware of this as well. +The “Add Peer” method is to inform the network that you are running a Qortal node on a port other than the default 12392. If it's on the default, the network will find it automatically, but if it's on something other than 12392 the other nodes won't know which port to connect to, and so that node won't receive inbound connections. Adding it as a node solves this, as it announces the port to the network. This can't be done automatically as the node itself doesn't generally know its external port - only the router and the user know that. Once a node has 32 connections it means its getting the full amount of inbound connections (assuming default settings) and therefore the network must know about the custom external port.
  
-Thank you and sorry for the long post!+“Add Peer” may need to be retried if it doesn't work the first time. It might take a while to propagate the network, so may require checking back an hour or so later. 
 + 
 +Go to the [[Port Forwarding]] page under the How-To Guides for more information. 
port_forwarding_upnp.txt · Last modified: 11/23/2022 19:15 by gfactor

Page Tools