Date   
Re: No voice announcements

AG0N-3055
 

On Feb 21, 2020, at 15:27, Gavin Jacobs <apriljunkbox@...> wrote:

I hear
"Node Number One Zero Zero Zero Link Active", and I don't appear to be getting through, because no one answers my calls.
How do you know there is someone there to answer? Maybe no one is around the radio.

Gary - AG0N

Re: Working IRLP Node For Sale

pete damron
 

Is this a Cameron node?
Enbedded or pie.... I pay shipping.whats the cost?
N5ZLW
3985 / 7533
903-262-5549

On Fri, Feb 21, 2020, 5:37 PM <Rtech.ralph@...> wrote:
If you have all of the documentation including the current passwords I would be interested. doing a re-install may be more than I have time for at the moment. 

I could take the radio as well. LOL 1 more radio around the shack won't be noticed. 

Drop me a note or T1A4N5 if you can get a frght estimate. 

Thanks 

Ralph 
VA6RHG

Re: Working IRLP Node For Sale

Rtech.ralph@...
 

If you have all of the documentation including the current passwords I would be interested. doing a re-install may be more than I have time for at the moment. 

I could take the radio as well. LOL 1 more radio around the shack won't be noticed. 

Drop me a note or T1A4N5 if you can get a frght estimate. 

Thanks 

Ralph 
VA6RHG

Re: No voice announcements

Milt Duquette
 

I tried from Medicine Hat, connected 

On Feb 21, 2020, at 3:27 PM, Gavin Jacobs <apriljunkbox@...> wrote:

I have Node 1196 running on a Raspberry Pi. It was working fine 2 weeks ago. Now, I can connect to 9990 (Echo Reflector) fine, but when I connect to any other node, I get a generic voice announcement. For example, if I run
decode 1000
I hear 
"Node Number One Zero Zero Zero  Link Active", and I don't appear to be getting through, because no one answers my calls.
I did try
troubleshoot-irlp
and all the tests passed (except Echolink port forwarding).

Any suggestions for further testing/troubleshooting?

Thanks,
VE7GSJ

Thanks
 

Milt Duquette

1 (403) 928-1000 (cell)

Web:  http://www.photosbymilt.ca

Emails:

miltduquette@...

Twitter: @milt_duquette




Re: No voice announcements

David Cameron - IRLP
 

Testing should always be done on the Echo reflector (9990 through 9999). Someone is always there to respond back :)

Generic messages come when downloading of the messages from the server fail for some reason. There is an issue we are trying to resolve with the Vancouver server that may be causing this. But it will not affect the ability for your node to communicate to others.

Dave Cameron
VE7LTD

On 2020-02-21 14:27, Gavin Jacobs wrote:
I have Node 1196 running on a Raspberry Pi. It was working fine 2
weeks ago. Now, I can connect to 9990 (Echo Reflector) fine, but when
I connect to any other node, I get a generic voice announcement. For
example, if I run
decode 1000
I hear
"Node Number One Zero Zero Zero Link Active", and I don't appear to
be getting through, because no one answers my calls.
I did try
troubleshoot-irlp
and all the tests passed (except Echolink port forwarding).
Any suggestions for further testing/troubleshooting?
Thanks,
VE7GSJ
Links:
------
[1] https://irlp.groups.io/g/IRLP/message/76849
[2] https://groups.io/mt/71460961/500965
[3] https://irlp.groups.io/g/IRLP/post
[4] https://irlp.groups.io/g/IRLP/editsub/500965
[5] https://irlp.groups.io/g/IRLP/leave/defanged

No voice announcements

Gavin Jacobs
 

I have Node 1196 running on a Raspberry Pi. It was working fine 2 weeks ago. Now, I can connect to 9990 (Echo Reflector) fine, but when I connect to any other node, I get a generic voice announcement. For example, if I run
decode 1000
I hear 
"Node Number One Zero Zero Zero  Link Active", and I don't appear to be getting through, because no one answers my calls.
I did try
troubleshoot-irlp
and all the tests passed (except Echolink port forwarding).

Any suggestions for further testing/troubleshooting?

Thanks,
VE7GSJ

Re: can't connect to our node 5730 raspberry pi

k9dc
 

I did just connect to your repeater, and had a nice conversation with a station, so things appear to be working fine. There is no guarantee that any particular station is still functioning though.

If you want to give me a call on IRLP 4733, or Echolink 4733, I am here for a while.

