Date   

Re: how do disable or uninstall IRLPvCON ?

David Cameron - IRLP
 

I would start by just turning off the web server.

systemctl disable apache2

You can also try to rename the web folders, so others can not use them. I am not sure where the folders are on your specific system, but you can type

locate irlpvcon
locate irlpvmon

It will show you where the folders are. Then you can use the mv command to "move" the folder to a new name.

Dave Cameron

On 2020-10-24 8:14 a.m., kd1yh wrote:
Need to  disable or uninstall.IRLPvCON
A comment is>>
The problem is the polling that IRLPvCON does of the parallel port somehow creates a race condition with the same polling being done by the DTMF process.
Does anybody have a fix?
Paul Upham
KD1YH
node 8581 , 4651, 8433


Re: Backup for restore help

James Hertel
 

OR add... ./home/irlp/scripts/backup_for_reinstall

On 10/24/2020 8:55 AM, Darin Lehnert wrote:
Try this.....
As root
/home/irlp/scripts/backup_for_reinstall

On Sat, Oct 24, 2020 at 8:36 AM Jim Harris <radiove1rb@...> wrote:
By the way it is running Centos 5.11

Jim VE1RB
Node 2952
(I see I had it wrong on the first email)

On Sat, Oct 24, 2020 at 12:31 PM Jim Harris <radiove1rb@...> wrote:
Our radio club has an older node computer and we are going to replace it. I sat down at the console and typed in the command from the Wiki

/home/irlp/scripts/backup_for_install

and I get the following response

No such file or directory

I run Linux on my computers so it is not real foreign to me. So what am I doing wrong?

73 and thanks,
Jim
VE1RB
Node 2925


Re: Backup for restore help

Darin Lehnert
 

Try this.....
As root
/home/irlp/scripts/backup_for_reinstall

On Sat, Oct 24, 2020 at 8:36 AM Jim Harris <radiove1rb@...> wrote:
By the way it is running Centos 5.11

Jim VE1RB
Node 2952
(I see I had it wrong on the first email)

On Sat, Oct 24, 2020 at 12:31 PM Jim Harris <radiove1rb@...> wrote:
Our radio club has an older node computer and we are going to replace it. I sat down at the console and typed in the command from the Wiki

/home/irlp/scripts/backup_for_install

and I get the following response

No such file or directory

I run Linux on my computers so it is not real foreign to me. So what am I doing wrong?

73 and thanks,
Jim
VE1RB
Node 2925


Re: Backup for restore help

Jim Harris
 

By the way it is running Centos 5.11

Jim VE1RB
Node 2952
(I see I had it wrong on the first email)

On Sat, Oct 24, 2020 at 12:31 PM Jim Harris <radiove1rb@...> wrote:
Our radio club has an older node computer and we are going to replace it. I sat down at the console and typed in the command from the Wiki

/home/irlp/scripts/backup_for_install

and I get the following response

No such file or directory

I run Linux on my computers so it is not real foreign to me. So what am I doing wrong?

73 and thanks,
Jim
VE1RB
Node 2925


Backup for restore help

Jim Harris
 

Our radio club has an older node computer and we are going to replace it. I sat down at the console and typed in the command from the Wiki

/home/irlp/scripts/backup_for_install

and I get the following response

No such file or directory

I run Linux on my computers so it is not real foreign to me. So what am I doing wrong?

73 and thanks,
Jim
VE1RB
Node 2925


how do disable or uninstall IRLPvCON ?

kd1yh
 

Need to  disable or uninstall.IRLPvCON
 
A comment is>>
 
The problem is the polling that IRLPvCON does of the parallel port somehow creates a race condition with the same polling being done by the DTMF process.
 
Does anybody have a fix?
 
Paul Upham
KD1YH
node 8581 , 4651, 8433
 
 


Re: How Low Can We Go

Ramon Gandia
 

On 10/19/20 6:52 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:
Hello Group,
I am wondering how low we can go for an network speed connection. Still trying to figure out a connection for a mountain top. Wondering if a 56K connection is still going to be fast enough to work? Just trying what I can to make things work. Yes, there is internet up there, but the company wants $80 a month for us to have a connection. I consider that absurd!
Mick - W7CAT
Node 3464

80.00 a month?!? Sign me up! Mine is $429.00 a month. And I got TWO
accounts for internet, and 16 cell lines. Ouch.

