Date   
Re: IRLP COS is not operating

Ralph
 

At this point, much more not working then working. 
Unit has been in service same radio, same location & power supply etc for almost 3 years
I have added a ground from the body of the node (connected to the main bus) to the shack ground & the Negative B+ with no change 

Re: IRLP COS is not operating

Ralph
 

+Pin voltage from the radio has no change between working and not working. roughly 4 - 4.1 volts when recieving a signal. 

Re: IRLP COS is not operating

David Cameron - IRLP
 

Very rare that it would be intermittent like this. Next time it acts up, I would check all your GROUND between the radio and the board. Often if there is a bad ground, the voltage potential can be too low to trigger the COS.

Also, try changing the position of the LGC LVL jumper.

The whole COS system is simple logic, nothing more.

Dave Cameron
VE7LTD

On 01/12/2019 5:15 p.m., @Rtech wrote:
I have an issue. If the node is powered down for extended time, I can turn it and the radio on & all works normal.
After running for some time (sometimes for a couple of hours sometime a couple of days) the node will stop working.
When it fails, the COS light on the board fails to turn on when a signal is received.
I can use the console and log into a noce or the Echo Test.
The radio will transmit the audi it receives from the internet perfectly
The board will acknowledge the DTMF tones it sees by flashing the DTMF light on the board.
It will not illuminate the COS light & will not pass the commands on to the internet
It will not pass the voice transmitted into the radio on to the internet.