-k9dc

On Feb 21, 2020, at 10:45, Dave Gingrich <dave@...> wrote:


I know very little about the EchoIRLP software as it is not an IRLP.net product. But are you logged in to Echolink, does your node show up in the list on another client or their website? What is your Echolink ID?

-k9dc

On Feb 21, 2020, at 10:38, Randy N9NWA <@N9nwa> wrote:

Dave, K9dc

I am not sure if irlp works when a station connects to us but I can run the decode 9999 and that works, but this is an echo link problem.
When a user or I try to connect via echo-link the connection times out.

Randy

Re: can't connect to our node 5730 raspberry pi

Randy N9NWA
 

Dave
Yes it does show up as on line. ID is W9DUP-R

Randy

On February 21, 2020 at 9:45 AM k9dc <Dave@...> wrote:



I know very little about the EchoIRLP software as it is not an IRLP.net product. But are you logged in to Echolink, does your node show up in the list on another client or their website? What is your Echolink ID?

-k9dc

On Feb 21, 2020, at 10:38, Randy N9NWA <@N9nwa> wrote:

Dave, K9dc

I am not sure if irlp works when a station connects to us but I can run the decode 9999 and that works, but this is an echo link problem.
When a user or I try to connect via echo-link the connection times out.

Randy



Re: can't connect to our node 5730 raspberry pi

k9dc
 

I know very little about the EchoIRLP software as it is not an IRLP.net product. But are you logged in to Echolink, does your node show up in the list on another client or their website? What is your Echolink ID?

-k9dc

On Feb 21, 2020, at 10:38, Randy N9NWA <@N9nwa> wrote:

Dave, K9dc

I am not sure if irlp works when a station connects to us but I can run the decode 9999 and that works, but this is an echo link problem.
When a user or I try to connect via echo-link the connection times out.

Randy

Re: can't connect to our node 5730 raspberry pi

Randy N9NWA
 

Dave, K9dc

I am not sure if irlp works when a station connects to us but I can run the decode 9999 and that works, but this is an echo link problem.
When a user or I try to connect via echo-link the connection times out.

Randy

On February 21, 2020 at 8:43 AM k9dc <Dave@...> wrote:



So this is an Echolink problem? You did not say that in your original post, so everyone was assuming and testing IRLP. It would help if you could describe the problem you are having, exactly. There are a plethora of problems that can cause Echolink to fail.

-k9dc


On Feb 21, 2020, at 01:02, Randy N9NWA <@N9nwa> wrote:

David
I ran the telnet localhost 15425repeater@stn537:~/$ telnet localhost 15425
This what I get. Looks like the test lines are not there any more but I still cant connect thru the echo-link app.

Randy



Re: can't connect to our node 5730 raspberry pi

k9dc
 

So this is an Echolink problem? You did not say that in your original post, so everyone was assuming and testing IRLP. It would help if you could describe the problem you are having, exactly. There are a plethora of problems that can cause Echolink to fail.

-k9dc

On Feb 21, 2020, at 01:02, Randy N9NWA <@N9nwa> wrote:

David
I ran the telnet localhost 15425repeater@stn537:~/$ telnet localhost 15425
This what I get. Looks like the test lines are not there any more but I still cant connect thru the echo-link app.

Randy

Re: can't connect to our node 5730 raspberry pi

Randy N9NWA
 

John
Thanks I tried that and also rebooted the node. It did not fix it.

Thanks
Randy

John wrote:

You may need to call 'update files' after changing your custom on file.
John @ 6163

On 21/02/2020 3:39:25 PM, Randy N9NWA (@N9nwa) wrote:
David
I have these lines in my custom on file, they have been there for a few years.
I did just comment them out but same problem.
I looked for the lines in other files in case I accidentally copied the lines there but cant find them.
I tried the line in command prompt and it doesn't work. test@irlp:~$ telnet stn5370 15425

Randy

David Cameron - IRLP wrote:
You have added some test lines somewhere in your system:

Trying 73.74.72.150...
Connected to stn5370.
Escape character is '^]'.
stn537 - w9dup : Welcome 159.89.122.231

challenge from 5370: 1582261370821452

test1
test2
test3
Connection closed by foreign host.

That causes the errors. Find and remove those test lines and your
node > will work again.

Dave Cameron


