Date   

Embedded Node Help ( formally IRLP] 20 years for Node 5960)

Phil Zocco
 

Hi Gary,

Thanks for the congrats and sorry to hear about your health issues.

As far as that the embedded node, you've just asked for help from the group. Maybe Dace C is watching.

If anyone can help Gary, please speak up.

Good luck getting back on the air.

73,

Phil N1BOW

-----Original Message-----
From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Gary - AG0N
Sent: Sunday, June 12, 2022 11:55 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] 20 years for Node 5960



On Jun 11, 2022, at 21:12, Phil Zocco <n1bow@...> wrote:

Just wanted to mention that this weekend marks my 20th anniversary with IRLP and node 5960, originally node 596.
Congratulations, Phil!

Hey, do you know anyone with good working knowledge of Dave�s embedded node? I bought one (slightly used one month) from a guy. It was on the air for a bit and then he lost interest and went away from it. He offered it to me for half price so I grabbed it to replace my crashed node (computer). I have installed a new firmware chip from Dave (LTD), but have had a lot of medical issues come up, as well as mental ones.

I need help! I�d like to put it on the air so my node is back on. Every time I get it out and look at it wanting to work on it, I mostly draw blanks. I�d really like to get back on the network so I can get to other more important things. The firmware from Dave is supposed to be set up with my 3055 number, despite the fact that it�s been off the air for quite awhile.

Any help or steerage you can provide would sure be welcome. I�m just hoping I am capable of getting it back up and running.

Thanks,
Gary - AG0N


Re: 20 years for Node 5960

Gary - AG0N
 

On Jun 11, 2022, at 21:12, Phil Zocco <n1bow@...> wrote:

Just wanted to mention that this weekend marks my 20th anniversary with IRLP and node 5960, originally node 596.
Congratulations, Phil!

Hey, do you know anyone with good working knowledge of Dave’s embedded node? I bought one (slightly used one month) from a guy. It was on the air for a bit and then he lost interest and went away from it. He offered it to me for half price so I grabbed it to replace my crashed node (computer). I have installed a new firmware chip from Dave (LTD), but have had a lot of medical issues come up, as well as mental ones.

I need help! I’d like to put it on the air so my node is back on. Every time I get it out and look at it wanting to work on it, I mostly draw blanks. I’d really like to get back on the network so I can get to other more important things. The firmware from Dave is supposed to be set up with my 3055 number, despite the fact that it’s been off the air for quite awhile.

Any help or steerage you can provide would sure be welcome. I’m just hoping I am capable of getting it back up and running.

Thanks,
Gary - AG0N


Re: 20 years for Node 5960

 

On 12/6/22 1:12 pm, Phil Zocco wrote:

Greetings,

 

Just wanted to mention that this weekend marks my 20th anniversary with IRLP and node 5960, originally node 596.

 

So far so good. Thanks to Dave C, Dave G and all who have helped me thru the years.

This weekend, 21 years ago, 6300 (formerly 630) became the first IRLP node in VK3.  My own node - 6390 (639) followed in the first week of September that year.  6390 is currently offline (but reporting to the servers), until I can get a chance to rebuild it on a new PC. 

Time flies, as even the newest part of my IRLP infrastructure - reflector 9550, turns 13 later this year.


-- 73 de Tony VK3JED/VK3IRL http://vkradio.com


Re: 20 years for Node 5960

Vince Buono
 

Hi Phil,

Well said! I too have been on IRLP since 2/2/2002; originally as node 491 and then 4910. It has been a great run. I’ve had many good QSO’s on the East Coast Reflector, and many other nodes. Thanks again to Dave C, Dave G, and Vic - N3IO, who introduced me to IRLP.

73, Vince WA3ADI 




Re: 20 years for Node 5960

Rick Szajkowski
 

Congrats

I have been on and some time off for over 20 years now also

Keep up the great work

Node 212 ( ops 2120)

Richard Szajkowski VA3RZS,VA3ZJ,VE3BTE

On Jun 12, 2022, at 12:34 AM, John <gielisj@...> wrote:

Hear Hear,
Dave, light up the candles, and we'll all fly over for your birthday
and help blow them out.

Cheers from Down Under
VK4JKL & co

LOL


On 12/06/2022 1:26 pm, K7FZO wrote:
We join you in sending our thanks to the IRLP team. Our node 7808 has been on the air since the summer of 2002.
73,
Thom
K7FZO
--
73 de K7FZO / Thom