I have tried different radios. (Icom & Yeasu) that require different set up on the COS jumper.
When i watch the pin for the COS while the radio is actively receiving, the icom shows 4.2 volts @ the COS input pin (DB() as well as at the centre pin of the jumper (with the jumper removed) Same with the Yeasu drops to 0.1 Volt at the COS pin when in receive.
Pin test the wire harness from DB9 to the Header pin OK.
Check by substitution the db9-header pin cable. I have access to an old V3 board and subberd in the harness from it (obviously no audio but it keys the transmitter when announcing IP and Node Activation.

Myassumption, failed component level repair required on the IRLP board.

My limited knowledge of how the system works would suggest that this is not a firmware/ software issue.

Any other suggestion gratefully accepted or information on where to send the board for repair if that is available.

Or  Is there an expedite method available for ordering a replacement board?

Ralph Garnett
VA6RHG
Node 1188

Re: IRLP COS is not operating

bruce clements
 

I agree it's not port forwarding...

I would take the cos line and remove it from the db9. Solder a wire to the cos pin on the db9 and connect it to the cos signal from the radio.  I would use a alligator clip..
When the cos fails , disconnect the wire from the cos from the radio. Take the db9 connection and put on ground. If the led fails to light it's hardware.
If it's a older version 2 board I had a transistor issue and I replaced it.

If it's a version 3 contact irlp guys and buy a new one.

Bruce Ve3bv 



Sent from my Galaxy Tab® E

-------- Original message --------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@...>
Date: 2019-12-01 8:59 PM (GMT-05:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] IRLP COS is not operating

Port forwarding (or lack of) isn't going to affect the hardware.

I think you may need to be a little clearer on what is going on with the COR. With just the same radio, what does it measure when it is working and what does it measure when it it isn't working?

Mick - W7CAT
Node 3464

----- Original Message -----
From: "Milt Duquette via Groups.Io"
To: IRLP@irlp.groups.io
Sent: Sunday, December 01, 2019 06:23:58 PM
Subject: Re: [IRLP] IRLP COS is not operating

> Ralph, did u change service providers and did u do the port forwarding through the new isp?
> > On Dec 1, 2019, at 6:16 PM, rtech.ralph@... wrote:
> >
> > ?I have an issue. If the node is powered down for extended time, I can turn it and the radio on & all works normal.
> > After running for some time (sometimes for a couple of hours sometime a couple of days) the node will stop working.
> > When it fails, the COS light on the board fails to turn on when a signal is received.
> > I can use the console and log into a noce or the Echo Test.
> > The radio will transmit the audi it receives from the internet perfectly
> > The board will acknowledge the DTMF tones it sees by flashing the DTMF light on the board.
> > It will not illuminate the COS light & will not pass the commands on to the internet
> > It will not pass the voice transmitted into the radio on to the internet.
> >
> > I have tried different radios. (Icom & Yeasu) that require different set up on the COS jumper.
> > When i watch the pin for the COS while the radio is actively receiving, the icom shows 4.2 volts @ the COS input pin (DB() as well as at the centre pin of the jumper (with the jumper removed) Same with the Yeasu drops to 0.1 Volt at the COS pin when in receive.
> > Pin test the wire harness from DB9 to the Header pin OK.
> > Check by substitution the db9-header pin cable. I have access to an old V3 board and subberd in the harness from it (obviously no audio but it keys the transmitter when announcing IP and Node Activation.
> >
> > Myassumption, failed component level repair required on the IRLP board.
> >
> > My limited knowledge of how the system works would suggest that this is not a firmware/ software issue.
> >
> > Any other suggestion gratefully accepted or information on where to send the board for repair if that is available.
> >
> > Or Is there an expedite method available for ordering a replacement board?
> >
> > Ralph Garnett
> > VA6RHG
> > Node 1188
> >
>
>
>
>
--

Re: IRLP COS is not operating

Teton Amateur Radio Repeater Association (TARRA)
 

Port forwarding (or lack of) isn't going to affect the hardware.

I think you may need to be a little clearer on what is going on with the COR. With just the same radio, what does it measure when it is working and what does it measure when it it isn't working?

Mick - W7CAT
Node 3464

----- Original Message -----
From: "Milt Duquette via Groups.Io"
To: IRLP@irlp.groups.io
Sent: Sunday, December 01, 2019 06:23:58 PM
Subject: Re: [IRLP] IRLP COS is not operating

> Ralph, did u change service providers and did u do the port forwarding through the new isp?
> > On Dec 1, 2019, at 6:16 PM, rtech.ralph@... wrote:
> >
> > ?I have an issue. If the node is powered down for extended time, I can turn it and the radio on & all works normal.
> > After running for some time (sometimes for a couple of hours sometime a couple of days) the node will stop working.
> > When it fails, the COS light on the board fails to turn on when a signal is received.
> > I can use the console and log into a noce or the Echo Test.
> > The radio will transmit the audi it receives from the internet perfectly
> > The board will acknowledge the DTMF tones it sees by flashing the DTMF light on the board.
> > It will not illuminate the COS light & will not pass the commands on to the internet
> > It will not pass the voice transmitted into the radio on to the internet.
> >
> > I have tried different radios. (Icom & Yeasu) that require different set up on the COS jumper.
> > When i watch the pin for the COS while the radio is actively receiving, the icom shows 4.2 volts @ the COS input pin (DB() as well as at the centre pin of the jumper (with the jumper removed) Same with the Yeasu drops to 0.1 Volt at the COS pin when in receive.
> > Pin test the wire harness from DB9 to the Header pin OK.
> > Check by substitution the db9-header pin cable. I have access to an old V3 board and subberd in the harness from it (obviously no audio but it keys the transmitter when announcing IP and Node Activation.
> >
> > Myassumption, failed component level repair required on the IRLP board.
> >
> > My limited knowledge of how the system works would suggest that this is not a firmware/ software issue.
> >
> > Any other suggestion gratefully accepted or information on where to send the board for repair if that is available.
> >
> > Or Is there an expedite method available for ordering a replacement board?
> >
> > Ralph Garnett
> > VA6RHG
> > Node 1188
> >
>
>
>
>
--

Re: IRLP COS is not operating

Milt Duquette
 

Ralph,  did u change service providers and did u do the port forwarding through the new isp?



On Dec 1, 2019, at 6:16 PM, rtech.ralph@... wrote:

I have an issue. If the node is powered down for extended time, I can turn it and the radio on & all works normal. 
After running for some time (sometimes for a couple of hours sometime a couple of days) the node will stop working.
When it fails, the COS light on the board fails to turn on when a signal is received.
I can use the console and log into a noce or the Echo Test. 
The radio will transmit the audi it receives from the internet perfectly
The board will acknowledge the DTMF tones it sees by flashing the DTMF light on the board. 
It will not illuminate the COS light & will not pass the commands on to the internet
It will not pass the voice transmitted into the radio on to the internet. 

I have tried different radios. (Icom & Yeasu) that require different set up on the COS jumper. 
When i watch the pin for the COS while the radio is actively receiving, the icom shows 4.2 volts @ the COS input pin (DB() as well as at the centre pin of the jumper (with the jumper removed) Same with the Yeasu drops to 0.1 Volt at the COS pin when in receive. 
Pin test the wire harness from DB9 to the Header pin OK.
Check by substitution the db9-header pin cable. I have access to an old V3 board and subberd in the harness from it (obviously no audio but it keys the transmitter when announcing IP and Node Activation. 

Myassumption, failed component level repair required on the IRLP board. 

My limited knowledge of how the system works would suggest that this is not a firmware/ software issue.

Any other suggestion gratefully accepted or information on where to send the board for repair if that is available. 

Or  Is there an expedite method available for ordering a replacement board?

Ralph Garnett 
VA6RHG
Node 1188

IRLP COS is not operating

Ralph
 

I have an issue. If the node is powered down for extended time, I can turn it and the radio on & all works normal. 
After running for some time (sometimes for a couple of hours sometime a couple of days) the node will stop working.
When it fails, the COS light on the board fails to turn on when a signal is received.
I can use the console and log into a noce or the Echo Test. 
The radio will transmit the audi it receives from the internet perfectly
The board will acknowledge the DTMF tones it sees by flashing the DTMF light on the board. 
It will not illuminate the COS light & will not pass the commands on to the internet
It will not pass the voice transmitted into the radio on to the internet. 

I have tried different radios. (Icom & Yeasu) that require different set up on the COS jumper. 
When i watch the pin for the COS while the radio is actively receiving, the icom shows 4.2 volts @ the COS input pin (DB() as well as at the centre pin of the jumper (with the jumper removed) Same with the Yeasu drops to 0.1 Volt at the COS pin when in receive. 
Pin test the wire harness from DB9 to the Header pin OK.
Check by substitution the db9-header pin cable. I have access to an old V3 board and subberd in the harness from it (obviously no audio but it keys the transmitter when announcing IP and Node Activation. 

Myassumption, failed component level repair required on the IRLP board. 

My limited knowledge of how the system works would suggest that this is not a firmware/ software issue.

Any other suggestion gratefully accepted or information on where to send the board for repair if that is available. 

Or  Is there an expedite method available for ordering a replacement board?

Ralph Garnett 
VA6RHG
Node 1188

Re: Node Update/Upgrade

k9dc
 

Mick,

DaveC used to do that with early generations of his embedded node, years ago when flash was very expensive. But with improvements in high availability (reliable) flash, he no longer does that. If you equip the Pi with high reliable flash (or SSD) you should be fine. Look for SLC (single level cell) flash. It sometimes is called ”Industrial Grade” and is spec’d to operate down to -40º.

Any RAM beyond 512 MB, is completely wasted if you are only running IRLP on the computer. I would skip the 4GB, save a few $$ and buy high quality flash instead. Then you have reduced the need to create a run from RAM configuration and can stay with a straight up IRLP installation.

I am still not a big fan of the Raspberry Pi for locations where reliability is very important, such as repeater sites with difficult physical access. But the Pi4 is way better than earlier models and is actually pretty impressive from a pure performance perspective. Solid 5V power and cabling is very critical.

-k9dc

On Nov 30, 2019, at 22:44, Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:

Hello Group,

While I am thinking about updating my node software, I am also thinking of upgrading my hardware. With the new Raspberry Pi4 that has 4 gigs of ram, I am wondering . . . Without a whole lot of trouble, can it be set up to copy the whole IRLP program (and OS) to ram on start up and then just copy the files that have been changed back to the SD card before shut down? Probably a good idea to copy the log files to the SD card on a regular basis while it running just to keep from losing them. There may be some other files that need saved as well, but not sure which ones they would be. Just trying to move operations away from running on the SD card so much.

Mick - W7CAT
Node 3464

Node Update/Upgrade

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Group,

While I am thinking about updating my node software, I am also thinking of upgrading my hardware. With the new Raspberry Pi4 that has 4 gigs of ram, I am wondering  . . . Without a whole lot of trouble, can it be set up to copy the whole IRLP program (and OS) to ram on start up and then just copy the files that have been changed back to the SD card before shut down? Probably a good idea to copy the log files to the SD card on a regular basis while it running just to keep from losing them. There may be some other files that need saved as well, but not sure which ones they would be. Just trying to move operations away from running on the SD card so much.

Mick - W7CAT
Node 3464

--

Re: WAV file audio

Nosey Nick VA3NNW
 

David Cameron - IRLP wrote:
With the advent of Pi-based systems, there is not a real reason not to
upgrade to something newer. I imagine with the cost of electricity,
you will recoup your up front cost in a matter of a year or two.
I thought this would be fun to calculate, kinda back-of-envelope but
with citations...

Raspi power consumption depends slightly on what model you're using and
how hard you're working it, but it's never eating TOO much CPU, IRLP is
mostly idle with occasional laid-back I/O.

http://www.irlp.net/pi/ says it supports "Raspberry Pi (models B and
B+), Pi2, and now [...] Pi3", but the ordering page has a Pi4 one, and I
happen to know it also works fine on a Pi Zero, but
https://magpi.raspberrypi.org/articles/raspberry-pi-3bplus-specs-benchmarks
and https://www.raspberrypi.org/documentation/faqs/#pi-power tend to
agree fairly well:

Power used:
Best case about 1.5W  (except honestly, only 0.75W for the pi zero?
Wow!  :-O )
Worst case about 3W

Compared with (say)
https://en.wikipedia.org/wiki/List_of_CPU_power_dissipation_figures

1st-gen Pentium 15W
Pentium 3 more like 27W
Pentium 4 more like 60-75W
Some are much MUCH worse, but I doubt anyone is running IRLP on a
dedicated 4-socket 8-core 3GHz server or anything.

However the above is ONLY THE CPU not the rest of the PC, so
http://www.buildc-omputers.net/power-consumption-of-pc-components.html
Low-end Motherboard 25 to 40W
RAM 2-5W
Assume you have no GFX card
HDD, old "spinning rust" one: 1-9W
Fans 1-6W ea
50-80% efficient PSU...

Tell you watt ('scuse the pun) let's just go with
http://www.buildcomputers.net/pc-power-requirements.html
Best case 117W, maybe you also already optimised by removing the GFX and
CD/DVD drive to bring down to 90W
Worst-case let's borrow their mid-range 278W

So the DIFFERENCE between your complete rpi system vs your old PC:
Best-case 278W-1.5W = approx 275W saving
Worst-case 90W-2.5W = 87.5W saving

Hours in a year: 8760 to 8784 for leap years
So best-case saving 275W * 8784hrs = 2415.6kWhr
worst-case only 87.5W * 8760hrs = 766.5kWhr saved

Home energy cost from
https://fusiontables.googleusercontent.com/embedviz?viz=MAP&q=select+col0+from+1qWveLELIJJjrpot_Qq7DTdv-zSLVYASbwHurDMs&h=false&lat=45.3216740792336&lng=-81.6543125&z=3&t=1&l=col0
Best case about 8c / kwH
Worst case about 22.2c / kwH

So best-case saving 2415.6kWhr @ 22.2c = $536/yr
Worst-case saving "only" 766.5kWhr @ 8c = $61.32/yr
Note that these are nearly an order of magnitude, depending on what
you're replacing, what with, ans where you live!

RRP of a Pi from https://en.wikipedia.org/wiki/Raspberry_Pi or
https://thepihut.com/

Pi Zero $4 but realistically you want the Pi Zero W $13 or with
pre-soldered header $17
Pi Zero W + sdcard + PSU + case + HDMI adapter $30
Pi 3 bare $20
Pi 4 + sdcard + PSU + case + HDMI cable $63
All the above assume you already have an IRLP board and are happy to
make the very simple 3.3V mod and follow the instructions to install
raspbian and the PIRLP software. Add $5-$10 for a USB sound card.
Up to http://www.irlp.net/order.html $350 for the fully assembled
ready-to-go pirlp node with brand new board, all OS+software etc
ready-to-go.

Let's say best-case is you're buying the pi zero + case + PSU + sdcard +
$5 USB sound-card and doing ALL the work yourself, including modding an
existing irlp board, to replace the hungriest PC above, somewhere with
expensive electricity. $35 spent to save $536/yr - pays for itself in
approximately 24 days.

Worst-case, paying for the fully-built $350 pirlp to replace a low-end
further-optimised 90W PC somewhere with cheap 8c electricity... $350 to
save $61.32/yr, about 5.7yrs to pay for itself.

Realistically, you're somewhere in the middle of each, say, 165W saved,
somewhere that charges 17c/kWhr, saving about $240/yr
... Which would pay for a $63 "DIY pi 4" pirlp upgrade in just over 3
months, or a full brand new $350 plug-n-go PIRLP from David in less than
1.5 yrs

Not to mention the noise saving, and the reduced fire risk, and not
having to worry about fan failures, and knowing that if anything DOES go
wrong, you can replace a pi with a pi for $20-$30, swap an sdcard for
less than $10, and not have to struggle to find an olde PC that still
has a parallel port in 2020.

Thanks David!   :-)

--
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer; sig@...
We have enough youth, how about a fountain of SMART?

Re: Loss of Announcements - Nodes 4480, 4490 & 4677

Nosey Nick VA3NNW
 

David Cameron - IRLP wrote:
Yes, but the old version if sox doesn't have a version flag....
HAH! That's kinda hilarious, but you could still do...

SOXVER=$(sox --version) 2>/dev/null
case "$SOXVER" in
  "") sox --options-for-versionless-sox ;;
  *v14.*) sox --some-newer-behaviour-here ;;
  *v15.*) sox --do-you-wanna-guess-at-future-behaviour-too? ;;
  *) echo "Don't know what to do with $VER" ; exit 9 ;;
esac

Nick CA3NNW

--
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer; sig@...
Speak softly and carry a +6 two-handed sword.

Re: Loss of Announcements - Nodes 4480, 4490 & 4677

David Cameron - IRLP
 

Yes, but the old version if sox doesn't have a version flag....

It really is not an easy fix either way. 

Dave

-------- Original message --------
From: Nosey Nick VA3NNW <irlp@...>
Date: 11/30/19 1:09 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Loss of Announcements - Nodes 4480, 4490 & 4677

David Cameron - IRLP wrote:
> I have made a new update to wavplay to cover the "old" style embedded
> nodes that run slackware.
> The problem is now I am using an OS detection routine to determine
> (hopefully) which version of sox will properly create the audio files.

You don't technically care about the *OS Version* though, do you? You
care about the *SOX version*, so perhaps you would prefer to do
something safer like...

SOXVER=$(sox --version) # ...
case "$SOXVER" in
  *v12.*) sox --how-old-do-you-need-to-go? ;;
  *v13.*) sox --some-old-behaviour-here ;;
  *v14.*) sox --some-newer-behaviour-here ;;
  *c15.*) sox --do-you-wanna-guess-at-future-behaviour-too? ;;
  *) echo "Don't know what to do with $VER" ; exit 9 ;;