On 20/02/2020 8:56 p.m., Randy N9NWA wrote:
I ran the troubleshoot script and all comes back ok. I get a time
out >> message.
Some of the users connect but they get a rpc time out disconnect
in >> the log.
I rebooted the comcast modem and restarted the router

Re: can't connect to our node 5730 raspberry pi

Randy N9NWA
 

David

I ran the telnet localhost 15425repeater@stn537:~/$ telnet localhost 15425
This what I get. Looks like the test lines are not there any more but I still cant connect thru the echo-link app.

Randy

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
stn537 - w9dup : Welcome 127.0.0.1
Connection closed by foreign host.
repeater@stn537:~/$ repeater@stn537:~/$ telnet localhost 15425
-bash: repeater@stn537:~/$: No such file or directory
repeater@stn537:~/$ Trying 127.0.0.1...
-bash: Trying: command not found
repeater@stn537:~/$ Connected to localhost.
-bash: Connected: command not found
repeater@stn537:~/$ Escape character is '^]'.
-bash: Escape: command not found
repeater@stn537:~/$ stn537 - w9dup : Welcome 127.0.0.1
-bash: stn537: command not found
repeater@stn537:~/$ Connection closed by foreign host.
-bash: Connection: command not found
repeater@stn537:~/$ repeater@stn537:~/$
-bash: repeater@stn537:~/$: No such file or directory
repeater@stn537:~/$



David Cameron - IRLP wrote:

To test locally, you need

telnet localhost 15425

Dave

-------- Original message --------
From: Randy N9NWA <@N9nwa>
Date: 2/20/20 9:39 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] can't connect to our node 5730 raspberry pi

David

I have these lines in my custom on file, they have been there for a few
years.
I did just comment them out but same problem.
I looked for the lines in other files in case I accidentally copied the
lines there but cant find them.
I tried the line in command prompt and it doesn't work. test@irlp:~$
telnet stn5370 15425

Randy

David Cameron - IRLP wrote:
You have added some test lines somewhere in your system:

Trying 73.74.72.150...
Connected to stn5370.
Escape character is '^]'.
stn537 - w9dup : Welcome 159.89.122.231

challenge from 5370: 1582261370821452

test1
test2
test3
Connection closed by foreign host.

That causes the errors. Find and remove those test lines and your node
will work again.

Dave Cameron


On 20/02/2020 8:56 p.m., Randy N9NWA wrote:
I ran the troubleshoot script and all comes back ok. I get a time out
message.
Some of the users connect but they get a rpc time out disconnect in
the log.
I rebooted the comcast modem and restarted the router
  The problem still exists.
I don't know what to do next.
Anyone have any suggestions?

Randy N9NWA
node 5370 W99DUP


Sent from Xfinity Connect Application







Re: can't connect to our node 5730 raspberry pi

John
 

You may need to call 'update files' after changing your custom on file.
John @ 6163

On 21/02/2020 3:39:25 PM, Randy N9NWA (@N9nwa) wrote:
David
I have these lines in my custom on file, they have been there for a few years.
I did just comment them out but same problem.
I looked for the lines in other files in case I accidentally copied the lines there but cant find them.
I tried the line in command prompt and it doesn't work. test@irlp:~$ telnet stn5370 15425
Randy
David Cameron - IRLP wrote:
You have added some test lines somewhere in your system:

Trying 73.74.72.150...
Connected to stn5370.
Escape character is '^]'.
stn537 - w9dup : Welcome 159.89.122.231

challenge from 5370: 1582261370821452

test1
test2
test3
Connection closed by foreign host.

That causes the errors. Find and remove those test lines and your node will work again.

Dave Cameron


On 20/02/2020 8:56 p.m., Randy N9NWA wrote:
I ran the troubleshoot script and all comes back ok. I get a time out message.
Some of the users connect but they get a rpc time out disconnect in the log.
I rebooted the comcast modem and restarted the router

Re: can't connect to our node 5730 raspberry pi

David Cameron - IRLP
 

To test locally, you need

telnet localhost 15425

Dave

-------- Original message --------
From: Randy N9NWA <rbzabel@...>
Date: 2/20/20 9:39 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] can't connect to our node 5730 raspberry pi

David

I have these lines in my custom on file, they have been there for a few
years.
I did just comment them out but same problem.
I looked for the lines in other files in case I accidentally copied the
lines there but cant find them.
I tried the line in command prompt and it doesn't work. test@irlp:~$
telnet stn5370 15425