Re: 20 years for Node 5960

John
 

Hear Hear,
Dave, light up the candles, and we'll all fly over for your birthday
and help blow them out.

Cheers from Down Under
VK4JKL & co

LOL

On 12/06/2022 1:26 pm, K7FZO wrote:
We join you in sending our thanks to the IRLP team. Our node 7808 has been on the air since the summer of 2002.
73,
Thom
K7FZO
--
73 de K7FZO / Thom


Re: 20 years for Node 5960

Cary Honeywell
 

Congrats. Long hauler. I brought up 2040 in September 2001 and 2053 in 2007. Dave and his crew have been a great resource.

_ Cary _
VE3EV
Node 2040 2053


On Sat, Jun 11, 2022 at 11:12 PM Phil Zocco <n1bow@...> wrote:

Greetings,

 

Just wanted to mention that this weekend marks my 20th anniversary with IRLP and node 5960, originally node 596.

 

So far so good. Thanks to Dave C, Dave G and all who have helped me thru the years.

 

73,

 

Phil N1BOW

Nodes 5960 and 4656

AMT MP 113.6

Niantic, CT USA Earth


Re: 20 years for Node 5960

K7FZO
 

We join you in sending our thanks to the IRLP team. Our node 7808 has been on the air since the summer of 2002.

73,
Thom
K7FZO
--
73 de K7FZO / Thom


20 years for Node 5960

Phil Zocco
 

Greetings,

 

Just wanted to mention that this weekend marks my 20th anniversary with IRLP and node 5960, originally node 596.

 

So far so good. Thanks to Dave C, Dave G and all who have helped me thru the years.

 

73,

 

Phil N1BOW

Nodes 5960 and 4656

AMT MP 113.6

Niantic, CT USA Earth


Re: Tracing a fault on a V3 Interface board

ray_gardiner
 

Many thanks for that,  the FET's tested OK,  and the fault was in the cabling to the DB9,  the V3 interface board was fine.  

I'll put the system back on test  running from the local network for a while before relocating to the remote site.

Regards
Ray VK3YNV


Re: Tracing a fault on a V3 Interface board

David Cameron - IRLP
 

R38 has nothing to do with the PTT. It forms a voltage divider on the input of the COS detection circuit. It is shorted with the Logic select jumper. Remove or change the LOGIC SELECT jumper and the short will go away.

R37 is the pull up for the AUX3 output, not the PTT. That is R12 beside the 10 pin connector.

The issue you have is likely the U5 FETs are shorted. They can short when subjected to static discharge. It is one of the most common failures I see. The FET U5 and U6 are the same IRF 7313 dual N-channel FET chip. U5 controls PTT and AUX3, U6 controls AUX1 and AUX2.

You can try swapping the two FETs - the problem will follow the FET.

Dave Cameron
VE7LTD


On 2022-06-07 4:06 a.m., ray_gardiner wrote:
Hi All, 

I'm aware that the schematics for the V3 interface board seem to be unavailable,  but I'm trying to trace a fault on the FET PTT output.

I'm driving the PTT line on a Unilab KL470 in parallel with the Open Collector output of a VK5DJ controller. 

I've removed the 100K R37 open drain pull up on U5,  and everything is working fine.  But I noticed while tracing the circuit that I measure short cct across R38,  so 
I removed R38 and measured it out of circuit and it's fine 3.09K

So it seems there is a short somewhere else. 

I don't need the full schematics,  just the output circuit and where R38 fits in the scheme of things. 

Regards
Ray
VK3YNV  
PS. The IRLP Node is 6990 The Shepparton & District Radio Club Mt Wombat repeater. 

 
 


Tracing a fault on a V3 Interface board

ray_gardiner
 
Edited

Hi All, 

I'm aware that the schematics for the V3 interface board seem to be unavailable,  but I'm trying to trace a fault on the FET PTT output.

I'm driving the PTT line on a Unilab KL470 in parallel with the Open Collector output of a VK5DJ controller. 

I've removed the 100K R12 open drain pull up on U5,  and everything is working fine.  But I noticed while tracing the circuit that I measure short cct across R38,  so 
I removed R38 and measured it out of circuit and it's fine 30.9K

So it seems there is a short somewhere else. 

