This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
port_forwarding [06/17/2023 12:14] – crowetic | port_forwarding [06/17/2023 12:33] (current) – cleaned up, made much simpler crowetic | ||
---|---|---|---|
Line 7: | Line 7: | ||
===== Single or Multiple nodes With uPnP Enabled===== | ===== Single or Multiple nodes With uPnP Enabled===== | ||
- | **Option 1:** In this case, you only have ONE device that is acting as a blockchain | + | **Option 1:** If you have only ONE node, and your router has **uPnP enabled**, you will not need to do anything, your single node will simply start obtaining incoming connections. |
- | If you ARE going to use uPnP, **you can have MULTIPLE nodes** on the same LAN obtaining incoming connections **via uPnP** by simply modifying a SINGLE setting in **settings.json**: | + | If you ARE going to use uPnP, **you can have MULTIPLE nodes** on the same LAN obtaining incoming connections **via uPnP** by simply modifying a SINGLE setting in **settings.json** |
- | < | + | Simply edit **settings.json** for the nodes ASIDE FROM THE FIRST NODE, and change the listenPort |
- | { | + | |
- | "listenPort": 22392 | + | |
- | } | + | |
- | </ | + | |
- | The above settings would be fine for your SECOND node, you do not need to do anything for the FIRST node, as it will run on the default port 12392. Any SUBSEQUENT node you will need to add ONLY the above setting in settings.json, | ||
- | |||
- | **Option 2:** If your router does NOT offer uPNP, you will need to configure port forwarding (on your router) AND disable the default uPnP in your settings.json (on your node): | ||
- | |||
- | 1) Stop the core on your node by opening the command terminal and entering: | ||
- | < | ||
- | |||
- | 2) Login to your router and set the IP address of the node to " | ||
- | |||
- | 4) In your router, configure port forwarding for this device: | ||
- | Inbound: 12392 (sometimes ‘inbound’ is titled ‘internal’) | ||
- | Outbound 12392 (sometimes ‘outbound’ is titled ‘external’) | ||
- | Protocol: TCP | ||
+ | < | ||
+ | " | ||
+ | }</ | ||
- | ===== More Than One Node On Your Home Network (no uPnP)===== | + | =====Networks Without |
+ | On networks that do NOT have uPnP available, you will need to **enable port forwarding and static assignment** to obtain incoming connections. Doing this will be DIFFERENT on any given router. You will need to obtain instructions for your router from an internet search as far as the terminology and specific settings that you will need. | ||
- | If you have more than one node on your network, then you’ll want to: | + | We will provide **basic overall instructions** here for understanding. |
- | + | ||
- | | + | |
- | | + | |
- | 1) Set the IP address of each node to STATIC. This will prevent | + | 1. Setup **static assignment** for each node machine on your LAN. - Static assignment ensures that the machine |
- | 2) Set port forwarding for each node as shown in the following. Internal and external | + | 2. Establish a **port forwarding |
- | **Node 1** Internal: 12392 External: 12392 | + | **You do NOT need to modify any further settings on your NODE**, simply add new entries for each node machine with a **DIFFERENT EXTERNAL PORT**. See below for an overall idea... |
- | **Node | + | **Node |
- | **Node | + | **Node |
- | **Node | + | **Node |
- | etc. | + | etc... You can use ANY port you like for the different external port, as long as it **doesn' |
- | (Just change | + | **All that needs to change |