<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I'll make an attempt. <br>
<br>
42996=<a moz-do-not-send="true"
href="http://radio@127.0.0.1/42996,NONE">radio@127.0.0.1/42996,NONE</a>
defines the node which resides in your computer is local. The IP
address of 127.0.0.1 is local host, and local host resolves to
this IP. It's defined so Asterisk knows where on the AllStar
system this node exists. In this case - it's local to your
computer itself. If there is more than one node instance in a
single computer, they will be added as well, to 127.0.0.1 local
host.<br>
<br>
Other nodes can be established in this stanza to statically define
where (in the world) they exist. Say your node commonly connects
to another node that has a static IP address. This address could
be public or private. Defining a node and an IP in this stanza
eliminates the need for the node to resolve (using DNS lookup)
where the node resides. This can eliminate nodes not connecting
to one another if the AllStar nodes resolver system should become
unreachable. If a node is defined, it doesn't do the look-up, it
simply uses the static assignment to attempt the connection.
Nodes that are on an Internet connection which are offered public
IP addresses which change on occasion should not be defined
statically. This is the whole reason behind DNS, As IP's change
(because the ISP changes them) the system will keep track and
always know what IP address your node is located at, so others can
connect to you.<br>
<br>
I believe this area only relates to AllStar nodes - not EchoLink
nodes - BUT I'm not sure about this.<br>
<br>
Hope this helps..<br>
Kevin W3KKC<br>
<br>
<br>
On 11/10/2016 12:31 PM, DuaneVT . wrote:<br>
</div>
<blockquote
cite="mid:CABhxdJkrk4q3Y7xn08zFZymcg+J3Jp4=Ka3XEh6La0Y4Zs_dLA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">Would someone explain the
NODES stanza of rpt.conf?</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">[nodes]</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif">110=<a moz-do-not-send="true"
href="http://radio@127.0.0.1/110,NONE">radio@127.0.0.1/110,NONE</a>
; My node on this computer (local)</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif">If my public repeater/node is configured
to be repeater controller/Allstar/Echolink:</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif">
<ol>
<li>Should ANYTHING be in [NODES}?<br>
</li>
<li>Allstar would be: 42996=<a moz-do-not-send="true"
href="http://radio@127.0.0.1/42996,NONE">radio@127.0.0.1/42996,NONE</a>?</li>
<li>Does the Echolink node be added like Allstar?</li>
<li>Is 127.0.0.1 ALWAYS the default regardless of
router/firewall/IP address?</li>
</ol>
<div>I see this template everywhere in the rpt.conf setup with
no explanations as to details. Like do ALL nodes,
public/private/link/repeater get entered the same way except
for node numbers?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Duane KA1LM #42996<br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>