Private nodes

Private Nodes - Additional Information

Defined: Private nodes are nodes you create that do not connect to the Allstar Network by default and are not connectable from the ASL network by default. But you can create any connection you can define manually correctly with them.

Numbering: The numbering system for them is under 2000 (ie 1999-0000) but best be advised to use 4 digit number to not confuse other parts of the dial plan in present or future expansion. If a private node is going to be connected to a ASL Public Network node, you may want to consider using a node number outside of the normal node used by examples in most how-to's such as 1999 because of a loopback protection in the code that prevents connection of the same node when you connect to other networks.

So, if you have a private node 1999 connected to your public node 29999 and you proceed to connect 29999 with some other system like 2135 that also has someone connected that has a private node 1999 connected, it will be refused. This has been the source of many hairs being pulled out when folks do not realize why they can not connect.

Of course, there is a more modern solution to fixing this issue. NNX or Node Number Extensions https://wiki.allstarlink.org/wiki/NNX NNX will create a extra digit on your existing node number, thereby making it 10 nodes, each unique and network connectable, or not. By using NNX, you can have a unique node number that can be set-up and not registered to the ASL network, thereby making it a private node. And of course, you could later change that to a public node just by putting in the registration string and review your settings to be sure they are public friendly.

Setting Up: Several areas will need to be edited.

Need a way to make local connection in the dial plan so...

extensions.conf:

[radio-secure] exten => 1950,1,rpt,1950 exten => 1951,1,rpt,1951

Define the node and how to connect to location and port...

rpt.conf

[1950] (the node number and normal node stanza with specific settings for the node +)

[nodes]  ; public and private node connections found late in the file 1950 = radio@127.0.0.1:4569/1950,NONE ; format= node# as dialed, radio @ ip (127.0.0.1 is local) : iax port on the machine / the actual number in the system pointed to, is remote base? 1951 = radio@127.0.0.1:4569/1951,NONE

Specific non-local standard connections

Here I am connecting to a private node on some other server using the same private node# in this system but you 'should' get the idea that it does not have to be the same number in both systems. But think about the actual need for it before you do it. Don't confuse yourself needlessly. In this example, it is a way to use a echolink connection across multiple servers and have control of it, if it is attached to a private node (1950). As you may not want to connect to a public node just for the echolink connection. Keeping it on a private node solves a good many issues and adds more possibilities across your servers.

1950 = radio@64.154.38.100:4570/1950,NONE ; elink 1950 on 29999

There is plenty of practical use in describing private nodes on other systems you control.

Here is one more example of a remote private connection...

1940 = radio@64.154.38.100:4570/1940,NONE ; ysf on p-node 1940 of 29999

It can simply add flexibility to all of your connection resources.