[arm-allstar] Node not registered

[Mr. Possum (Bill)]

I could be wrong here, but are you using the same ports in between the two Pi's?  It sounds like a port forwarding issue for IAX - maybe...  Each Pi has to have their own ports if they are co-located behind the same router - AND they have to be configured on Allstar.org to those different ports too...

Bill - N5MBM


      From: Barry Buelow via arm-allstar <arm-allstar at hamvoip.org>
 To: arm-allstar at hamvoip.org 
Cc: Barry Buelow <iabarryyy at gmail.com>
 Sent: Saturday, February 24, 2018 9:47 PM
 Subject: [arm-allstar] Node not registered
   
I have 2 nodes sitting side by side. Both are RPIs.  One will disappear 
from the list on ASL and preventing other stations from connecting. I 
was away for a few weeks and a friend sent me an email about it. I 
immediately was able to access the missing node via SSH. It all looked 
ok and I was able to do outgoing pings.  A manually issued reboot.sh did 
execute, but the node still did not appear on ASL.

When I got home, the node appeared to be alive as it was doing time/temp 
on the hour and I could access it via SSH, but still not listed on ASL.  
Another reboot.sh had no effect on the ASL list.

I rebooted the router and things started working again, with the node 
showing on ASL.  This behavior had been happening before, so I bought a 
new router and things act the same with the new router (different 
brand). Through all of this, the adjacent node just played along fine.

Is there anything I can do from SSH (or a script) that would allow the 
node to determine this unregistered condition and announce the fact?

Also, is there a lock or buffer to clear which would allow reboot.sh to 
register?

thanks,

Barry w0iy


_______________________________________________

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