esac

Yes, BASH has case statements! ... or do you need to support REALLY
REALLY old versions of BASH too?    :-O

Nick VA3NNW

--
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer;    sig@...
If you can stay in love for more than two years, you're on something.




Re: Loss of Announcements - Nodes 4480, 4490 & 4677

Nosey Nick VA3NNW
 

David Cameron - IRLP wrote:
I have made a new update to wavplay to cover the "old" style embedded
nodes that run slackware.
The problem is now I am using an OS detection routine to determine
(hopefully) which version of sox will properly create the audio files.
You don't technically care about the *OS Version* though, do you? You
care about the *SOX version*, so perhaps you would prefer to do
something safer like...

SOXVER=$(sox --version) # ...
case "$SOXVER" in
  *v12.*) sox --how-old-do-you-need-to-go? ;;
  *v13.*) sox --some-old-behaviour-here ;;
  *v14.*) sox --some-newer-behaviour-here ;;
  *c15.*) sox --do-you-wanna-guess-at-future-behaviour-too? ;;
  *) echo "Don't know what to do with $VER" ; exit 9 ;;
esac

Yes, BASH has case statements! ... or do you need to support REALLY
REALLY old versions of BASH too?    :-O

Nick VA3NNW

--
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer; sig@...
If you can stay in love for more than two years, you're on something.

