NNX node on different locations and different computers under a VPN

AllStarLink
1

Hello community. I have tried with no success to run two nodes installed on two rpis under the same IP (VPN). This is using ASL3 on both machines.

Node 484550
iax.conf
bindport = 4570
bindaddress = 0.0.0.0

rpt.conf
node 484550 pointing to 127.0.0.1
node 484551 pointing to 192.168.20.51:4569

using http registration file and the node 484550 password

Node 484551
iax.conf
bindport = 4569
bindaddress = 0.0.0.0

rpt.conf
node 484551 pointing to 127.0.0.0.1
node 484550 pointing to 192.168.20.50:4570

using the http registration file and the node 484550 pasword

on the VPN I have the iptables set to forward UDP port 4570 to the 484550 machine and UDP 4569 to the 484551 machine.

This yields to having the node 484550 showing up with port 4569 and 4570 some times, I interpret this as both rpis registering themselves with the same password but different port.

Regarding this new number scheme, does this mean that I may connect 484550 to node 27339 and node 484551 to node 48496, being each node on a different radio serving a different location? Or is this just to link al remaining 9 nodes back to 484550 and repeat whatever the node is connected to?

Thank you.

TG9AOR

2

Are you really trying to have 484551 register as 484550? Why?

3

Also, because you have two servers (one for each node) do you also have two servers configured in the AllStarLink portal ... with each node setup to use it's own portal server?

4

Hello Sir and thank you for your reply. Therein lies the issue, in my misunderstanding as to soliciting servers. I do not know if then I may apply for another server and use the nnx incremental node for it or how to go about that. I read about more than one node in a nat or a network but it does not mention this.

As we are in this subject, if I were to expand on node 484550 as to have all private nnx nodes repeat what it connects to, on each computer do I put 484550's credentials? That is the part I am not clear.

PC with node 484550 uses its respective password
PC with private node 484551 on another PC would then use what password, or is it the server's (484550) password.

For the sake of brevety I am not detailing the pointing of private nodes to its server and vice versa.

Thanks

TG9AOR

5

I wanted to expand the server which has Node 48455, and so I went ahead and requested the change to NNX. But I lack the knowledge to expand the RF network either by having the nnx incremental nodes repeat the server's node or to have a separate nnx node for my use and leave the rest linked up to 484550.

TG9AOR

6

Essentially, on the portal :

  • in the portal, you want to have a unique "server" for each CPU (PC, RPi, ...)
    • a "server" can support a single node OR multiple nodes
  • in the portal, each "node" should point to its "server"

For the actual server(s) :

  • the "server" will have a single IP (possibly a public IP, more likely a NAT'd IP on your local LAN) and IAX port (4569, ...)
    • if you have a server supporting multiple nodes they will all be using the same IP address and port
  • each "node" should be registering itself to the network

Re: NNX. This is just a quick way for you to get additional node #'s. Once allocated they are just node #'s.

Have a look at :
Multiple Nodes on the Same Network
Node Number Extensions (NNX)

7

Thank you Sir, I really appreciate your reply and information. I have created another server and will point the simplex node to it.

Thanks and 73

TG9AOR