[arm-allstar] Connection failed

[Larry]

Strange Glenn,

Sorry to say I run a couple IRLP nodes on my repeaters but I haven't 
migrated them to my Allstar Hardware yet so I am not familiar with any 
configs that need to changed.
I was taking a shot in the dark that you may have forgot to edit the 
Port Forward settings in your router and didn't re-direct it from the 
IRLP Pi3's IP to the Allstar node's IP address.

Are the 2 nodes you can connect with Allstar capable nodes with IRLP on 
them as well?

Larry - N7FM



On 12/3/18 8:47 AM, "Glenn via ARM-allstar" wrote:
> "Larry via ARM-allstar" wrote:
>> Did you forget to reassign the port forwarding to the new Pi3's IP 
>> address?
>>
>> Larry - N7FM
>>
>>
>> On 12/2/18 1:56 PM, "ka5tkn--- via ARM-allstar" wrote:
>>> Howdy folks,  I have AllStar,Echo,supermon and Iaxrpt workin fine, 
>>> with a
>>>> lot of help from Doug.Thought I would move the IRLP node off my 
>>>> other Pi3
>>>> to my AllStar node...I followed all the how to for the install...After
>>>> install, ck the IRLP status page it showed stn3702 idle..Now the help
>>>> needed.  I have found that I have only been able to connect to one
>>>> node...All other attempts I get 'connection failed'.  I have no 
>>>> idea what
>>>> to check.Any suggestion Glenn K5CODAllStar 47954Echo 4345IRLP 3702
>>>>
>>>
>>> Sent via the Samsung Galaxy Note5, an AT&T 4G LTE smartphone
>>> _______________________________________________
>>>
>>> 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
> Tnks for reply Larry, All the ports are forward correct.. I can 
> correct to two nodes here in Texas.(3337 and 3639) all the rest I get 
> 'connection failed'
> here is the correct connect..
>
> Mon Dec 03 09:06:23 CST 2018 [irlp_fullreset] Full Reset completed.
> Mon Dec 03 09:06:24 CST 2018 [call] IRLP call initiated to stn3337 
> KD5OXM-R
> Mon Dec 03 09:06:24 CST 2018 [call] The nodes IP is determined to be 
> 12.44.136.99
> Mon Dec 03 09:06:24 CST 2018 [control] KD5OXM-R stn3337 reply 
> connectok ADPCM
> Mon Dec 03 09:06:24 CST 2018 [on] stn3337 ADPCM 12.44.136.99
> Mon Dec 03 09:09:58 CST 2018 [end] Node Disconnect from stn3337 KD5OXM-R
> Mon Dec 03 09:09:58 CST 2018 [dropcall] Call dropped.
>
> and the failed call connect
>
> Mon Dec 03 09:00:25 CST 2018 [irlp_fullreset] Full Reset completed.
> Mon Dec 03 09:00:25 CST 2018 [call] IRLP call initiated to stn3751 
> K5RNB-R
> Mon Dec 03 09:00:26 CST 2018 [call] The nodes IP is determined to be 
> 65.36.39.4
> Mon Dec 03 09:00:26 CST 2018 [control] K5RNB-R stn3751 reply connectok 
> ADPCM
> Mon Dec 03 09:00:27 CST 2018 [on] stn3751 ADPCM 65.36.39.4
> Mon Dec 03 09:00:50 CST 2018 [end] Node Disconnect from stn3751 K5RNB-R
> Mon Dec 03 09:00:50 CST 2018 [dropcall] Call dropped.
>  between 0900:27 and 0900:50 it does not connect 'times out'
> I think its a timming issue but I have no idea ...
> Glenn k5cod
>
> _______________________________________________
>
> 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