Re: Can't login to Terminal

Don DeGregori
 

I forwarded your email to him. When he replies, I'll get him take picture of screen and ship it to you.
I thought too that would be a strange change to make.

Don

Re: Loss of Announcements - Nodes 4480, 4490 & 4677

David Cameron - IRLP
 

Yes, you either need to reboot, or wait 24 hours since the last update. If you're in North America it should happen sometime overnight.

-------- Original message --------
From: James Hall <thecoldduck@...>
Date: 11/29/19 4:43 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Loss of Announcements - Nodes 4480, 4490 & 4677

Is there anything I need to do such as reboot?  So far no change on 3024,3212.
Jim
WH7CD

created with care by Cold Duck


> On Nov 29, 2019, at 12:32 PM, David Cameron - IRLP <dcameron@...> wrote:
>
> I have made a new update to wavplay to cover the "old" style embedded nodes that run slackware.
>
> The problem is now I am using an OS detection routine to determine (hopefully) which version of sox will properly create the audio files. The issue is the "joining of files" to make the audio congruent needs "sox", and the new version of sox do not use the same arguments as the old. Up until Debian 9, they would allow them and call them deprecated, but now on Debian 10 they throw an error with the latest version of sox.
>
> Dave Cameron
>
>
>> On 2019-11-28 12:32, James Hall wrote:
>> Follow up on my last email. I had just arrived in Hawaii. I have since
>> tested this embedded node. It acts same way. Only connect/disconnect
>> announcements are gone for IRLP only. EchoLink announcements are ok.
>> Custom CW id on IRLP announcements works still. So that’s both my
>> nodes stopped working last Friday.  I ran ... rc. Irlp and every thing
>> rebooted but same loss of connect/disconnect announcements.
>> 3212
>> 3024
>> WH7CD
>> Jim
>
>
>
>
>