I don't need the full schematics,  just the output circuit and where R38 fits in the scheme of things. 

Regards
Ray
VK3YNV  
PS. The IRLP Node is 6990 The Shepparton & District Radio Club Mt Wombat repeater. 


Re: IRLP node 1041 help

Dave K9DC
 


https://status.irlp.net/?nodeid=1041

If you turn it back on, it will show up.

-k9dc

On Jun 5, 2022, at 17:07, ricging via groups.io <rginger@...> wrote:



Hi David:

 

My IRLP node 1041 located in Sicamous BC on frequency 147.540 does not appear on Canada NodeID list.

 

Can you please help get that showing again?

 

PS:  hard drive problem which is corrected

 

Richard Ginger

VE7BYN

 

 

 

 


IRLP node 1041 help

ricging
 

Hi David:

 

My IRLP node 1041 located in Sicamous BC on frequency 147.540 does not appear on Canada NodeID list.

 

Can you please help get that showing again?

 

PS:  hard drive problem which is corrected

 

Richard Ginger

VE7BYN

 

 

 

 


Re: Issue reviving Nano Node after power failure

Ronald Payne
 

I had a node do something similar, and it turned out that the power supply (Wall wart) didnt fully recover. I replace the original one with a slightly up scale unit.


On Mon, May 23, 2022 at 5:14 PM Steve Herman <w7voa@...> wrote:

We had an hours-long power failure and after the juice came back on my IRLP Nano-Node seems to have an issue fully rebooting and is just displaying LOADING SYSTEM... 
I was able to control the node from the LAN IP but there was no audio coming through on RF. I then did a complete shutdown and after a while powered on the node again but it still doesn't get past LOADING SYSTEM... 
Online the node status is showing as idle. But after the attempted reboot I'm no longer even able to log on via the LAN to get to the admin interface. 
Any suggestions most welcome. 

Steve 
W7VOA 
IRLP Node 3510 


Re: Issue reviving Nano Node after power failure

ai6bx
 

Unfortunately I have had this happen a few times as some of the software on the Nano SD card really does not like hard shutdowns. After sending the node back to Mark for a new image and testing, I have learned to make a back up image as soon as I complete my custom items. I was lucky once and was able to take a fresh card and burn an image of the old card to the new one and things worked again.

Mark is up and operational again so I am certain he can assist.

Keith - Ai6bx


Issue reviving Nano Node after power failure

 

We had an hours-long power failure and after the juice came back on my IRLP Nano-Node seems to have an issue fully rebooting and is just displaying LOADING SYSTEM... 
I was able to control the node from the LAN IP but there was no audio coming through on RF. I then did a complete shutdown and after a while powered on the node again but it still doesn't get past LOADING SYSTEM... 
Online the node status is showing as idle. But after the attempted reboot I'm no longer even able to log on via the LAN to get to the admin interface. 
Any suggestions most welcome. 

Steve 
W7VOA 
IRLP Node 3510 


Fldigi and voice Digi Trivia net on 9204

Tommy KA3TKW
 

Hello I'm KA3TKW Tom in Harrisburg pa.   If anyone is interested in joining us Weds evenings at 8 pm est on the 9204 reflector you are welcome 
to join us.   I run a fun digital trivia net where I ask 15 trivia questions and send them using different modes with fldigi....cw.  Rtty. Contesa. Psk. 
Throb.  Thor. Mfsk32 modes.  I also ask the question thru voice so if your not interested in fldigi you can join us thru voice answers.  I take 
checkins then start the questions and we roll down the check-in list and you can answer the trivia questions....it's alot of fun.  Hope to see 
you on the 9204 irlp reflector.    Weds at 8 pm est.  Thanks. KA3TKW. Tom


Re: Node 6220

Rick Szajkowski
 

That’s simple , he would have to port forward the new port through his router , once done then you should connect

Richard Szajkowski VA3RZS,VA3ZJ,VE3BTE

On May 18, 2022, at 5:05 AM, tomsdad97 <sharpst@...> wrote:

G'day John,

I think I'm getting beyond my pay scale!

telnet stn6220.ip.irlp.net 15425

telnet: Unable to connect to remote host: Connection refused <--refused

telnet stn6220.ip.irlp.net XXXX <--new port

telnet: Unable to connect to remote host: Connection timed out<-- time out.

The sshd_config had port 22 and 15426 enabled and I changed 15426 to the new XXXX port.