Ramon AL7X


Re: How Low Can We Go

kd1yh
 

Is there a schematic on how all this goes together?
 
I think it is NetGear 340u  plugs into the Cradlepoint MBR1200B router and then a lan to computer, is that correct?
And you get a sim card from FreedomPop etc. ?
 
Paul Upham
KD1YH node 4651
 

From: Bob DeMattia, K1IW
Sent: Tuesday, October 20, 2020 9:04 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] How Low Can We Go
 
On eBay, you can purchase a Cradlepoint MBR1200B router for about $100 on eBay, and either a NetGear 340u or 341u
for about $30.    You plug the Netgear into the USB port of the Cradlepoint, then use either a wired or wireless connection
to the router.
 
The 340 works with FreedomPop, which will give you a 4G connection 200MB/month for $0,  the 341 works with Tello,
which will give you 500MB/month for $5.  Other plans with more data are available. 
 
My club is doing this at six remote sites - our usage is easily under 150MB a month at each site.
 
 
Bob - K1IW
 
 
 
 
On Tue, Oct 20, 2020 at 7:55 AM Rich Ball <wa2zpx@...> wrote:
You can always go the other route, and put the node somewhere else and link it to the site on a remote base port on the controller. Been doing that for years...
 
Rich, WA2ZPX
Node 4130

---------- Original Message ----------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@...>
To: IRLP@irlp.groups.io
Subject: [IRLP] How Low Can We Go
Date: Mon, 19 Oct 2020 19:52:21 -0700

Hello Group,

I am wondering how low we can go for an network speed connection. Still trying to figure out a connection for a mountain top. Wondering if a 56K connection is still going to be fast enough to work? Just trying what I can to make things work. Yes, there is internet up there, but the company wants $80 a month for us to have a connection. I consider that absurd!

Mick - W7CAT
Node 3464



____________________________________________________________

Top News - Sponsored By Newser


Re: Error message... connection could not be authenticated #piirlp

Elden W7LDN (Node 7006)
 
Edited

Fair enough. I guess I realized that when you asked for my node number callsign. Because I know you are one of the officials. My callsign is shown on every message I post (W7LDN if anyone is still wondering... node 7006). My apologies for not providing the info up front. And thanks to all of you for the suggestions.

At any rate, those reading will know the problem was solved by Dave Cameron almost instantly. He graciously restored my key. I had no idea that there were any remnants of my IRLP config on my Allstar node. Seriously, I deleted the entire IRLP binaries and config directory. And I disabled the loading of the module. So I don't see how it could happen.

At any rate. I have spent the night rebuilding my Allstar node from a fresh image. So the IRLP system should no longer be hearing anything from it.

While I'm on a roll... naturally I don't like that my key was revoked (twice). But I can understand. I am however quite unhappy with the hamvoip people for making it seem like their IRLP feature was legit. I know that way back, they removed the IRLP code from their distribution at "your" request. When they added it back, I figure there had been an agreement reached. I think it's very misleading on their part. And not fair to their users.

Anyway, thanks to everyone for your help and especially K9DC and Dave Cameron who restored my key when I needed it.



On Thu, Oct 22, 2020 at 09:12 PM, k9dc wrote:
This is incorrect. There is no direct relationship between a call sign and node number. Node numbers are unique, callsigns are not. IOW, every node has a callsign. But callsigns can have many nodes, in some cases dozens.

-k9dc


On Oct 22, 2020, at 23:08, Elden W7LDN <w7ldn@...> wrote:

Well my thinking was... anyone official with IRLP would easily be able to determine my node number by my callsign. After all, they have records do they not? I also figured the folks without access to that info, didn't really need to know anyway.

------ Original Message ------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@...>
To: IRLP@irlp.groups.io
Sent: 10/22/2020 5:31:06 PM
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

I thought you guys knew by now that no one has a name, call sign or node number any more. Oh wait, maybe they do, we are just supposed to know all that (some how).

Mick - W7CAT
Node 3464


Re: Error message... connection could not be authenticated #piirlp

Dave K9DC
 

This is incorrect. There is no direct relationship between a call sign and node number. Node numbers are unique, callsigns are not. IOW, every node has a callsign. But callsigns can have many nodes, in some cases dozens.

-k9dc

On Oct 22, 2020, at 23:08, Elden W7LDN <w7ldn@moondog.org> wrote:

Well my thinking was... anyone official with IRLP would easily be able to determine my node number by my callsign. After all, they have records do they not? I also figured the folks without access to that info, didn't really need to know anyway.

------ Original Message ------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@wyocat.com>
To: IRLP@irlp.groups.io
Sent: 10/22/2020 5:31:06 PM
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

I thought you guys knew by now that no one has a name, call sign or node number any more. Oh wait, maybe they do, we are just supposed to know all that (some how).

Mick - W7CAT
Node 3464


Re: Error message... connection could not be authenticated #piirlp

Dave Schultheis
 

Elden LDN wrote:


Well my thinking was... anyone official with IRLP would easily be able to determine my node number by my callsign. After all, they have records do they not? I also figured the folks without access to that info, didn't really need to know anyway.

It has become the tradition of this group that if you ask a question or for some type of assistance, that you provide enough facts to give any possibly repliers enough information for them to provide a good answer to your question.

And, using the theory of making it easy for the other guy, it's been tradition to sign your message with your name, call sign and node number, partly to assure that you are a legitimate user and partly so that other users can help you better, in some cases.

You've done some of that and it resulted in a suggestion from a user; I hope you can do the rest of it. Kinda like this ...

--

73 de Dave WB6KHP
San Jose
IRLP 3246 (currently down due to access restrictions)


Re: Error message... connection could not be authenticated #piirlp

Teton Amateur Radio Repeater Association (TARRA)
 

I, and I don't believe Phil, were taking aim at you exclusively. Any more there are a lot of people who don't list a name and call sign (and node number) on posts to this group and many other groups.

There are a lot of people in this group who try to help others. Pretty much the reason for this group. So having the information out there for the whole group is still important. If the group shouldn't know, then quite simply, don't post it to the group.

Even after taking offense to this, you still don't sign with a name, call sign, and node number.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Elden W7LDN
To: IRLP@irlp.groups.io
Sent: Thursday, October 22, 2020 09:08:46 PM
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

> Well my thinking was... anyone official with IRLP would easily be able
> to determine my node number by my callsign. After all, they have records
> do they not? I also figured the folks without access to that info,
> didn't really need to know anyway.
>
> ------ Original Message ------
> From: "Teton Amateur Radio Repeater Association (TARRA)"
>
> To: IRLP@irlp.groups.io
> Sent: 10/22/2020 5:31:06 PM
> Subject: Re: [IRLP] Error message... connection could not be
> authenticated #piirlp
>
> >I thought you guys knew by now that no one has a name, call sign or
> >node number any more. Oh wait, maybe they do, we are just supposed to
> >know all that (some how).
> >
> >Mick - W7CAT
> >Node 3464
> >
> >----- Original Message -----
> >From: Phil Zocco
> >To: IRLP@irlp.groups.io
> >Sent: Thursday, October 22, 2020 04:22:44 PM
> >Subject: Re: [IRLP] Error message... connection could not be
> >authenticated #piirlp
> >
> > > To K9DC.
> > >
> > >
> > >
> > > Sorry, Dave. I see you already got the node number. Two of your
> >emails went to my junk email file hence I missed that one email.
> > >
> > >
> > >
> > > You would think after all of these years folks here, when writing an
> >email, would add their name and node number at least.
> > >
> > >
> > >
> > > The things they teach us in elementary school should still be there.
> > >
> > >
> > >
> > > Anyway, hello from Horseshoe Curve and Altoona, PA.
> > >
> > >
> > >
> > > 73,
> > >
> > >
> > >
> > > Phil N1BOW
> > >
> > >
> > >
> > > From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of
> >Phil Zocco
> > > Sent: Thursday, October 22, 2020 6:17 PM
> > > To: IRLP@irlp.groups.io
> > > Subject: Re: [IRLP] Error message... connection could not be
> >authenticated #piirlp
> > >
> > >
> > >
> > > It’s node number 7006 per status.irlp.net
> > >
> > >
> > >
> > > You’re welcome. I gotta tell ya…….
> > >
> > >
> > >
> > > 73,
> > >
> > >
> > >
> > > Phil N1BOW
> > >
> > > Node 5960
> > >
> > > AMT MP 113.6
> > >
> > > Niantic, CT USA Earth
> > >
> > >
> > >
> > > From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of
> >Elden W7LDN
> > > Sent: Thursday, October 22, 2020 5:13 PM
> > > To: IRLP@irlp.groups.io
> > > Subject: Re: [IRLP] Error message... connection could not be
> >authenticated #piirlp
> > >
> > >
> > >
> > > Thanks for trying to help Ian. I was able to get it worked out. Turns
> >out my Allstar node must have had remnants of my IRLP configuration on
> >it that was phoning home. I had thought I wiped it all off, but I must
> >have missed something. Hence my key was revoked. No worries though.
> >Things are back and running now. And I'm not even sure I will be doing
> >Allstar again at this point. I appreciate you pointing out these
> >scripts. I did find a couple of those last night and ran them. Very
> >useful.
> > >
> > > On Thu, Oct 22, 2020 at 11:50 AM, zl1vfo wrote:
> > >
> > > Have you tried running the troubleshooting script? From
> >http://www.irlp.net/ts.html ...
> > >
> > > Log in and switch to user repeater
> > > su - repeater
> > >
> > > Now make sure you have the latest files on your system by running
> >./scripts/update files
> > >
> > > Now run the troubleshooting script ./scripts/troubleshoot-irlp
> > >
> > > From what little I can see from this end, your ports 15425 and 15426
> >are forwarded into your IRLP node correctly, however the
> >troubleshooting script should tell you somewhat more. ..and the status
> >page shows that your node has made contact with the IRLP servers..
> >http://status.irlp.net/index.php?PSTART=11 &nodeid=7006
> > >
> > > -Ian ZL1VFO Node 6950, 6611
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >--
> >Untitled Document
> >
> >
>
>
>
>
>
>
--