Re: Loss of Announcements - Nodes 4480, 4490 & 4677

James Hall
 

Is there anything I need to do such as reboot? So far no change on 3024,3212.
Jim
WH7CD

created with care by Cold Duck

On Nov 29, 2019, at 12:32 PM, David Cameron - IRLP <dcameron@...> wrote:

I have made a new update to wavplay to cover the "old" style embedded nodes that run slackware.

The problem is now I am using an OS detection routine to determine (hopefully) which version of sox will properly create the audio files. The issue is the "joining of files" to make the audio congruent needs "sox", and the new version of sox do not use the same arguments as the old. Up until Debian 9, they would allow them and call them deprecated, but now on Debian 10 they throw an error with the latest version of sox.

Dave Cameron


On 2019-11-28 12:32, James Hall wrote:
Follow up on my last email. I had just arrived in Hawaii. I have since
tested this embedded node. It acts same way. Only connect/disconnect
announcements are gone for IRLP only. EchoLink announcements are ok.
Custom CW id on IRLP announcements works still. So that’s both my
nodes stopped working last Friday. I ran ... rc. Irlp and every thing
rebooted but same loss of connect/disconnect announcements.
3212
3024
WH7CD
Jim



Re: Loss of Announcements - Nodes 4480, 4490 & 4677

