[arm-allstar] troubleshooting two nodes that can't connect

Patrick Perdue borrisinabox at gmail.com
Sat Nov 9 20:24:17 EST 2019 

As I said earlier, my node is directly connected to the internet. No 
ports to forward. Inbound to 4569 works. I have 7 nodes connected to me 
now, but these specific ones can't do it.


On 11/9/2019 7:49 PM, "larry via ARM-allstar" wrote:
> Patrick,
>
> I may have misunderstood your previous posts. It appeared you were 
> speaking about your own nodes not connecting, or others not connecting 
> to to them.
>
> Regardless of what you do public or private you will need to configure 
> your Router if using NAT on your LAN so that any incoming traffic can 
> route to the correct Allstar SERVER.
>
> Since you have more than one Allstar SERVER your IAX port is the key 
> to which Allstar SERVER the incoming request is sent to on your LAN. 
> Once routed to to proper SERVER. Asterisk takes over and attempts to 
> negotiate a connection between an incoming request and the node number 
> being requested.
>
> If you use Allstar externally off the Allstar system you will need to 
> configure both ends of ANY connection to recognize the opposite node.
>
> Unless your router does hairpin NAT you will need to define your LAN's 
> local nodes (as indicated) in each of your nodes rpt.conf files if you 
> plan to connect between them on your own LAN.
>
> According to the last post you mention details I either missed or were 
> not mentioned before. Therefore advice may be lacking or not totally 
> complete for what your issue is.
>
> No matter what you think running multiple Allstar Servers from the 
> same Public IP, your Router and the IAX port assigned to a particular 
> SERVER will be a major problem if you don't configure things correctly.
>
> Larry - N7FM
>
>
>
>
>
>
>
> On 11/9/19 2:01 PM, "Patrick Perdue via ARM-allstar" wrote:
>> OK, so I'm a little confused here.
>>
>> This appears to be the procedure for routing private to public nodes, 
>> or between private nodes on the same machine, which I'm not doing.
>>
>> I guess I could define these and see what happens, but that doesn't 
>> fix the actual problem.
>>
>> Clearly, some people can't connect to my node as normal without any 
>> defined route in iax.conf, which shouldn't be necessary in the first 
>> place, as this is a public node (the only one defined on this 
>> machine, in fact,) though most can. It seems this is primarily an 
>> issue with newer node numbers. Some clear nodes with older node 
>> numbers can connect just fine, so it's not strictly a problem with 
>> the configuration at the other end. Also, they can connect to my 
>> hamvoip node just fine (50368) but not my stock ASL (50631.)
>>
>> So, I'll define these lines in iax.conf for these specific nodes, but 
>> surely this will come up again, and I don't want to go around 
>> manually making exceptions for every node that can't connect because 
>> they are "not found!" according to 50631. Surely, something else is 
>> going on here.
>>
>>
>> On 11/9/2019 2:38 PM, "larry via ARM-allstar" wrote:
>>
>>> Patrick ....Might I ask, Have you checked these things on the nodes 
>>> that will not connect?
>>>
>>> Check your iax.conf file...
>>>
>>> [general]
>>> bindport= 4569 make the second nodes server be a different iax port 
>>> number (ie 4568)
>>>
>>> Assign different iax bindport port numbers for each different server 
>>> on the same LAN. Set Port Forwarding in your router to forward 
>>> incoming traffic to the proper IP for each of those assigned ports.
>>>
>>> Nodes will not connect inbound if the individual node's iax port is 
>>> not correct. You can connect outbound to other nodes but incoming 
>>> connects will fail.
>>>
>>> Also in many instances ... if running multiple Servers with nodes on 
>>> the same LAN you need enlightened rpt.conf [nodes] section on each 
>>> node of the opposite nodes existence. (Some router don't need this 
>>> but most do.)
>>>
>>> [nodes]
>>> ; Note, if you are using automatic updates for allstar link nodes,
>>> ; no allstar link nodes should be defined here. Only place a definition
>>> ; for your local (within your LAN) nodes, and private (off of allstar
>>> ; link) nodes here.
>>>
>>> 50663 = radio at 127.0.0.1:4569/50663,NONE
>>> 1999 = radio at 127.0.0.1/1999,NONE
>>> 50531 = radio at 192.168.x.x:4568/50531,NONE -192.168 x.x = your LAN IP
>>>
>>> On the 50531 nodes Server add needed info for 50663 at the bottom of 
>>> it's rpt.conf [nodes] section if you haven't already done this.
>>>
>>> Restart Asterisk  astres.sh or reboot each server for their changes 
>>> to take effect.
>>>
>>> See if that helps.
>>>
>>> Larry - N7FM
>>>
>>>
>>>
>>>
>>> On 11/9/19 9:30 AM, "Patrick Perdue via ARM-allstar" wrote:
>>>> 50631 is directly connected to the internet. The other two are 
>>>> behind NAT, and I don't think they work inbound anyway. 50631 
>>>> definitely should, though.
>>>>
>>>>
>>>> On 11/9/2019 10:41 AM, "Tony Ross via ARM-allstar" wrote:
>>>>> All 3 nodes exist in the database:
>>>>>
>>>>> # grep -E "50663|50631|50531" /var/log/asterisk/astdb.txt
>>>>> 50531|N1JBC|433.500|Barrington RI
>>>>> 50631|blind hams hub|<None>|Newark, NJ
>>>>> 50663|NE5V|<None>|Liberty Hill, Tx
>>>>>
>>>>> However, my node is unable to link to any of them, causing me to 
>>>>> suspect that none of them have UDP port 4569 forwarded through 
>>>>> their routers to them.
>>>>>
>>>>>
>>>>> On 11/9/19 2:52 AM, "Patrick Perdue via ARM-allstar" wrote:
>>>>>> Hi all:
>>>>>>
>>>>>> I have a stock ASL running in the cloud, which I'm using as a 
>>>>>> multi-mode bridge. For the most part, this is working well, but 
>>>>>> at least two (probably more) Hamvoip (clear node) boxes can't 
>>>>>> connect to my node, 50631.
>>>>>>
>>>>>> app_rpt.c:22685 rpt_exec: Reported node 50531 cannot be found!!
>>>>>>
>>>>>> app_rpt.c:20352 rpt_exec: Reported node 50663 cannot be found!!
>>>>>>
>>>>>> So far, these are the only two nodes that show up this way in the 
>>>>>> log.
>>>>>>
>>>>>> The common denominators are that they are both newish nodes, and 
>>>>>> they are both clear nodes. Other than that, I don't know what 
>>>>>> else to look for. 50663 has been active for less than 24 hours, 
>>>>>> but 50531 has been around for a while, and has never been able to 
>>>>>> connect to my 50631 in the nearly two weeks it's been operational.
>>>>>>
>>>>>> When I first brought the node online, 50531 reported not being in 
>>>>>> the database. So, I updated the database, and now it's just "not 
>>>>>> found!" So, I assume the problem is somewhere between my node and 
>>>>>> Asterisk's DNS. IAX2 show registry suggests that all is well.
>>>>>>
>>>>>> ASL_Box*CLI> iax2 show registry
>>>>>> Host                  dnsmgr  Username    Perceived Refresh State
>>>>>> 44.72.21.13:4569      Y       50631 45.79.180.62:4569 60 Registered
>>>>>> ASL_Box*CLI>
>>>>>>
>>>>>> I have a cron running astdb.php every morning at 3:01.
>>>>>>
>>>>>> What else can I look for?
>>>>>>
>>>>>> Thanks and 73
>>>>>>
>>>>>> de
>>>>>>
>>>>>> KE4DYI
>>>>>>
>>>>>> _______________________________________________
>>>>>>
>>>>>> ARM-allstar mailing list
>>>>>> ARM-allstar at hamvoip.org
>>>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>>>>
>>>>>> Visit the BBB and RPi2/3 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/3 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/3 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/3 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/3 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/3 web page - http://hamvoip.org

More information about the ARM-allstar mailing list