Re: Error message... connection could not be authenticated #piirlp

Elden W7LDN (Node 7006)
 

Well my thinking was... anyone official with IRLP would easily be able to determine my node number by my callsign. After all, they have records do they not? I also figured the folks without access to that info, didn't really need to know anyway. 

------ Original Message ------
From: "Teton Amateur Radio Repeater Association (TARRA)" <tarra@...>
Sent: 10/22/2020 5:31:06 PM
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

I thought you guys knew by now that no one has a name, call sign or node number any more. Oh wait, maybe they do, we are just supposed to know all that (some how).

Mick - W7CAT
Node 3464

----- Original Message -----
From: Phil Zocco <n1bow@...>
To: IRLP@irlp.groups.io
Sent: Thursday, October 22, 2020 04:22:44 PM
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

> To K9DC.
>
>
>
> Sorry, Dave. I see you already got the node number. Two of your emails went to my junk email file hence I missed that one email.
>
>
>
> You would think after all of these years folks here, when writing an email, would add their name and node number at least.
>
>
>
> The things they teach us in elementary school should still be there.
>
>
>
> Anyway, hello from Horseshoe Curve and Altoona, PA.
>
>
>
> 73,
>
>
>
> Phil N1BOW
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Phil Zocco
> Sent: Thursday, October 22, 2020 6:17 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp
>
>
>
> It’s node number 7006 per status.irlp.net
>
>
>
> You’re welcome. I gotta tell ya…….
>
>
>
> 73,
>
>
>
> Phil N1BOW
>
> Node 5960
>
> AMT MP 113.6
>
> Niantic, CT USA Earth
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Elden W7LDN
> Sent: Thursday, October 22, 2020 5:13 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp
>
>
>
> Thanks for trying to help Ian. I was able to get it worked out. Turns out my Allstar node must have had remnants of my IRLP configuration on it that was phoning home. I had thought I wiped it all off, but I must have missed something. Hence my key was revoked. No worries though. Things are back and running now. And I'm not even sure I will be doing Allstar again at this point. I appreciate you pointing out these scripts. I did find a couple of those last night and ran them. Very useful.
>
> On Thu, Oct 22, 2020 at 11:50 AM, zl1vfo wrote:
>
> Have you tried running the troubleshooting script? From http://www.irlp.net/ts.html ...
>
> Log in and switch to user repeater
> su - repeater
>
> Now make sure you have the latest files on your system by running ./scripts/update files
>
> Now run the troubleshooting script ./scripts/troubleshoot-irlp
>
> From what little I can see from this end, your ports 15425 and 15426 are forwarded into your IRLP node correctly, however the troubleshooting script should tell you somewhat more. ..and the status page shows that your node has made contact with the IRLP servers.. http://status.irlp.net/index.php?PSTART=11 &nodeid=7006
>
> -Ian ZL1VFO Node 6950, 6611
>
>
>
>
>
>
>
>
>
--


