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

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
port_forwarding_upnp [07/21/2022 06:59] – gfactorport_forwarding_upnp [07/21/2022 10:07] – caldescent
Line 26: Line 26:
 "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.  "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. 
  
-The "Add Node" 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.+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.
  
-Definitely worth trying the Add Peer some more times then. It might take a while to propagate the network, so worth trying a few more times then checking back an hour or so later.+“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.  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