[arm-allstar] node connections

[Tim Sawyer]

Doug,

Good wright up. I would only add that the port, if different from the
default, must not only be defined in the [nodes] stanza but also on the
AllStar Portal. That's because the port that's defined on the portal is the
port is put into rpt_extnodes.

This step is often forgotten and can be a cause of inbound connects not
working.

On Sun, Aug 16, 2015 at 5:20 AM, Doug Crompton <doug at crompton.com> wrote:

> I guess I should do a how-to on this since this question gets asked so
> often!
>
> When connecting nodes they need both the information to connect and the
> path to connect. The information to connect is found either in the
> rpt_extnodes file (in /tmp on the RPi2 and BBB and /var/lib/asterisk in
> Acid) or in a specific path entered in your rpt.conf file under the [nodes]
> stanza.
>
> To check use grep on the database or view the nodes section in rpt.conf
>
> grep 42285 /tmp/rpt_extnodes
>
> grep 28302 /tmp/rpt_extnodes
> 28302=radio at 50.93.230.87:4569/28302,50.93.230.87
>
> As you can see one node turned up an address the other did not here this
> morning but perhaps the 42285 node is off the air.
>
> Nodes have to have routing information at BOTH ends to work. This includes
> the IP address AND proper port. Often ports are the issue because people do
> not specify them if they are different then the default 4569. The port must
> be defined in the local ( [nodes] stanza ) information if it is different
> than the default.
>
> The master database ( rpt_extnodes ) is usually used to determine how to
> get to another node but for local or private connections it is often
> specifically defined in the rpt.conf [nodes] stanza.
>
> You can use the Asterisk client  (asterisk -rvvv at the Linux prompt) to
> troubleshoot this as it gives messages at BOTH ends about what went wrong.
> If you connect from one node to another and you do not see any messages at
> the node you are connecting to then it did not get through and you can
> suspect a routing problem due to a misaddress or port either in the
> database or port forwarding if it is outside your LAN. Of course outside
> your LAN it could also be a hopefully temporary Internet routing problem
> beyond your control.
>
> Some more background can be found here -
>
>
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/multi-server%20howto.pd
> f
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Sun, 16 Aug 2015 11:35:34 +0000
> From: n7jys at yahoo.com
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] node connections
>
> I have put two new nodes on line and all is working great. Yesterday my
> 42285 node
>  stopped being able to connect  to the reset of my nodes 2351,2578,28302.
> But
> it can connect to any other node that's on line.
>
> 2351,2578,28302 cannot connect to 42285 but they all will connect to any
> other nodes on line.
> This is strange behavior and not understanding why this is happening.
>
> 2351,2578,28302 all live on one RPI2 and on its own IP at my repeater
> site. 42285 is on
> an ACID install P4 computer at my home qth and its own IP. Port 4569 is
> forward correctly
> on both routers as they all will connect to other nodes on line. Both IP
> address at my repeater
> site and at my home are from the same provider.
>
>
>
> Eric (N7JYS) Marshall's Communications
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
> BBB and RPi2 web page - http://hamvoip.org
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>



-- 
--
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150816/4ff10a9d/attachment.html>