Re: Error message... connection could not be authenticated #piirlp

Teton Amateur Radio Repeater Association (TARRA)
 

I thought you guys knew by now that no one has a name, call sign or node number any more. Oh wait, maybe they do, we are just supposed to know all that (some how).

Mick - W7CAT
Node 3464

----- Original Message -----
From: Phil Zocco
To: IRLP@irlp.groups.io
Sent: Thursday, October 22, 2020 04:22:44 PM
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

> To K9DC.
>
>
>
> Sorry, Dave. I see you already got the node number. Two of your emails went to my junk email file hence I missed that one email.
>
>
>
> You would think after all of these years folks here, when writing an email, would add their name and node number at least.
>
>
>
> The things they teach us in elementary school should still be there.
>
>
>
> Anyway, hello from Horseshoe Curve and Altoona, PA.
>
>
>
> 73,
>
>
>
> Phil N1BOW
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Phil Zocco
> Sent: Thursday, October 22, 2020 6:17 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp
>
>
>
> It’s node number 7006 per status.irlp.net
>
>
>
> You’re welcome. I gotta tell ya…….
>
>
>
> 73,
>
>
>
> Phil N1BOW
>
> Node 5960
>
> AMT MP 113.6
>
> Niantic, CT USA Earth
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Elden W7LDN
> Sent: Thursday, October 22, 2020 5:13 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp
>
>
>
> Thanks for trying to help Ian. I was able to get it worked out. Turns out my Allstar node must have had remnants of my IRLP configuration on it that was phoning home. I had thought I wiped it all off, but I must have missed something. Hence my key was revoked. No worries though. Things are back and running now. And I'm not even sure I will be doing Allstar again at this point. I appreciate you pointing out these scripts. I did find a couple of those last night and ran them. Very useful.
>
> On Thu, Oct 22, 2020 at 11:50 AM, zl1vfo wrote:
>
> Have you tried running the troubleshooting script? From http://www.irlp.net/ts.html ...
>
> Log in and switch to user repeater
> su - repeater
>
> Now make sure you have the latest files on your system by running ./scripts/update files
>
> Now run the troubleshooting script ./scripts/troubleshoot-irlp
>
> From what little I can see from this end, your ports 15425 and 15426 are forwarded into your IRLP node correctly, however the troubleshooting script should tell you somewhat more. ..and the status page shows that your node has made contact with the IRLP servers.. http://status.irlp.net/index.php?PSTART=11 &nodeid=7006
>
> -Ian ZL1VFO Node 6950, 6611
>
>
>
>
>
>
>
>
>
--


Re: Error message... connection could not be authenticated #piirlp

Phil Zocco
 

To K9DC.

 

Sorry, Dave. I see you already got the node number. Two of your emails went to my junk email file hence I missed that one email.

 

You would think after all of these years folks here, when writing an email, would add their name and node number at least.

 

The things they teach us in elementary school should still be there.

 

Anyway, hello from Horseshoe Curve and Altoona, PA.

 

73,

 

Phil N1BOW

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Phil Zocco
Sent: Thursday, October 22, 2020 6:17 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

 

It’s node number 7006 per status.irlp.net

 

You’re welcome. I gotta tell ya…….

 

73,

 

Phil N1BOW

Node 5960

AMT MP 113.6

Niantic, CT USA Earth

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Elden W7LDN
Sent: Thursday, October 22, 2020 5:13 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

 

Thanks for trying to help Ian. I was able to get it worked out. Turns out my Allstar node must have had remnants of my IRLP configuration on it that was phoning home. I had thought I wiped it all off, but I must have missed something. Hence my key was revoked. No worries though. Things are back and running now. And I'm not even sure I will be doing Allstar again at this point. I appreciate you pointing out these scripts. I did find a couple of those last night and ran them. Very useful.

On Thu, Oct 22, 2020 at 11:50 AM, zl1vfo wrote:

Have you tried running the troubleshooting script? From http://www.irlp.net/ts.html ...

Log in and switch to user repeater
su - repeater

Now make sure you have the latest files on your system by running ./scripts/update files

Now run the troubleshooting script ./scripts/troubleshoot-irlp