David Cameron - IRLP
 

I have made a new update to wavplay to cover the "old" style embedded nodes that run slackware.

The problem is now I am using an OS detection routine to determine (hopefully) which version of sox will properly create the audio files. The issue is the "joining of files" to make the audio congruent needs "sox", and the new version of sox do not use the same arguments as the old. Up until Debian 9, they would allow them and call them deprecated, but now on Debian 10 they throw an error with the latest version of sox.

Dave Cameron

On 2019-11-28 12:32, James Hall wrote:
Follow up on my last email. I had just arrived in Hawaii. I have since
tested this embedded node. It acts same way. Only connect/disconnect
announcements are gone for IRLP only. EchoLink announcements are ok.
Custom CW id on IRLP announcements works still. So that’s both my
nodes stopped working last Friday. I ran ... rc. Irlp and every thing
rebooted but same loss of connect/disconnect announcements.
3212
3024
WH7CD
Jim

Re: Can't login to Terminal

David Cameron - IRLP
 

There is nothing blocking commands. I am sure he is getting more than just the prompt back.

Can he take a picture of the screen and attach it? Are you sure he is actually logging in, and has the password correct? The node number appears in the login prompt also.

David Cameron

On 2019-11-29 11:37, Don DeGregori wrote:
I have a friend with the newest assembled PiRLP4 Node. He wants to
check ifconfig on the Terminal to find his local inet IP address. He
thinks the ports are not port forwarded properly.
I told him to reboot to get the login prompt. He does and sees login.
He types root. For password, he puts in his changed password. He sees
his node number within the prompt. I ask him to type ifconfig
(Return). He gets the prompt back. I said to try ls command. He gets
prompt back. I believe he is in the IRLP directory which doesn't
allow Linux commands?
I have an old old Red Hat legacy box which works fine. So I'm not sure
what the newest software has in it.
W6RWN 3146
Links:
------
[1] https://irlp.groups.io/g/IRLP/message/76330
[2] https://groups.io/mt/64396878/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