Any of this make sense?

Steve VK2ARS Node6255

-----Original Message----- From: John
Sent: Wednesday, May 18, 2022 6:53 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220

So what port did you change it to?
That port # will have regard to the telnet command.

If I run a telnet test to 6220 on 15425
Connecting To stn6220.ip.irlp.net...Could not open connection to the host, on
port 15425: Connect failed

If I run that w/o the port #
Connecting To stn6220.ip.irlp.net...Could not open connection to the host, on
port 23: Connect failed

Your move Steve


On 18/05/2022 6:18 pm, tomsdad97 wrote:
Interestingly enough I was given permission to take a look using pico -w /etc/ssh/sshd_config and found that 2 ports were enabled 22 and 15426. (on my node there is only 1 port enabled fwiw)

Changed 15426 to another value saved the change and rebooted the system.

I now get "the node that you called is not responding" so something has happened.

Also I cannot SSH back into the Node using the new port value?

Advice?

Steve VK2ARS Node 6255

-----Original Message----- From: Dave K9DC via groups.io
Sent: Tuesday, May 17, 2022 11:33 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220


It looks like you have configured SSH to use port 15425. Unfortunately, port 15425 must be available for IRLP to use. Using an on board editor edit the file /etc/ssh/sshd_config and change it to something else, like 15427 perhaps.

Good catch John!

pico -w /etc/ssh/sshd_config


Dave K9DC, K9IP



On May 17, 2022, at 04:50, tomsdad97 <sharpst@...> wrote:
G'day John,

Yes, that's what it returned a year ago as well!

Do you get the same message I get if you attempt to connect?

Cheers,

Steve VK2ARS Node 6255

-----Original Message----- From: John
Sent: Tuesday, May 17, 2022 6:38 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220

I think I see an issue here Steve.
When I telnet to 6220
telnet stn6220.ip.irlp.net 15425
The response displays
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u2

which hangs there. I did not wait for the other end to respond any further, as
it seems his LAN IP system is incorrect.
The SSH port should not be configured like that,
but that is where I leave the train.

Hey !! We've been down this track a year ago??
see below..

73 John


On 17/05/2022 5:37 pm, tomsdad97 wrote:
Wow, a year ago I was trying to sort this problem and it's still unresolved!

When I attempt to connect to Node 6220 I get the following reply "An error has occurred the connection can not be authenticated". (I have also attempted to connect from Nodes other than mine with the same result.)

I finally managed to get hold of the administrator of 6220 and advised him of the issue, he ran the troubleshoot-irlp script and he reports no problems reported.

Outbound connections from 6220 work as do Echolink connections both in and out.

Are there any other suggestions on what the problem may be?

Cheers,
Steve VK2ARS Node 6255


















Re: Node 6220

tomsdad97
 

Hi Dave, I did think of the router after the event!

The Node is about 100km away I think someone will be there over the weekend (it's in the Radio Clubrooms) so hopefully they'll be able to port forward 2480 and see what happens.

Thanks for the explanations, helps me a lot.

73 Steve VK2ARS

-----Original Message-----
From: Dave K9DC via groups.io
Sent: Wednesday, May 18, 2022 8:58 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220


If you changed SSH to use port 2480, did you make a corresponding change to the site's router port forwarding configuration? Whatever port you choose for SSH must be explicitly allowed through, or forwarded by, the router, if you want to access the node externally.

If you are now getting “Connection refused” from port 15425, something else has prevented IRLP from starting.

Basically, when an IRLP node is started, all the processes used by the computer, including SSH are started first. The last thing to start is IRLP itself. If you have used one of the ports required by IRLP, 15425 for example, for SSH, IRLP will not be able start its listener on that port, because it is already in use by the operating system.

For the ports used by IRLP, see https://www.irlp.net/new-install/routers/General.htm. The ports required incoming at the top of the page must be avoided. SSH can be changed to something else (2480 in your case), but anything you chose must be allowed through your router.

If you want to play it safe, you may want to avoid any ports listed on that page entirely, although technically the outbound ports and the install only ports will not interfere. For example on my nodes, I generally use 15427 for SSH.

I don’t know where 6220 is physically located, but you may have to make a trip to that site to fix it, if you need to change the router.

Another ultimate solution might be to use IRLP VPN, which requires no port forwarding or any special router configuration to work. But you will have to visit the 6220 site to set it up. Also IRLP VPN blocks port TCP 22 so you must pick something else for SSH when using IRLP VPN.

You can open a support ticket with an email to installs@ irlp.net, but the support team will need SSH to work to help you very much.


Dave K9DC, K9IP



On May 18, 2022, at 05:37, tomsdad97 <sharpst@...> wrote:

I changed it to 2480 fwiw.

I heard it restart over the air on the repeater, IRLP enabled, Echolink Node enabled messages were heard.

Steve


-----Original Message----- From: John
Sent: Wednesday, May 18, 2022 7:30 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220

The standard (default) telnet port is 15425 so we all what it is.
The fact you cannot remotely SSH into it now, raises another issue.
Are you sure 6220 did reboot?
Also, what catches my eye, is the reply you get from a telnet test to 6220.
The response I get is
'Could not open connection to the host, on port xxxxx: Connect failed'

In my irlp install, /etc/ssh/sshd_config needs ROOT permission.
I also noted to save and exit AND
run service ssh restart
but a reboot should resolve that...if it did?

Scratching the cobwebs in the 12 hrs might clear the fog.

John

On 18/05/2022 7:05 pm, tomsdad97 wrote:
G'day John,

I think I'm getting beyond my pay scale!

telnet stn6220.ip.irlp.net 15425

telnet: Unable to connect to remote host: Connection refused <--refused

telnet stn6220.ip.irlp.net XXXX <--new port

telnet: Unable to connect to remote host: Connection timed out<-- time out.

The sshd_config had port 22 and 15426 enabled and I changed 15426 to the new XXXX port.

Any of this make sense?

Steve VK2ARS Node6255

-----Original Message----- From: John
Sent: Wednesday, May 18, 2022 6:53 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220

So what port did you change it to?
That port # will have regard to the telnet command.

If I run a telnet test to 6220 on 15425
Connecting To stn6220.ip.irlp.net...Could not open connection to the host, on
port 15425: Connect failed

If I run that w/o the port #
Connecting To stn6220.ip.irlp.net...Could not open connection to the host, on
port 23: Connect failed

Your move Steve


On 18/05/2022 6:18 pm, tomsdad97 wrote:
Interestingly enough I was given permission to take a look using pico -w /etc/ssh/sshd_config and found that 2 ports were enabled 22 and 15426. (on my node there is only 1 port enabled fwiw)

Changed 15426 to another value saved the change and rebooted the system.

I now get "the node that you called is not responding" so something has happened.

Also I cannot SSH back into the Node using the new port value?

Advice?

Steve VK2ARS Node 6255

-----Original Message----- From: Dave K9DC via groups.io
Sent: Tuesday, May 17, 2022 11:33 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220


It looks like you have configured SSH to use port 15425. Unfortunately, port 15425 must be available for IRLP to use. Using an on board editor edit the file /etc/ssh/sshd_config and change it to something else, like 15427 perhaps.

Good catch John!

pico -w /etc/ssh/sshd_config


Dave K9DC, K9IP



On May 17, 2022, at 04:50, tomsdad97 <sharpst@...> wrote:

G'day John,

Yes, that's what it returned a year ago as well!

Do you get the same message I get if you attempt to connect?

Cheers,

Steve VK2ARS Node 6255

-----Original Message----- From: John
Sent: Tuesday, May 17, 2022 6:38 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node 6220

I think I see an issue here Steve.
When I telnet to 6220
telnet stn6220.ip.irlp.net 15425
The response displays
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u2

which hangs there. I did not wait for the other end to respond any further, as
it seems his LAN IP system is incorrect.
The SSH port should not be configured like that,
but that is where I leave the train.

Hey !! We've been down this track a year ago??
see below..

73 John


On 17/05/2022 5:37 pm, tomsdad97 wrote:
Wow, a year ago I was trying to sort this problem and it's still unresolved!

When I attempt to connect to Node 6220 I get the following reply "An error has occurred the connection can not be authenticated". (I have also attempted to connect from Nodes other than mine with the same result.)

I finally managed to get hold of the administrator of 6220 and advised him of the issue, he ran the troubleshoot-irlp script and he reports no problems reported.

Outbound connections from 6220 work as do Echolink connections both in and out.

Are there any other suggestions on what the problem may be?

Cheers,
Steve VK2ARS Node 6255
























81 - 100 of 79611