From what little I can see from this end, your ports 15425 and 15426 are forwarded into your IRLP node correctly, however the troubleshooting script should tell you somewhat more. ..and the status page shows that your node has made contact with the IRLP servers.. http://status.irlp.net/index.php?PSTART=11&nodeid=7006

-Ian ZL1VFO Node 6950, 6611


Re: Error message... connection could not be authenticated #piirlp

Phil Zocco
 

It’s node number 7006 per status.irlp.net

 

You’re welcome. I gotta tell ya…….

 

73,

 

Phil N1BOW

Node 5960

AMT MP 113.6

Niantic, CT USA Earth

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Elden W7LDN
Sent: Thursday, October 22, 2020 5:13 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Error message... connection could not be authenticated #piirlp

 

Thanks for trying to help Ian. I was able to get it worked out. Turns out my Allstar node must have had remnants of my IRLP configuration on it that was phoning home. I had thought I wiped it all off, but I must have missed something. Hence my key was revoked. No worries though. Things are back and running now. And I'm not even sure I will be doing Allstar again at this point. I appreciate you pointing out these scripts. I did find a couple of those last night and ran them. Very useful.

On Thu, Oct 22, 2020 at 11:50 AM, zl1vfo wrote:

Have you tried running the troubleshooting script? From http://www.irlp.net/ts.html ...

Log in and switch to user repeater
su - repeater

Now make sure you have the latest files on your system by running ./scripts/update files

Now run the troubleshooting script ./scripts/troubleshoot-irlp

From what little I can see from this end, your ports 15425 and 15426 are forwarded into your IRLP node correctly, however the troubleshooting script should tell you somewhat more. ..and the status page shows that your node has made contact with the IRLP servers.. http://status.irlp.net/index.php?PSTART=11&nodeid=7006

-Ian ZL1VFO Node 6950, 6611


Re: Error message... connection could not be authenticated #piirlp

Elden W7LDN (Node 7006)
 

Thanks for trying to help Ian. I was able to get it worked out. Turns out my Allstar node must have had remnants of my IRLP configuration on it that was phoning home. I had thought I wiped it all off, but I must have missed something. Hence my key was revoked. No worries though. Things are back and running now. And I'm not even sure I will be doing Allstar again at this point. I appreciate you pointing out these scripts. I did find a couple of those last night and ran them. Very useful.


On Thu, Oct 22, 2020 at 11:50 AM, zl1vfo wrote:

Have you tried running the troubleshooting script? From http://www.irlp.net/ts.html ...

Log in and switch to user repeater
su - repeater

Now make sure you have the latest files on your system by running ./scripts/update files

Now run the troubleshooting script ./scripts/troubleshoot-irlp

From what little I can see from this end, your ports 15425 and 15426 are forwarded into your IRLP node correctly, however the troubleshooting script should tell you somewhat more. ..and the status page shows that your node has made contact with the IRLP servers.. http://status.irlp.net/index.php?PSTART=11&nodeid=7006

-Ian ZL1VFO Node 6950, 6611


Re: Error message... connection could not be authenticated #piirlp

zl1vfo
 

Have you tried running the troubleshooting script? From http://www.irlp.net/ts.html ...

Log in and switch to user repeater
su - repeater

Now make sure you have the latest files on your system by running ./scripts/update files

Now run the troubleshooting script ./scripts/troubleshoot-irlp

From what little I can see from this end, your ports 15425 and 15426 are forwarded into your IRLP node correctly, however the troubleshooting script should tell you somewhat more. ..and the status page shows that your node has made contact with the IRLP servers.. http://status.irlp.net/index.php?PSTART=11&nodeid=7006

-Ian ZL1VFO Node 6950, 6611


remote_admin: php_lock prevented end from running

kd1yh
 

“remote_admin: php_lock prevented end from running”
 
from RA,
 
I keep getting this error and have to end from repeater login twice to get back to root.
Then I can decode xxxx and it works until “end call “
or DTMF Script: and enter xxxx and it works until I end.

 
Paul KD1YH
node 4651


Re: Error message... connection could not be authenticated #piirlp

Elden W7LDN (Node 7006)
 

On Wed, Oct 21, 2020 at 07:24 PM, k9dc wrote:

What is your node number?
-k9dc 
 
Node 7006

321 - 340 of 78242