Re: Can't login to Terminal

k9dc
 


Who is your friend and what is his node number?
-k9dc


On Nov 29, 2019, at 14:37, Don DeGregori <don1mh@...> wrote:

I have a friend with the newest assembled PiRLP4 Node. He wants to check ifconfig on the Terminal to find his local inet IP address. He thinks the ports are not port forwarded properly.

I told him to reboot to get the login prompt. He does and sees login. He types root. For password, he puts in his changed password. He sees his node number within the prompt. I ask him to type ifconfig (Return). He gets the prompt back. I said to try ls command. He gets prompt back. I believe he is in the IRLP directory which doesn't  allow Linux commands?

I have an old old Red Hat legacy box which works fine. So I'm not sure what the newest software has in it.

W6RWN   3146

Can't login to Terminal

Don DeGregori
 

I have a friend with the newest assembled PiRLP4 Node. He wants to check ifconfig on the Terminal to find his local inet IP address. He thinks the ports are not port forwarded properly.

I told him to reboot to get the login prompt. He does and sees login. He types root. For password, he puts in his changed password. He sees his node number within the prompt. I ask him to type ifconfig (Return). He gets the prompt back. I said to try ls command. He gets prompt back. I believe he is in the IRLP directory which doesn't  allow Linux commands?

I have an old old Red Hat legacy box which works fine. So I'm not sure what the newest software has in it.

W6RWN   3146