Randy

David Cameron - IRLP wrote:
> You have added some test lines somewhere in your system:
>
>

> Trying 73.74.72.150...
> Connected to stn5370.
> Escape character is '^]'.
> stn537 - w9dup : Welcome 159.89.122.231
>
> challenge from 5370: 1582261370821452
>
> test1
> test2
> test3
> Connection closed by foreign host.
>
> That causes the errors. Find and remove those test lines and your node
> will work again.
>
> Dave Cameron
>
>
> On 20/02/2020 8:56 p.m., Randy N9NWA wrote:
>> I ran the troubleshoot script and all comes back ok. I get a time out
>> message.
>> Some of the users connect but they get a rpc time out disconnect in
>> the log.
>> I rebooted the comcast modem and restarted the router
>>   The problem still exists.
>> I don't know what to do next.
>> Anyone have any suggestions?
>>
>> Randy N9NWA
>> node 5370 W99DUP
>>
>>
>> Sent from Xfinity Connect Application
>>
>>
>>
>
>
>
>
>



Re: can't connect to our node 5730 raspberry pi

Randy N9NWA
 

David

I have these lines in my custom on file, they have been there for a few years.
I did just comment them out but same problem.
I looked for the lines in other files in case I accidentally copied the lines there but cant find them.
I tried the line in command prompt and it doesn't work. test@irlp:~$ telnet stn5370 15425

Randy

David Cameron - IRLP wrote:

You have added some test lines somewhere in your system:

Trying 73.74.72.150...
Connected to stn5370.
Escape character is '^]'.
stn537 - w9dup : Welcome 159.89.122.231

challenge from 5370: 1582261370821452

test1
test2
test3
Connection closed by foreign host.

That causes the errors. Find and remove those test lines and your node will work again.

Dave Cameron


On 20/02/2020 8:56 p.m., Randy N9NWA wrote:
I ran the troubleshoot script and all comes back ok. I get a time out message.
Some of the users connect but they get a rpc time out disconnect in the log.
I rebooted the comcast modem and restarted the router
  The problem still exists.
I don't know what to do next.
Anyone have any suggestions?

Randy N9NWA
node 5370 W99DUP


Sent from Xfinity Connect Application




Re: can't connect to our node 5730 raspberry pi

David Cameron - IRLP
 

You have added some test lines somewhere in your system:

test@irlp:~$ telnet stn5370 15425
Trying 73.74.72.150...
Connected to stn5370.
Escape character is '^]'.
stn537 - w9dup : Welcome 159.89.122.231

challenge from 5370: 1582261370821452

test1
test2
test3
Connection closed by foreign host.

That causes the errors. Find and remove those test lines and your node will work again.

Dave Cameron

On 20/02/2020 8:56 p.m., Randy N9NWA wrote:
I ran the troubleshoot script and all comes back ok. I get a time out message.
Some of the users connect but they get a rpc time out disconnect in the log.
I rebooted the comcast modem and restarted the router
The problem still exists.
I don't know what to do next.
Anyone have any suggestions?

Randy N9NWA
node 5370 W99DUP


Sent from Xfinity Connect Application

can't connect to our node 5730 raspberry pi

Randy N9NWA
 

I ran the troubleshoot script and all comes back ok. I get a time out message.
Some of the users connect but they get a rpc time out disconnect in the log.
I rebooted the comcast modem and restarted the router
The problem still exists.
I don't know what to do next.
Anyone have any suggestions?

Randy N9NWA
node 5370 W99DUP


Sent from Xfinity Connect Application

Re: How to fix wifi after reinstall for a RPI node

Scott Anderson
 

I forgot to thank David and Nick for the help.
Thank you.

How to fix wifi after reinstall for a RPI node

Scott Anderson
 

Hi to anyone who reads this.
I am posting this for other people who may of had this happen to their node. I am using IRLP V3.0 board and a Raspberry Pi 2 with Debian 10 (buster) image and I had to do a reinstall that caused the wifi to stop working. This is what I had to do to fix it.
Go into pico /etc/network/interfaces and make sure that this is in there.
auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan0
iface wlan0 inet static
          address 0.0.0.0
          netmask 0.0.0.0
          gateway 0.0.0.0
          wpa-ssid router name
          wpa-psk router pass word

hit control X Y to save and enter.
reboot and you should have wifi now.
I wish the best of luck.
Scott