Date   

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

Elden AI7HL (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 AI7HL (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 AI7HL (Node 7006)
 

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

What is your node number?
-k9dc 
 
Node 7006


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

Elden AI7HL (Node 7006)
 

I eventually got the error message that asked me to email installs@.... Which I did. And Mr Cameron got me fixed up.

I'm puzzled though. He said he showed my Allstar node reporting my IRLP node number long after I completely removed and disabled IRLP from that box. 

However, I do run an Allstar node and an IRLP node from the same public IP address. That shouldn't be a problem should it?


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

Dave K9DC
 


What is your node number?
-k9dc 


On Oct 21, 2020, at 21:59, Elden W7LDN <w7ldn@...> wrote:

I pulled out my IRLP node and plugged it in tonight. Can't connect to anything. I get the error "An error has occurred. The connection could not be authenticated." when I try.

This was working when I put it away a few months ago. Anyone have an idea?

Do I need to wait 24 hours after plugging this in before I can connect?


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

Elden AI7HL (Node 7006)
 

Before anyone asks... I will offer the following info.

My key was restored by K9DC back in January. This was after I learned that using non-IRLP software was not allowed and discovered that my key had been revoked.

I did learn my lesson and removed the IRLP configuration from my Allstar node at that time. Since then I have not connected to IRLP using any means other than my PiRLP node that I purchased from the IRLP folks.


------ Original Message ------
From: "Elden W7LDN" <w7ldn@...>
Sent: 10/21/2020 7:10:14 PM
Subject: [IRLP] Error message... connection could not be authenticated #piirlp

I pulled out my IRLP node and plugged it in tonight. Can't connect to anything. I get the error "An error has occurred. The connection could not be authenticated." when I try.

This was working when I put it away a few months ago. Anyone have an idea?

Do I need to wait 24 hours after plugging this in before I can connect?


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

Teton Amateur Radio Repeater Association (TARRA)
 

The first thing you are going to get asked, is for a node number.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Elden W7LDN
To: IRLP@irlp.groups.io
Sent: Wednesday, October 21, 2020 08:10:14 PM
Subject: [IRLP] Error message... connection could not be authenticated #piirlp

> I pulled out my IRLP node and plugged it in tonight. Can't connect to anything. I get the error "An error has occurred. The connection could not be authenticated." when I try.
>
> This was working when I put it away a few months ago. Anyone have an idea?
>
> Do I need to wait 24 hours after plugging this in before I can connect?
>
>
>
>
>
>
--


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

Elden AI7HL (Node 7006)
 

I pulled out my IRLP node and plugged it in tonight. Can't connect to anything. I get the error "An error has occurred. The connection could not be authenticated." when I try.

This was working when I put it away a few months ago. Anyone have an idea?

Do I need to wait 24 hours after plugging this in before I can connect?


Re: How Low Can We Go

 

On 20/10/20 1: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!
You will be limited to using the GSM codec.  This will be good for
node-node connections and only some reflectors (reflectors channels are
set to use a specific codec).

This is what was done in the dialup days.  There's still a number of GSM
reflector channels (including almost all of those linked to Echolink
conferences) available.

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


Re: How Low Can We Go

Teton Amateur Radio Repeater Association (TARRA)
 

The simplest thing is to have a couple of phones to test with for signal. Far more common to use a phone to check things with. I know and understand the data device, I have one for Verizon at one of my sites where the IRLP node is now. Trying to get away from Verizon because of their poor network. Rather unlikely to have AT&T and even much more unlikely to have Sprint (T-Mobile) available at this site.

Mick - W7CAT

Node 3464


Re: How Low Can We Go

Bob DeMattia, K1IW
 

Really hard to tell what you are responding to.

Are you saying you have no 4G cell coverage by either AT&T or Sprint at the site?
Freedompop uses the AT&T network,  Tello uses Sprint.

You don't need a phone - the Netgear devices are data-only 4G devices.


-Bob


On Tue, Oct 20, 2020 at 12:38 PM Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:

Once again, probably not going to have service at the site. Not many services out here in the wild, wild, west.

Mick - W7CAT

Node 3464


Re: Delivery failure

Teton Amateur Radio Repeater Association (TARRA)
 

I sent an email to groups.io support and it failed. I may be done with groups.io

Mick - W7CAT

Node 3464


Re: How Low Can We Go

Teton Amateur Radio Repeater Association (TARRA)
 

Once again, probably not going to have service at the site. Not many services out here in the wild, wild, west.

Mick - W7CAT

Node 3464


Re: How Low Can We Go

Teton Amateur Radio Repeater Association (TARRA)
 

I looked at both of those. When I say "remote" I do mean remote. I doubt that either of those companies would have anything at the site. I wouldn't know without being able to test at the site. Then I would need phones that would work with those services. Right now probably snowed out of the site until July.

Mick - W7CAT

Node 3464


Re: How Low Can We Go

Teton Amateur Radio Repeater Association (TARRA)
 

Using it for the link. No RF link at the site.

Mick - W7CAT
Node 3464

841 - 860 of 78750