From gerf at gerf.com Tue May 14 14:21:53 2019 From: gerf at gerf.com (Gerry Filby) Date: Tue, 14 May 2019 11:21:53 -0700 Subject: [Arm-allstar-irlp] Problems connecting to IRLP reflectors Message-ID: <14afb32c-8e36-bbdd-fe43-0708eed290cd@gerf.com> I don't use IRLP a whole lot, but just noticed that I can't connect to any of the reflectors - the connection times out. I CAN connect to 89999 and the transmit and playback works fine. I've double checked the configuration per the how-to document and all seems fine - including port forwarding at my firewall. It used to work and nothing has changed in many months. Below is the contents of the IRLP log if it's any help. My station # is stn3366. Any ideas ? Gerry W6WNG File: /home/irlp/log/messages ----------------------------------------------------------------- Tue May 14 10:44:45 PDT 2019 [update:hosts] Gzipped file was unavailable, downloading hosts.update direct. Tue May 14 10:44:45 PDT 2019 [update:hosts] ERROR: Hosts file seems invalid. Tue May 14 10:44:45 PDT 2019 [update:hosts] Update completed. Tue May 14 10:44:55 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:44:56 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:45:11 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:45:11 PDT 2019 [connect_to_reflector] Reflector ref910/Ch-9 CODEC chosen is UNCOMP. Tue May 14 10:45:13 PDT 2019 [update:hosts] Update completed. Tue May 14 10:45:49 PDT 2019 [failure] timeout connect Tue May 14 10:45:50 PDT 2019 [irlp_reset] Reset completed. Tue May 14 10:46:12 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:46:12 PDT 2019 [connect_to_reflector] Reflector ref922/Ch-9 CODEC chosen is GSM. Tue May 14 10:46:28 PDT 2019 [failure] timeout connect Tue May 14 10:46:28 PDT 2019 [irlp_reset] Reset completed. Tue May 14 10:47:26 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:47:26 PDT 2019 [connect_to_reflector] Reflector ref910/Ch-0 CODEC chosen is UNCOMP. Tue May 14 10:47:42 PDT 2019 [failure] timeout connect Tue May 14 10:47:42 PDT 2019 [irlp_reset] Reset completed. Tue May 14 10:48:57 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:48:57 PDT 2019 [connect_to_reflector] Reflector ref999/Ch-9 CODEC chosen is ADPCM. Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Timeout is disabled. Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Node Connected to base reflector ref999/Ch-9 Tue May 14 10:49:59 PDT 2019 [end] Node Disconnect from ref9999 Tue May 14 10:50:14 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 10:50:14 PDT 2019 [connect_to_reflector] Reflector ref910/Ch-0 CODEC chosen is UNCOMP. Tue May 14 10:50:29 PDT 2019 [failure] timeout connect Tue May 14 10:50:30 PDT 2019 [irlp_reset] Reset completed. Tue May 14 11:12:29 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 11:12:29 PDT 2019 [connect_to_reflector] Reflector ref910/Ch-0 CODEC chosen is UNCOMP. Tue May 14 11:12:45 PDT 2019 [failure] timeout connect Tue May 14 11:12:45 PDT 2019 [irlp_reset] Reset completed. Tue May 14 11:13:08 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 11:13:08 PDT 2019 [connect_to_reflector] Reflector ref910/Ch-9 CODEC chosen is UNCOMP. Tue May 14 11:13:24 PDT 2019 [failure] timeout connect Tue May 14 11:13:25 PDT 2019 [irlp_reset] Reset completed. Tue May 14 11:14:30 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 11:14:30 PDT 2019 [connect_to_reflector] Reflector ref960/Ch-0 CODEC chosen is UNCOMP. Tue May 14 11:14:46 PDT 2019 [failure] timeout connect Tue May 14 11:14:46 PDT 2019 [irlp_reset] Reset completed. From tpwaterman at gmail.com Tue May 14 14:58:30 2019 From: tpwaterman at gmail.com (Pres W) Date: Tue, 14 May 2019 14:58:30 -0400 Subject: [Arm-allstar-irlp] Problems connecting to IRLP reflectors In-Reply-To: <14afb32c-8e36-bbdd-fe43-0708eed290cd@gerf.com> References: <14afb32c-8e36-bbdd-fe43-0708eed290cd@gerf.com> Message-ID: Gerry, I understand you feel your ports are in order, but it's worth going though BOTH Allstar and IRLP ports, paying particular attention to UDP vs TCP selection. From memory: 2074-2093 UDP ; 15425-15527 TCP and the usual Allstar ports 4569 UDP; and 5038 and 222 TCP (plus Echolink if used). Routers do funny things now and then, including letting previously reserved/locked devices wander. 73 Pres W2PW On Tue, May 14, 2019, 2:22 PM "Gerry Filby via ARM-allstar-irlp" < arm-allstar-irlp at hamvoip.org> wrote: > I don't use IRLP a whole lot, but just noticed that I can't connect to > any of the reflectors - the connection times out. > > I CAN connect to 89999 and the transmit and playback works fine. > > I've double checked the configuration per the how-to document and all > seems fine - including port forwarding at my firewall. > > It used to work and nothing has changed in many months. > > Below is the contents of the IRLP log if it's any help. > > My station # is stn3366. > > Any ideas ? > > Gerry > W6WNG > > > File: /home/irlp/log/messages > ----------------------------------------------------------------- > Tue May 14 10:44:45 PDT 2019 [update:hosts] Gzipped file was > unavailable, downloading hosts.update direct. > Tue May 14 10:44:45 PDT 2019 [update:hosts] ERROR: Hosts file seems > invalid. > Tue May 14 10:44:45 PDT 2019 [update:hosts] Update completed. > Tue May 14 10:44:55 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:44:56 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:45:11 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:45:11 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-9 CODEC chosen is UNCOMP. > Tue May 14 10:45:13 PDT 2019 [update:hosts] Update completed. > Tue May 14 10:45:49 PDT 2019 [failure] timeout connect > Tue May 14 10:45:50 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:46:12 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:46:12 PDT 2019 [connect_to_reflector] Reflector > ref922/Ch-9 CODEC chosen is GSM. > Tue May 14 10:46:28 PDT 2019 [failure] timeout connect > Tue May 14 10:46:28 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:47:26 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:47:26 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 10:47:42 PDT 2019 [failure] timeout connect > Tue May 14 10:47:42 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:48:57 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:48:57 PDT 2019 [connect_to_reflector] Reflector > ref999/Ch-9 CODEC chosen is ADPCM. > Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Timeout is disabled. > Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Node Connected to > base reflector ref999/Ch-9 > Tue May 14 10:49:59 PDT 2019 [end] Node Disconnect from ref9999 > Tue May 14 10:50:14 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:50:14 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 10:50:29 PDT 2019 [failure] timeout connect > Tue May 14 10:50:30 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:12:29 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:12:29 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 11:12:45 PDT 2019 [failure] timeout connect > Tue May 14 11:12:45 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:13:08 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:13:08 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-9 CODEC chosen is UNCOMP. > Tue May 14 11:13:24 PDT 2019 [failure] timeout connect > Tue May 14 11:13:25 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:14:30 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:14:30 PDT 2019 [connect_to_reflector] Reflector > ref960/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 11:14:46 PDT 2019 [failure] timeout connect > Tue May 14 11:14:46 PDT 2019 [irlp_reset] Reset completed. > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From gerf at gerf.com Tue May 14 16:29:39 2019 From: gerf at gerf.com (Gerry Filby) Date: Tue, 14 May 2019 13:29:39 -0700 Subject: [Arm-allstar-irlp] Fwd: Re: Problems connecting to IRLP reflectors In-Reply-To: References: Message-ID: <522664db-43b6-d7aa-cec5-1ab9c363ea8b@gerf.com> Well I've been through it with a fine-toothed comb - I can't see anything wrong. Also I can connect to 89999 and 80016 the experimental news station just fine - see the log below. Times out on 9100, 9200 etc ... Tonight I'll drag out the old IRLP hardware and see if that works. g Tue May 14 13:23:42 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 13:23:42 PDT 2019 [experimental_call] The experimental node is using a hostname: newsline.thelinkbox.net Tue May 14 13:23:42 PDT 2019 [experimental_call] The experimental node IP is determined to be 72.249.77.29 Tue May 14 13:23:42 PDT 2019 [experimental_call] Timeout is disabled. Tue May 14 13:23:42 PDT 2019 [experimental_call] Node Connected to experimental node exp0016, CODEC=ADPCM_FD Tue May 14 13:23:43 PDT 2019 [experimental_call] CODEC at this point is =ADPCM_FD= Tue May 14 13:24:31 PDT 2019 [end] Node Disconnect from exp0016 Tue May 14 13:24:32 PDT 2019 [dropcall] Call dropped. Tue May 14 13:24:49 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 13:24:49 PDT 2019 [connect_to_reflector] Reflector ref920/Ch-0 CODEC chosen is UNCOMP. Tue May 14 13:25:05 PDT 2019 [failure] timeout connect Tue May 14 13:25:05 PDT 2019 [irlp_reset] Reset completed. Pres W wrote on 5/14/19 11:58 AM: > Gerry, > > I understand you feel your ports are in order, but it's worth going > though BOTH Allstar and IRLP ports, paying particular attention to UDP > vs TCP selection. From memory: 2074-2093 UDP ; 15425-15527 TCP and the > usual Allstar ports 4569 UDP; and 5038 and 222 TCP (plus Echolink if > used). Routers do funny things now and then, including letting > previously reserved/locked devices wander. 73 > > Pres > W2PW > > On Tue, May 14, 2019, 2:22 PM "Gerry Filby via ARM-allstar-irlp" > > wrote: > > I don't use IRLP a whole lot, but just noticed that I can't connect to > any of the reflectors - the connection times out. > > I CAN connect to 89999 and the transmit and playback works fine. > > I've double checked the configuration per the how-to document and all > seems fine - including port forwarding at my firewall. > > It used to work and nothing has changed in many months. > > Below is the contents of the IRLP log if it's any help. > > My station # is stn3366. > > Any ideas ? > > Gerry > W6WNG > > > File: /home/irlp/log/messages > ----------------------------------------------------------------- > Tue May 14 10:44:45 PDT 2019 [update:hosts] Gzipped file was > unavailable, downloading hosts.update direct. > Tue May 14 10:44:45 PDT 2019 [update:hosts] ERROR: Hosts file seems > invalid. > Tue May 14 10:44:45 PDT 2019 [update:hosts] Update completed. > Tue May 14 10:44:55 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:44:56 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:45:11 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:45:11 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-9 CODEC chosen is UNCOMP. > Tue May 14 10:45:13 PDT 2019 [update:hosts] Update completed. > Tue May 14 10:45:49 PDT 2019 [failure] timeout connect > Tue May 14 10:45:50 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:46:12 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:46:12 PDT 2019 [connect_to_reflector] Reflector > ref922/Ch-9 CODEC chosen is GSM. > Tue May 14 10:46:28 PDT 2019 [failure] timeout connect > Tue May 14 10:46:28 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:47:26 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:47:26 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 10:47:42 PDT 2019 [failure] timeout connect > Tue May 14 10:47:42 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:48:57 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:48:57 PDT 2019 [connect_to_reflector] Reflector > ref999/Ch-9 CODEC chosen is ADPCM. > Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Timeout is disabled. > Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Node Connected to > base reflector ref999/Ch-9 > Tue May 14 10:49:59 PDT 2019 [end] Node Disconnect from ref9999 > Tue May 14 10:50:14 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:50:14 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 10:50:29 PDT 2019 [failure] timeout connect > Tue May 14 10:50:30 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:12:29 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:12:29 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 11:12:45 PDT 2019 [failure] timeout connect > Tue May 14 11:12:45 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:13:08 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:13:08 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-9 CODEC chosen is UNCOMP. > Tue May 14 11:13:24 PDT 2019 [failure] timeout connect > Tue May 14 11:13:25 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:14:30 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:14:30 PDT 2019 [connect_to_reflector] Reflector > ref960/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 11:14:46 PDT 2019 [failure] timeout connect > Tue May 14 11:14:46 PDT 2019 [irlp_reset] Reset completed. > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From paulkn2r at gmail.com Tue May 14 16:49:33 2019 From: paulkn2r at gmail.com (Paul - KN2R) Date: Tue, 14 May 2019 16:49:33 -0400 Subject: [Arm-allstar-irlp] Fwd: Re: Problems connecting to IRLP reflectors In-Reply-To: <522664db-43b6-d7aa-cec5-1ab9c363ea8b@gerf.com> References: <522664db-43b6-d7aa-cec5-1ab9c363ea8b@gerf.com> Message-ID: <017701d50a96$89a60a30$9cf21e90$@com> Hi Gerry, After connecting and then disconnecting an IRLP node, you MUST wait at LEAST 20 or more seconds, in between, before you dial another IRLP node. The bridging channel driver requires time to fully complete and clear the previous connection! Paul / KN2R -----Original Message----- From: ARM-allstar-irlp [mailto:arm-allstar-irlp-bounces at hamvoip.org] On Behalf Of "Gerry Filby via ARM-allstar-irlp" Sent: Tuesday, May 14, 2019 4:30 PM To: arm-allstar-irlp at hamvoip.org Cc: Gerry Filby Subject: [Arm-allstar-irlp] Fwd: Re: Problems connecting to IRLP reflectors Well I've been through it with a fine-toothed comb - I can't see anything wrong. Also I can connect to 89999 and 80016 the experimental news station just fine - see the log below. Times out on 9100, 9200 etc ... Tonight I'll drag out the old IRLP hardware and see if that works. g Tue May 14 13:23:42 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 13:23:42 PDT 2019 [experimental_call] The experimental node is using a hostname: newsline.thelinkbox.net Tue May 14 13:23:42 PDT 2019 [experimental_call] The experimental node IP is determined to be 72.249.77.29 Tue May 14 13:23:42 PDT 2019 [experimental_call] Timeout is disabled. Tue May 14 13:23:42 PDT 2019 [experimental_call] Node Connected to experimental node exp0016, CODEC=ADPCM_FD Tue May 14 13:23:43 PDT 2019 [experimental_call] CODEC at this point is =ADPCM_FD= Tue May 14 13:24:31 PDT 2019 [end] Node Disconnect from exp0016 Tue May 14 13:24:32 PDT 2019 [dropcall] Call dropped. Tue May 14 13:24:49 PDT 2019 [irlp_fullreset] Full Reset completed. Tue May 14 13:24:49 PDT 2019 [connect_to_reflector] Reflector ref920/Ch-0 CODEC chosen is UNCOMP. Tue May 14 13:25:05 PDT 2019 [failure] timeout connect Tue May 14 13:25:05 PDT 2019 [irlp_reset] Reset completed. Pres W wrote on 5/14/19 11:58 AM: > Gerry, > > I understand you feel your ports are in order, but it's worth going > though BOTH Allstar and IRLP ports, paying particular attention to UDP > vs TCP selection. From memory: 2074-2093 UDP ; 15425-15527 TCP and the > usual Allstar ports 4569 UDP; and 5038 and 222 TCP (plus Echolink if > used). Routers do funny things now and then, including letting > previously reserved/locked devices wander. 73 > > Pres > W2PW > > On Tue, May 14, 2019, 2:22 PM "Gerry Filby via ARM-allstar-irlp" > > wrote: > > I don't use IRLP a whole lot, but just noticed that I can't connect to > any of the reflectors - the connection times out. > > I CAN connect to 89999 and the transmit and playback works fine. > > I've double checked the configuration per the how-to document and all > seems fine - including port forwarding at my firewall. > > It used to work and nothing has changed in many months. > > Below is the contents of the IRLP log if it's any help. > > My station # is stn3366. > > Any ideas ? > > Gerry > W6WNG > > > File: /home/irlp/log/messages > ----------------------------------------------------------------- > Tue May 14 10:44:45 PDT 2019 [update:hosts] Gzipped file was > unavailable, downloading hosts.update direct. > Tue May 14 10:44:45 PDT 2019 [update:hosts] ERROR: Hosts file seems > invalid. > Tue May 14 10:44:45 PDT 2019 [update:hosts] Update completed. > Tue May 14 10:44:55 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:44:56 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:45:11 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:45:11 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-9 CODEC chosen is UNCOMP. > Tue May 14 10:45:13 PDT 2019 [update:hosts] Update completed. > Tue May 14 10:45:49 PDT 2019 [failure] timeout connect > Tue May 14 10:45:50 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:46:12 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:46:12 PDT 2019 [connect_to_reflector] Reflector > ref922/Ch-9 CODEC chosen is GSM. > Tue May 14 10:46:28 PDT 2019 [failure] timeout connect > Tue May 14 10:46:28 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:47:26 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:47:26 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 10:47:42 PDT 2019 [failure] timeout connect > Tue May 14 10:47:42 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 10:48:57 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:48:57 PDT 2019 [connect_to_reflector] Reflector > ref999/Ch-9 CODEC chosen is ADPCM. > Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Timeout is disabled. > Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Node Connected to > base reflector ref999/Ch-9 > Tue May 14 10:49:59 PDT 2019 [end] Node Disconnect from ref9999 > Tue May 14 10:50:14 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 10:50:14 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 10:50:29 PDT 2019 [failure] timeout connect > Tue May 14 10:50:30 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:12:29 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:12:29 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 11:12:45 PDT 2019 [failure] timeout connect > Tue May 14 11:12:45 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:13:08 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:13:08 PDT 2019 [connect_to_reflector] Reflector > ref910/Ch-9 CODEC chosen is UNCOMP. > Tue May 14 11:13:24 PDT 2019 [failure] timeout connect > Tue May 14 11:13:25 PDT 2019 [irlp_reset] Reset completed. > Tue May 14 11:14:30 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 11:14:30 PDT 2019 [connect_to_reflector] Reflector > ref960/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 11:14:46 PDT 2019 [failure] timeout connect > Tue May 14 11:14:46 PDT 2019 [irlp_reset] Reset completed. > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > _______________________________________________ ARM-allstar-irlp mailing list ARM-allstar-irlp at hamvoip.org http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp From gerf at gerf.com Tue May 14 16:51:57 2019 From: gerf at gerf.com (Gerry Filby) Date: Tue, 14 May 2019 13:51:57 -0700 Subject: [Arm-allstar-irlp] Fwd: Re: Problems connecting to IRLP reflectors In-Reply-To: <017701d50a96$89a60a30$9cf21e90$@com> References: <522664db-43b6-d7aa-cec5-1ab9c363ea8b@gerf.com> <017701d50a96$89a60a30$9cf21e90$@com> Message-ID: <2c262ff2-ff54-f053-7c54-0c5dfa2c583f@gerf.com> Thx ! Same behavior ... g W6WNG Paul - KN2R wrote on 5/14/19 1:49 PM: > Hi Gerry, > > After connecting and then disconnecting an IRLP node, you MUST wait at LEAST > 20 or more seconds, in between, before you dial another IRLP node. The > bridging channel driver requires time to fully complete and clear the > previous connection! > > Paul / KN2R > > > -----Original Message----- > From: ARM-allstar-irlp [mailto:arm-allstar-irlp-bounces at hamvoip.org] On > Behalf Of "Gerry Filby via ARM-allstar-irlp" > Sent: Tuesday, May 14, 2019 4:30 PM > To: arm-allstar-irlp at hamvoip.org > Cc: Gerry Filby > Subject: [Arm-allstar-irlp] Fwd: Re: Problems connecting to IRLP reflectors > > > Well I've been through it with a fine-toothed comb - I can't see > anything wrong. > > Also I can connect to 89999 and 80016 the experimental news station just > fine - see the log below. > > Times out on 9100, 9200 etc ... > > Tonight I'll drag out the old IRLP hardware and see if that works. > > g > > Tue May 14 13:23:42 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 13:23:42 PDT 2019 [experimental_call] The experimental node > is using a hostname: newsline.thelinkbox.net > Tue May 14 13:23:42 PDT 2019 [experimental_call] The experimental node > IP is determined to be 72.249.77.29 > Tue May 14 13:23:42 PDT 2019 [experimental_call] Timeout is disabled. > Tue May 14 13:23:42 PDT 2019 [experimental_call] Node Connected to > experimental node exp0016, CODEC=ADPCM_FD > Tue May 14 13:23:43 PDT 2019 [experimental_call] CODEC at this point is > =ADPCM_FD= > Tue May 14 13:24:31 PDT 2019 [end] Node Disconnect from exp0016 > Tue May 14 13:24:32 PDT 2019 [dropcall] Call dropped. > Tue May 14 13:24:49 PDT 2019 [irlp_fullreset] Full Reset completed. > Tue May 14 13:24:49 PDT 2019 [connect_to_reflector] Reflector > ref920/Ch-0 CODEC chosen is UNCOMP. > Tue May 14 13:25:05 PDT 2019 [failure] timeout connect > Tue May 14 13:25:05 PDT 2019 [irlp_reset] Reset completed. > > Pres W wrote on 5/14/19 11:58 AM: >> Gerry, >> >> I understand you feel your ports are in order, but it's worth going >> though BOTH Allstar and IRLP ports, paying particular attention to UDP >> vs TCP selection. From memory: 2074-2093 UDP ; 15425-15527 TCP and the >> usual Allstar ports 4569 UDP; and 5038 and 222 TCP (plus Echolink if >> used). Routers do funny things now and then, including letting >> previously reserved/locked devices wander. 73 >> >> Pres >> W2PW >> >> On Tue, May 14, 2019, 2:22 PM "Gerry Filby via ARM-allstar-irlp" >> > > wrote: >> >> I don't use IRLP a whole lot, but just noticed that I can't connect to >> any of the reflectors - the connection times out. >> >> I CAN connect to 89999 and the transmit and playback works fine. >> >> I've double checked the configuration per the how-to document and all >> seems fine - including port forwarding at my firewall. >> >> It used to work and nothing has changed in many months. >> >> Below is the contents of the IRLP log if it's any help. >> >> My station # is stn3366. >> >> Any ideas ? >> >> Gerry >> W6WNG >> >> >> File: /home/irlp/log/messages >> ----------------------------------------------------------------- >> Tue May 14 10:44:45 PDT 2019 [update:hosts] Gzipped file was >> unavailable, downloading hosts.update direct. >> Tue May 14 10:44:45 PDT 2019 [update:hosts] ERROR: Hosts file seems >> invalid. >> Tue May 14 10:44:45 PDT 2019 [update:hosts] Update completed. >> Tue May 14 10:44:55 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:44:56 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:45:11 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:45:11 PDT 2019 [connect_to_reflector] Reflector >> ref910/Ch-9 CODEC chosen is UNCOMP. >> Tue May 14 10:45:13 PDT 2019 [update:hosts] Update completed. >> Tue May 14 10:45:49 PDT 2019 [failure] timeout connect >> Tue May 14 10:45:50 PDT 2019 [irlp_reset] Reset completed. >> Tue May 14 10:46:12 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:46:12 PDT 2019 [connect_to_reflector] Reflector >> ref922/Ch-9 CODEC chosen is GSM. >> Tue May 14 10:46:28 PDT 2019 [failure] timeout connect >> Tue May 14 10:46:28 PDT 2019 [irlp_reset] Reset completed. >> Tue May 14 10:47:26 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:47:26 PDT 2019 [connect_to_reflector] Reflector >> ref910/Ch-0 CODEC chosen is UNCOMP. >> Tue May 14 10:47:42 PDT 2019 [failure] timeout connect >> Tue May 14 10:47:42 PDT 2019 [irlp_reset] Reset completed. >> Tue May 14 10:48:57 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:48:57 PDT 2019 [connect_to_reflector] Reflector >> ref999/Ch-9 CODEC chosen is ADPCM. >> Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Timeout is > disabled. >> Tue May 14 10:48:58 PDT 2019 [connect_to_reflector] Node Connected to >> base reflector ref999/Ch-9 >> Tue May 14 10:49:59 PDT 2019 [end] Node Disconnect from ref9999 >> Tue May 14 10:50:14 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 10:50:14 PDT 2019 [connect_to_reflector] Reflector >> ref910/Ch-0 CODEC chosen is UNCOMP. >> Tue May 14 10:50:29 PDT 2019 [failure] timeout connect >> Tue May 14 10:50:30 PDT 2019 [irlp_reset] Reset completed. >> Tue May 14 11:12:29 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 11:12:29 PDT 2019 [connect_to_reflector] Reflector >> ref910/Ch-0 CODEC chosen is UNCOMP. >> Tue May 14 11:12:45 PDT 2019 [failure] timeout connect >> Tue May 14 11:12:45 PDT 2019 [irlp_reset] Reset completed. >> Tue May 14 11:13:08 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 11:13:08 PDT 2019 [connect_to_reflector] Reflector >> ref910/Ch-9 CODEC chosen is UNCOMP. >> Tue May 14 11:13:24 PDT 2019 [failure] timeout connect >> Tue May 14 11:13:25 PDT 2019 [irlp_reset] Reset completed. >> Tue May 14 11:14:30 PDT 2019 [irlp_fullreset] Full Reset completed. >> Tue May 14 11:14:30 PDT 2019 [connect_to_reflector] Reflector >> ref960/Ch-0 CODEC chosen is UNCOMP. >> Tue May 14 11:14:46 PDT 2019 [failure] timeout connect >> Tue May 14 11:14:46 PDT 2019 [irlp_reset] Reset completed. >> _______________________________________________ >> ARM-allstar-irlp mailing list >> ARM-allstar-irlp at hamvoip.org >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp >> > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From wa7spy at att.net Thu May 23 20:01:37 2019 From: wa7spy at att.net (Glenn Maclean) Date: Thu, 23 May 2019 17:01:37 -0700 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded Message-ID: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Hi, I am very new to Allstar and just got my node up and running. I was able to get Echolink to work without issue and Allstar node seems to be working. When I run the IRLP troubleshooting script as user repeater I am getting two errors. 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound 2. Your node?s hostname does not resolve I am using an ATT router with the raspberry pi IP address in the DMZ. Using DHCP I had not issues what so ever with the original IRLP raspberry pi with the IRLP board using the same router with the raspberry pi in the DMZ using DHCP. There is no issue with the router, I have triple checked the environment file and the call and IRLP node numbers are there in lower case! The hosts file is also configured correctly. Here is my hosts file: # # /etc/hosts: static lookup table for host names # > 127.0.0.1 stn388 #: : 1 #End of file Any help would be much appreciated! Thank you, Glenn Maclean WA7SPY From wa7spy at att.net Fri May 24 00:14:04 2019 From: wa7spy at att.net (Glenn Maclean) Date: Thu, 23 May 2019 21:14:04 -0700 Subject: [Arm-allstar-irlp] Having two issues getting IRLP to work Message-ID: <63BEEA70-42C7-42FE-8A2E-71777ED96467@att.net> Hi, I am very new to Allstar and just got my node up and running. I was able to get Echolink to work without issue and Allstar node seems to be working. When I run the IRLP troubleshooting script as user repeater I am getting two errors. 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound 2. Your node?s hostname does not resolve I am using an ATT router with the raspberry pi IP address in the DMZ. Using DHCP I had not issues what so ever with the original IRLP raspberry pi with the IRLP board using the same router with the raspberry pi in the DMZ using DHCP. There is no issue with the router, I have triple checked the environment file and the call and IRLP node numbers are there in lower case! The hosts file is also configured correctly. Here is my hosts file: # # /etc/hosts: static lookup table for host names # > 127.0.0.1 stn388 #: : 1 #End of file Any help would be much appreciated! Thank you, Glenn Maclean WA7SPY From ka5tkn at suddenlink.net Fri May 24 08:41:57 2019 From: ka5tkn at suddenlink.net (ka5tkn@suddenlink.Net) Date: Fri, 24 May 2019 07:41:57 -0500 Subject: [Arm-allstar-irlp] Not in data base Message-ID: <20190524124200.WYTJ27691.dalofep04.suddenlink.net@[10.241.135.211]> Morning Doug.? Node 47954 not in database. Did a reboot still no joy. My other nodes are fineGlenn K5CODSent via the Samsung Galaxy Note5, an AT&T 4G LTE smartphone From kc5czx at gmail.com Fri May 24 08:50:05 2019 From: kc5czx at gmail.com (Darrell Wilkinson) Date: Fri, 24 May 2019 07:50:05 -0500 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: <58770CE5-768E-4F43-846F-425524FDB270@att.net> References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: Check your IRLP node # all node# are 4 digits I only see 3 On Thu, May 23, 2019, 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < arm-allstar-irlp at hamvoip.org> wrote: > Hi, > I am very new to Allstar and just got my node up and running. I was able > to get Echolink to work without issue and Allstar node seems to be working. > When I run the IRLP troubleshooting script as user repeater I am getting > two errors. > 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound > > 2. Your node?s hostname does not resolve > > I am using an ATT router with the raspberry pi IP address in the DMZ. > Using DHCP I had not issues what so ever with the original IRLP raspberry > pi with the IRLP board using the same router with the raspberry pi in the > DMZ using DHCP. There is no issue with the router, I have triple checked > the environment file and the call and IRLP node numbers are there in lower > case! The hosts file is also configured correctly. Here is my hosts file: > > # > # /etc/hosts: static lookup table for host names > # > > 127.0.0.1 localhost > 127.0.0.1 localhost.localdomain localhost > 127.0.0.1 config.allstarlinl.org < > http://config.allstarlinl.org/> > 127.0.0.1 stn388 > #: : 1 > > #End of file > > Any help would be much appreciated! > > Thank you, > Glenn Maclean WA7SPY > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From wa7spy at att.net Fri May 24 15:26:14 2019 From: wa7spy at att.net (Glenn Maclean) Date: Fri, 24 May 2019 12:26:14 -0700 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: I have tried with both 3 digits and 4 digits in both environment and hosts files .Same issue either way. Old node with raspberry pi files have 3 numbers for the node and works just fine, The actual node number is 3880 > On May 24, 2019, at 5:50 AM, Darrell Wilkinson via ARM-allstar-irlp wrote: > > Check your IRLP node # all node# are 4 digits I only see 3 > > On Thu, May 23, 2019, 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < > arm-allstar-irlp at hamvoip.org > wrote: > >> Hi, >> I am very new to Allstar and just got my node up and running. I was able >> to get Echolink to work without issue and Allstar node seems to be working. >> When I run the IRLP troubleshooting script as user repeater I am getting >> two errors. >> 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound >> >> 2. Your node?s hostname does not resolve >> >> I am using an ATT router with the raspberry pi IP address in the DMZ. >> Using DHCP I had not issues what so ever with the original IRLP raspberry >> pi with the IRLP board using the same router with the raspberry pi in the >> DMZ using DHCP. There is no issue with the router, I have triple checked >> the environment file and the call and IRLP node numbers are there in lower >> case! The hosts file is also configured correctly. Here is my hosts file: >> >> # >> # /etc/hosts: static lookup table for host names >> # >> >> > 127.0.0.1 localhost >> 127.0.0.1 localhost.localdomain localhost >> 127.0.0.1 config.allstarlinl.org < >> http://config.allstarlinl.org/ > >> 127.0.0.1 stn388 >> #: : 1 >> >> #End of file >> >> Any help would be much appreciated! >> >> Thank you, >> Glenn Maclean WA7SPY >> _______________________________________________ >> ARM-allstar-irlp mailing list >> ARM-allstar-irlp at hamvoip.org >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp >> > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp From decloyd at gci.net Fri May 24 16:37:22 2019 From: decloyd at gci.net (decloyd at gci.net) Date: Fri, 24 May 2019 16:37:22 -0400 (EDT) Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: <1156965049.19004648.1558730242649.JavaMail.zimbra@gci.net> Understand the IRLP system has three and four digit .pgp numbers. The three digit numbers are the old legacy numbers and are still used. Look in the IRLP node in /home/irlp/.pgp open that file and at the end will be the correct stn number will be either stn388 or some other number, stn3880 ?? That is the number that should be in /home/irlp/custom/environment Also the call sign should match with what's on record with IRLP status system. The error message about hostname not resolving. The software want's the name in that file use the format "stnxxxx" in this case stn388, or maybe stn3880 ???? Once you make these changes reboot and all should be good. Dave, KL7M ----- Original Message ----- From: "Glenn Maclean via ARM-allstar-irlp" irlp at hamvoip.org> To: arm-allstar-irlp at hamvoip.org Cc: "Glenn Maclean" att.net> Sent: Friday, May 24, 2019 11:26:14 AM Subject: Re: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded I have tried with both 3 digits and 4 digits in both environment and hosts files .Same issue either way. Old node with raspberry pi files have 3 numbers for the node and works just fine, The actual node number is 3880 > On May 24, 2019, at 5:50 AM, Darrell Wilkinson via ARM-allstar-irlp irlp at hamvoip.org> wrote: > > Check your IRLP node # all node# are 4 digits I only see 3 > > On Thu, May 23, 2019, 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < > arm-allstar-irlp at hamvoip.org > wrote: > >> Hi, >> I am very new to Allstar and just got my node up and running. I was able >> to get Echolink to work without issue and Allstar node seems to be working. >> When I run the IRLP troubleshooting script as user repeater I am getting >> two errors. >> 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound >> >> 2. Your node?s hostname does not resolve >> >> I am using an ATT router with the raspberry pi IP address in the DMZ. >> Using DHCP I had not issues what so ever with the original IRLP raspberry >> pi with the IRLP board using the same router with the raspberry pi in the >> DMZ using DHCP. There is no issue with the router, I have triple checked >> the environment file and the call and IRLP node numbers are there in lower >> case! The hosts file is also configured correctly. Here is my hosts file: >> >> # >> # /etc/hosts: static lookup table for host names >> # >> >> > 127.0.0.1 localhost >> 127.0.0.1 localhost.localdomain localhost >> 127.0.0.1 config.allstarlinl.org < >> http://config.allstarlinl.org/ > >> 127.0.0.1 stn388 >> #: : 1 >> >> #End of file >> >> Any help would be much appreciated! >> >> Thank you, >> Glenn Maclean WA7SPY >> _______________________________________________ >> ARM-allstar-irlp mailing list >> ARM-allstar-irlp at hamvoip.org >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp >> > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp _______________________________________________ ARM-allstar-irlp mailing list ARM-allstar-irlp at hamvoip.org http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp From k8lrc.lc at gmail.com Fri May 24 17:49:00 2019 From: k8lrc.lc at gmail.com (Logan Crook) Date: Fri, 24 May 2019 17:49:00 -0400 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: Glenn, Your IRLP node is 3860 not 3880. Logan K8LRC On Fri, May 24, 2019, 3:26 PM "Glenn Maclean via ARM-allstar-irlp" < arm-allstar-irlp at hamvoip.org wrote: > I have tried with both 3 digits and 4 digits in both environment and hosts > files .Same issue either way. Old node with raspberry pi files have 3 > numbers for the node and works just fine, The actual node number is 3880 > > > On May 24, 2019, at 5:50 AM, Darrell Wilkinson via ARM-allstar-irlp < > arm-allstar-irlp at hamvoip.org> wrote: > > > > Check your IRLP node # all node# are 4 digits I only see 3 > > > > On Thu, May 23, 2019, 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < > > arm-allstar-irlp at hamvoip.org > > wrote: > > > >> Hi, > >> I am very new to Allstar and just got my node up and running. I was able > >> to get Echolink to work without issue and Allstar node seems to be > working. > >> When I run the IRLP troubleshooting script as user repeater I am getting > >> two errors. > >> 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound > >> > >> 2. Your node?s hostname does not resolve > >> > >> I am using an ATT router with the raspberry pi IP address in the DMZ. > >> Using DHCP I had not issues what so ever with the original IRLP > raspberry > >> pi with the IRLP board using the same router with the raspberry pi in > the > >> DMZ using DHCP. There is no issue with the router, I have triple checked > >> the environment file and the call and IRLP node numbers are there in > lower > >> case! The hosts file is also configured correctly. Here is my hosts > file: > >> > >> # > >> # /etc/hosts: static lookup table for host names > >> # http://hostname.domain.org/> http://hostname.domain.org/>>> > >> >> 127.0.0.1 localhost > >> 127.0.0.1 localhost.localdomain localhost > >> 127.0.0.1 config.allstarlinl.org < > http://config.allstarlinl.org/> < > >> http://config.allstarlinl.org/ > > >> 127.0.0.1 stn388 > >> #: : 1 > >> > >> #End of file > >> > >> Any help would be much appreciated! > >> > >> Thank you, > >> Glenn Maclean WA7SPY > >> _______________________________________________ > >> ARM-allstar-irlp mailing list > >> ARM-allstar-irlp at hamvoip.org > >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp < > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp> > >> > > _______________________________________________ > > ARM-allstar-irlp mailing list > > ARM-allstar-irlp at hamvoip.org > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp < > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp> > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From k8lrc.lc at gmail.com Fri May 24 18:08:41 2019 From: k8lrc.lc at gmail.com (Logan Crook) Date: Fri, 24 May 2019 18:08:41 -0400 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: Disregard the last post I looked at 3880 and somehow you are the node owner of it. Trying to help 73 Logan K8LRC On Fri, May 24, 2019, 5:49 PM Logan Crook Glenn, > > Your IRLP node is 3860 not 3880. > > Logan > > K8LRC > > > On Fri, May 24, 2019, 3:26 PM "Glenn Maclean via ARM-allstar-irlp" < > arm-allstar-irlp at hamvoip.org wrote: > >> I have tried with both 3 digits and 4 digits in both environment and >> hosts files .Same issue either way. Old node with raspberry pi files have 3 >> numbers for the node and works just fine, The actual node number is 3880 >> >> > On May 24, 2019, at 5:50 AM, Darrell Wilkinson via ARM-allstar-irlp < >> arm-allstar-irlp at hamvoip.org> wrote: >> > >> > Check your IRLP node # all node# are 4 digits I only see 3 >> > >> > On Thu, May 23, 2019, 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < >> > arm-allstar-irlp at hamvoip.org > >> wrote: >> > >> >> Hi, >> >> I am very new to Allstar and just got my node up and running. I was >> able >> >> to get Echolink to work without issue and Allstar node seems to be >> working. >> >> When I run the IRLP troubleshooting script as user repeater I am >> getting >> >> two errors. >> >> 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound >> >> >> >> 2. Your node?s hostname does not resolve >> >> >> >> I am using an ATT router with the raspberry pi IP address in the DMZ. >> >> Using DHCP I had not issues what so ever with the original IRLP >> raspberry >> >> pi with the IRLP board using the same router with the raspberry pi in >> the >> >> DMZ using DHCP. There is no issue with the router, I have triple >> checked >> >> the environment file and the call and IRLP node numbers are there in >> lower >> >> case! The hosts file is also configured correctly. Here is my hosts >> file: >> >> >> >> # >> >> # /etc/hosts: static lookup table for host names >> >> # > http://hostname.domain.org/> > http://hostname.domain.org/>>> >> >> > >> 127.0.0.1 localhost >> >> 127.0.0.1 localhost.localdomain localhost >> >> 127.0.0.1 config.allstarlinl.org < >> http://config.allstarlinl.org/> < >> >> http://config.allstarlinl.org/ > >> >> 127.0.0.1 stn388 >> >> #: : 1 >> >> >> >> #End of file >> >> >> >> Any help would be much appreciated! >> >> >> >> Thank you, >> >> Glenn Maclean WA7SPY >> >> _______________________________________________ >> >> ARM-allstar-irlp mailing list >> >> ARM-allstar-irlp at hamvoip.org >> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp < >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp> >> >> >> > _______________________________________________ >> > ARM-allstar-irlp mailing list >> > ARM-allstar-irlp at hamvoip.org >> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp < >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp> >> _______________________________________________ >> ARM-allstar-irlp mailing list >> ARM-allstar-irlp at hamvoip.org >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp >> > From tpwaterman at gmail.com Sat May 25 12:26:21 2019 From: tpwaterman at gmail.com (Pres W) Date: Sat, 25 May 2019 12:26:21 -0400 Subject: [Arm-allstar-irlp] MDC-1200 request Message-ID: Hello. Since Allstar (and HAMVOIP) suppport MDC-1200 decoding, would it be possible to incorporate a valid MDC-1200 burst as a third RX qualifier? Meaning, without MDC-1200 the system does not pass the transmission through to the Allstar network? Ideally DTMF would still work without MDC, so as to be able to turn the feature on and off. Sadly, my system is attracting a lot of bootleggers and I'm considering taking my system off East Coast Reflector. Or even worse, going all digital. Thank you -Pres W2PW From k4fxc at pcrn.net Sat May 25 15:29:35 2019 From: k4fxc at pcrn.net (David McGough) Date: Sat, 25 May 2019 15:29:35 -0400 (EDT) Subject: [Arm-allstar-irlp] MDC-1200 request In-Reply-To: Message-ID: Hi Pres, I've been pondering ways to utilize MDC-1200 coding for a while. A big concern is that most ham gear doesn't support it, so you're limited to commercial radios. Now that the MDC-1200 patents have expired, perhaps ham vendors will show more interest. Another thought is to try DPL coding rather than CTCSS, which might present a little more of a road block to the bootleggers. 73, David K4FXC On Sat, 25 May 2019, "Pres W via ARM-allstar-irlp" wrote: > Hello. Since Allstar (and HAMVOIP) suppport MDC-1200 decoding, would > it be possible to incorporate a valid MDC-1200 burst as a third RX > qualifier? Meaning, without MDC-1200 the system does not pass the > transmission through to the Allstar network? Ideally DTMF would still > work without MDC, so as to be able to turn the feature on and off. > > Sadly, my system is attracting a lot of bootleggers and I'm > considering taking my system off East Coast Reflector. Or even worse, > going all digital. > > Thank you > > -Pres W2PW > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From wa7spy at att.net Sat May 25 18:18:38 2019 From: wa7spy at att.net (Glenn Maclean) Date: Sat, 25 May 2019 15:18:38 -0700 Subject: [Arm-allstar-irlp] Cant get IRLP to work Message-ID: <245BA747-6E4B-45FE-9219-F3867C76AA55@att.net> ************************ * Port Forwarding Test * ************************ Performing INBOUND Port Forwarding Test Starting listening services on UDP ports .... done. Detecting Incoming IP = 70.231.88.220 Testing TCP and UDP ports .. done. ----------------------------------------------------------------------------- TEST No. 2a REPORT - TCP PASS - TCP port 15425 is forwarded correctly. Performing OUTBOUND Port Test Testing OUTBOUND TCP and UDP ports ........................... done. ------------------------------------------------------------------------------ TEST No. 3 REPORT - ERROR - The following ports do NOT work OUTBOUND: 873 8873 10000 15425 15426 15427 ------------------------------------------------------------------------------ Press ENTER to continue : ***************************** * Host Name Resolution Test * ***************************** Your node's hostname is set to "W6YDD" Testing if your hostname resolves... done. ------------------------------------------------------------------------------ TEST No. 4 REPORT - ERROR - Your node's hostname DOES NOT resolve! Please consult the troubleshooting information on how to fix this problem. ------------------------------------------------------------------------------ Press ENTER to continue : * PGP Key Test * **************** Updating pgp keyring... done. ------------------------------------------------------------------------------ TEST No. 5 REPORT - ERROR - Your public PGP key does not exist in the keyring. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TEST No. 6 REPORT - PASS - Your secret keyring only contains one secret PGP key. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TEST No. 7 REPORT - ERROR - Your PGP key does NOT match your stationid in the environment file. Please check the troubleshooting documents on how to solve this problem. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TEST No. 8 REPORT - PASS - Test is no longer required. ------------------------------------------------------------------------------ Press ENTER to continue : I am still continuing to have issues getting IRLp to work. My node number is 3880 under the call of W6YDD my personal call is WA7SPY. My environment file looks correct lower case letters for the node call sign w6ydd and stn3880. Here is a copy of my hosts file: # # /etc/hosts: static lookup table for hosts names # # 127.0.0.1 localhost 127.0.0.1 localhost.localdomain localhost 127.0.0.1 config.allstarlink.org 127.0.0.1. stn3880 localhost.localdomain localhost #::1 localhost.localdomain localhost # End of file I would appreciate help! The IRLP Node status page shows Node 3880 under W6YDD being idle. Thank you, Glenn Maclean WA7SPY From wa7spy at att.net Sat May 25 18:46:47 2019 From: wa7spy at att.net (Glenn Maclean) Date: Sat, 25 May 2019 15:46:47 -0700 Subject: [Arm-allstar-irlp] More on not able to get IRLP to work Message-ID: <28B51D72-1C50-49CA-BDFC-DCB0B70C3A65@att.net> I forgot to mention in my previous post. I am using a wired ethernet connection to an ATT Uverse router. I have the IP address of the raspberry pi in the DMZplus of the router meaning all ports are open. I have no issues with the raspberry pi using the IRLp software and IRLp board so I know the router is not blocking any ports, The troubleshooting script passes all tests with the old IRLP raspberry pi and IRLp board. The PGP key checks out. I have noticed if I wait a few hours the PGP test passes. That leaves me with the two issues of: 1. The Node?s name does not resolve 2. The following ports are not forwarded properly outbound 873, 8873, 10000, 15425,15426,15427 I hope someone on this list can help me get my IRLp node working with Allstar! Thank you, Glenn Maclean WA7SPY From decloyd at gci.net Sat May 25 21:23:28 2019 From: decloyd at gci.net (decloyd at gci.net) Date: Sat, 25 May 2019 21:23:28 -0400 (EDT) Subject: [Arm-allstar-irlp] Cant get IRLP to work In-Reply-To: <245BA747-6E4B-45FE-9219-F3867C76AA55@att.net> References: <245BA747-6E4B-45FE-9219-F3867C76AA55@att.net> Message-ID: <1273321698.22649626.1558833808031.JavaMail.zimbra@gci.net> Sir, To test if the public key is good for any IRLP node number as repeater: type pgp -kv stn3880 or any node number you're interested in knowing if it's still good... W6YDD stn3880 is not good for some reason at this time. The public key for W6YDD stn3367 is good. If this node number (stn3880) is the one you're trying to use, that's your problem. You'll need to sort things out with the IRLP people. Dave, KL7M ----- Original Message ----- From: "Glenn Maclean via ARM-allstar-irlp" To: "Glenn Maclean via ARM-allstar-irlp" Cc: "Glenn Maclean" Sent: Saturday, May 25, 2019 2:18:38 PM Subject: [Arm-allstar-irlp] Cant get IRLP to work ************************ * Port Forwarding Test * ************************ Performing INBOUND Port Forwarding Test Starting listening services on UDP ports .... done. Detecting Incoming IP = 70.231.88.220 Testing TCP and UDP ports .. done. ----------------------------------------------------------------------------- TEST No. 2a REPORT - TCP PASS - TCP port 15425 is forwarded correctly. Performing OUTBOUND Port Test Testing OUTBOUND TCP and UDP ports ........................... done. ------------------------------------------------------------------------------ TEST No. 3 REPORT - ERROR - The following ports do NOT work OUTBOUND: 873 8873 10000 15425 15426 15427 ------------------------------------------------------------------------------ Press ENTER to continue : ***************************** * Host Name Resolution Test * ***************************** Your node's hostname is set to "W6YDD" Testing if your hostname resolves... done. ------------------------------------------------------------------------------ TEST No. 4 REPORT - ERROR - Your node's hostname DOES NOT resolve! Please consult the troubleshooting information on how to fix this problem. ------------------------------------------------------------------------------ Press ENTER to continue : * PGP Key Test * **************** Updating pgp keyring... done. ------------------------------------------------------------------------------ TEST No. 5 REPORT - ERROR - Your public PGP key does not exist in the keyring. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TEST No. 6 REPORT - PASS - Your secret keyring only contains one secret PGP key. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TEST No. 7 REPORT - ERROR - Your PGP key does NOT match your stationid in the environment file. Please check the troubleshooting documents on how to solve this problem. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ TEST No. 8 REPORT - PASS - Test is no longer required. ------------------------------------------------------------------------------ Press ENTER to continue : I am still continuing to have issues getting IRLp to work. My node number is 3880 under the call of W6YDD my personal call is WA7SPY. My environment file looks correct lower case letters for the node call sign w6ydd and stn3880. Here is a copy of my hosts file: # # /etc/hosts: static lookup table for hosts names # # 127.0.0.1 localhost 127.0.0.1 localhost.localdomain localhost 127.0.0.1 config.allstarlink.org 127.0.0.1. stn3880 localhost.localdomain localhost #::1 localhost.localdomain localhost # End of file I would appreciate help! The IRLP Node status page shows Node 3880 under W6YDD being idle. Thank you, Glenn Maclean WA7SPY _______________________________________________ ARM-allstar-irlp mailing list ARM-allstar-irlp at hamvoip.org http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp From tpwaterman at gmail.com Sat May 25 23:21:07 2019 From: tpwaterman at gmail.com (Pres W) Date: Sat, 25 May 2019 23:21:07 -0400 Subject: [Arm-allstar-irlp] MDC-1200 request In-Reply-To: References: Message-ID: I understand. It's not a great solution because of the limited availability, but it's quite a bit more secure than DPL has become the last few years, and once you accept the "bummer" that making the system limited-access, it opens up some interesing aspects: Making it a qualifier means the repeater would not broadcast the user's code (since the path wasn't opened until the MDC itself) Allstar users wouldn't hear it for the same reason Also, the jammer would have to be able to hear a valid user on the input to decode/copy the valid code, which could be changed if it becomes compromised I know that decoding the MDC can trigger a macro or COP command. Is there a COP command that would toggle a connection from "monitor only" to "transceive" quickly? That would suffice. However, cop 2 and cop 3 (System enable and disable) would not work because both ends of the link would be cut off and thus nobody local could hear stations to contact. Cop 36 and 37 (Foreign Link Local Output Path Enable/Disable) seem intriguing but did not do anything when I ran "rpt cmd 40980 cop 37" at the CLI. -Pres On Sat, May 25, 2019, 3:29 PM David McGough wrote: > > Hi Pres, > > I've been pondering ways to utilize MDC-1200 coding for a while. A big > concern is that most ham gear doesn't support it, so you're limited to > commercial radios. Now that the MDC-1200 patents have expired, perhaps ham > vendors will show more interest. > > Another thought is to try DPL coding rather than CTCSS, which might > present a little more of a road block to the bootleggers. > > > 73, David K4FXC > > > > On Sat, 25 May 2019, "Pres W via ARM-allstar-irlp" wrote: > > > Hello. Since Allstar (and HAMVOIP) suppport MDC-1200 decoding, would > > it be possible to incorporate a valid MDC-1200 burst as a third RX > > qualifier? Meaning, without MDC-1200 the system does not pass the > > transmission through to the Allstar network? Ideally DTMF would still > > work without MDC, so as to be able to turn the feature on and off. > > > > Sadly, my system is attracting a lot of bootleggers and I'm > > considering taking my system off East Coast Reflector. Or even worse, > > going all digital. > > > > Thank you > > > > -Pres W2PW > > _______________________________________________ > > ARM-allstar-irlp mailing list > > ARM-allstar-irlp at hamvoip.org > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > > > > From kc5czx at gmail.com Sun May 26 09:06:26 2019 From: kc5czx at gmail.com (Darrell Wilkinson) Date: Sun, 26 May 2019 08:06:26 -0500 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: <58770CE5-768E-4F43-846F-425524FDB270@att.net> References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: Just for the asking which allstar .img are you using. The .img you download from the allstar website is a raspbian stretch linux , the .img you download from hamvoip is arch linux. The IRLP support is made for arch. Why I ask this is you said you logged in as repeater which is what you would be using if you where using the raspbian stretch linux. I would download a new .img from hamvoip follow the howto to install IRLP and I bet you could get it to work. On the other side of that coin I have tried building a bridge out of the raspbian stretch .img myself but so far no luck getting it to work right On Thu, May 23, 2019 at 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < arm-allstar-irlp at hamvoip.org> wrote: > Hi, > I am very new to Allstar and just got my node up and running. I was able > to get Echolink to work without issue and Allstar node seems to be working. > When I run the IRLP troubleshooting script as user repeater I am getting > two errors. > 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound > > 2. Your node?s hostname does not resolve > > I am using an ATT router with the raspberry pi IP address in the DMZ. > Using DHCP I had not issues what so ever with the original IRLP raspberry > pi with the IRLP board using the same router with the raspberry pi in the > DMZ using DHCP. There is no issue with the router, I have triple checked > the environment file and the call and IRLP node numbers are there in lower > case! The hosts file is also configured correctly. Here is my hosts file: > > # > # /etc/hosts: static lookup table for host names > # > > 127.0.0.1 localhost > 127.0.0.1 localhost.localdomain localhost > 127.0.0.1 config.allstarlinl.org < > http://config.allstarlinl.org/> > 127.0.0.1 stn388 > #: : 1 > > #End of file > > Any help would be much appreciated! > > Thank you, > Glenn Maclean WA7SPY > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp > From wa7spy at att.net Sun May 26 12:53:32 2019 From: wa7spy at att.net (Glenn Maclean) Date: Sun, 26 May 2019 09:53:32 -0700 Subject: [Arm-allstar-irlp] Brand new with Allstar Host name does not resolve outgoing ports not forwarded In-Reply-To: References: <58770CE5-768E-4F43-846F-425524FDB270@att.net> Message-ID: <49DBE681-98C1-4001-92C4-864E7B29B83A@att.net> I am using https://hamvoip.org/RPi2/RPi2-3_V1.5rc50_Allstar.img.xz Downloaded from the Ham VOIP website. Still unable to get IRLP to work. The problem is in the PGP. I have used WSCP to transfer the searing.pgp file to the .pgp folder which does not list with the ls command and pop command does not work so there is something wrong with my set top but do not know where to look? The old raspberry pi computer works just fine with the IRLP board. I am using a brand new 3b+ raspberry pi for the Allstar set up Glenn WA7SPY > On May 26, 2019, at 6:06 AM, Darrell Wilkinson via ARM-allstar-irlp wrote: > > Just for the asking which allstar .img are you using. The .img you download > from the allstar website is a raspbian stretch linux , the .img you > download from hamvoip is arch linux. The IRLP support is made for arch. Why > I ask this is you said you logged in as repeater which is what you would be > using if you where using the raspbian stretch linux. I would download a new > .img from hamvoip follow the howto to install IRLP and I bet you could get > it to work. On the other side of that coin I have tried building a bridge > out of the raspbian stretch .img myself but so far no luck getting it to > work right > > On Thu, May 23, 2019 at 7:09 PM "Glenn Maclean via ARM-allstar-irlp" < > arm-allstar-irlp at hamvoip.org > wrote: > >> Hi, >> I am very new to Allstar and just got my node up and running. I was able >> to get Echolink to work without issue and Allstar node seems to be working. >> When I run the IRLP troubleshooting script as user repeater I am getting >> two errors. >> 1. Ports 873, 8873,10000, 15425,15426,15427 do not work outbound >> >> 2. Your node?s hostname does not resolve >> >> I am using an ATT router with the raspberry pi IP address in the DMZ. >> Using DHCP I had not issues what so ever with the original IRLP raspberry >> pi with the IRLP board using the same router with the raspberry pi in the >> DMZ using DHCP. There is no issue with the router, I have triple checked >> the environment file and the call and IRLP node numbers are there in lower >> case! The hosts file is also configured correctly. Here is my hosts file: >> >> # >> # /etc/hosts: static lookup table for host names >> # >> >> > 127.0.0.1 localhost >> 127.0.0.1 localhost.localdomain localhost >> 127.0.0.1 config.allstarlinl.org < >> http://config.allstarlinl.org/ > >> 127.0.0.1 stn388 >> #: : 1 >> >> #End of file >> >> Any help would be much appreciated! >> >> Thank you, >> Glenn Maclean WA7SPY >> _______________________________________________ >> ARM-allstar-irlp mailing list >> ARM-allstar-irlp at hamvoip.org >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp >> > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp From wa7spy at att.net Sun May 26 23:37:23 2019 From: wa7spy at att.net (Glenn Maclean) Date: Sun, 26 May 2019 20:37:23 -0700 Subject: [Arm-allstar-irlp] Still can't get IRLp to work with hamvoip version of allstar Message-ID: I am making progress getting IRLP to work, The PGP keys now pass. I took one of my other IRLP Nodes (Node 3860)and put the information on the AllStar Raspberry Pi. There are two issues from the trouble shooting script now I am using the image file from hamvoip RPi2-3_V1.5rc50_Allstar.img 1.I am getting outbound port fail on the following ports: 873,8873,10000,15425,15426,15427 2. Your node?s hostname DOES NOT resolve The raspberryPi is in the DMZplus zone all ports are open. The old IRLP node which is also a RaspberryPi using the same router and putting the IP address in the DMZplus on my ATT Uverse Router passes all tests just fine! /etc/hosts # /etc/hosts: static lookup table for host names # # 127.0.0.1 localhost.localdomain localhost 127.0.0.1 config.allstarlink.org 127.0.0.1 stn3860 127.0.1.1 raspberrypi ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # End of file Lgged in as repeater pep -kv stn3860 works! The new node information I am using is Node Number 3860 under my call WA7SPY So where do I go to fix the node?s host name DOES NOT resolve? What do I need to do to get the ports to forward and very sure it is not the router? The environment file is correct my call in lower case wa7spy Stn3860 The /etc/asterisk/irlp.conf is also correct per the hamvoip instructions. Thank you, Glenn Maclean WA7SPY From wa7spy at att.net Mon May 27 14:44:49 2019 From: wa7spy at att.net (Glenn Maclean) Date: Mon, 27 May 2019 11:44:49 -0700 Subject: [Arm-allstar-irlp] I got IRLP working Message-ID: <893A17D2-9238-4CBD-AD84-6FE207B8BA79@att.net> Thank you everyone for the help and suggestions. I am happy to say I was able to get IRLp up and working. This may help others who are trying to add IRLP. What I learned: 1. The IRLP troubleshooting script when used with Allstar IRLP showed Node?s Host name DOES NOT resolve. 2. Outbound ports 873, 8873,10000,15425,15426,15427 are not forwarded correctly even though the IP address is in the DMZ of my router, These two issues are normal with the Allstar set up and IRLP is working fine. The lesson I learned is get IRLp set up and configured per the Ham Voip website instructions, Try connecting to other nodes. If it connects both directions IRLp is working despite the troubleshooting script findings on the to above items. Thanks again for everyone?s help Glenn Maclean WA7SPY From tpwaterman at gmail.com Mon May 27 14:54:42 2019 From: tpwaterman at gmail.com (Pres W) Date: Mon, 27 May 2019 14:54:42 -0400 Subject: [Arm-allstar-irlp] I got IRLP working In-Reply-To: <893A17D2-9238-4CBD-AD84-6FE207B8BA79@att.net> References: <893A17D2-9238-4CBD-AD84-6FE207B8BA79@att.net> Message-ID: Terrific news. All that needs to be tested is can you receive incoming IRLP calls? Pres W2PW On Mon, May 27, 2019, 2:44 PM "Glenn Maclean via ARM-allstar-irlp" < arm-allstar-irlp at hamvoip.org> wrote: > Thank you everyone for the help and suggestions. I am happy to say I was > able to get IRLp up and working. This may help others who are trying to add > IRLP. What I learned: > > 1. The IRLP troubleshooting script when used with Allstar IRLP showed > Node?s Host name DOES NOT resolve. > > 2. Outbound ports 873, 8873,10000,15425,15426,15427 are not forwarded > correctly even though the IP address is in the DMZ of my router, > > These two issues are normal with the Allstar set up and IRLP is working > fine. The lesson I learned is get IRLp set up and configured per the Ham > Voip website instructions, Try connecting to other nodes. If it connects > both directions IRLp is working despite the troubleshooting script findings > on the to above items. > > Thanks again for everyone?s help > Glenn Maclean WA7SPY > _______________________________________________ > ARM-allstar-irlp mailing list > ARM-allstar-irlp at hamvoip.org > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp >