Date   

Re: new crontab file is missing newline before EOF, can't install.

Charlie Wa2gug
 

Dave,
Thanks. I was missing the return in the custom.crons.

Fixed :-)


Charlie wa2gug
ARRL FIELD INSTRUCTOR, VE



-------- Original message --------
From David Cameron - IRLP <dcameron@...>
Date: 01/10/2020 12:25 (GMT-05:00)
To IRLP@irlp.groups.io
Cc k9dc <Dave@...>
Subject Re: [IRLP] new crontab file is missing newline before EOF, can't install.


The problem is likely any custom crontabs you have added in
/home/irlp/custom/custom.crons.

You may have made the file on a windows machine, and then moved it to
Linux. That will cause weird characters to exist in it.

Google the program dos2unix for more info on a converter you can use.

Dave Cameron
VE7LTD

On 2020-01-10 09:10, k9dc wrote:
> What file are you looking at and how are you looking at it?  It should
> just be text.
>
> 'crontab -l’ to list it; ‘crontab -e’ to edit
>
> -k9dc
>
>
>> On Jan 10, 2020, at 11:58, Charlie Wa2gug <wa2gug@...> wrote:
>>
>> Dave thanks for reply. I tried looking at the file with an editor. It
>> is unreadable.  To me it looks curopt.
>> Can it be regenerated?
>>
>>
>> Charlie wa2gug
>> ARRL FIELD INSTRUCTOR, VE
>>
>>
>>
>> -------- Original message --------
>> From k9dc <Dave@...>
>> Date: 01/10/2020 11:19 (GMT-05:00)
>> To IRLP@irlp.groups.io
>> Subject Re: [IRLP] new crontab file is missing newline before EOF,
>> can't install.
>>
>>
>>
>> Not worth re-installing over. The error message you received is pretty
>> clear what the problem is.
>>
>> > new crontab file is missing newline before EOF, can't install.
>>
>> Simply make sure the last character in the file is a NEWLINE, aka a
>> <return> or <enter>.  The crontab file must end with <return> <EOF>.
>> If there is anything other than a <return> at the end of that file, it
>> will be rejected by the OS.
>>
>> -k9dc
>>
>
>
>





Re: new crontab file is missing newline before EOF, can't install.

Charlie Wa2gug
 

I was looking at wrong file. I added the carriage return at the end of the file, saved it, tried again same error.

On 1/10/2020 12:10, k9dc wrote:
What file are you looking at and how are you looking at it?  It should just be text.

'crontab -l’ to list it; ‘crontab -e’ to edit

-k9dc
 

On Jan 10, 2020, at 11:58, Charlie Wa2gug <wa2gug@...> wrote:

Dave thanks for reply. I tried looking at the file with an editor. It is unreadable.  To me it looks curopt. 
Can it be regenerated?


Charlie wa2gug
ARRL FIELD INSTRUCTOR, VE



-------- Original message --------
From k9dc <Dave@...> 
Date: 01/10/2020 11:19 (GMT-05:00) 
To IRLP@irlp.groups.io 
Subject Re: [IRLP] new crontab file is missing newline before EOF, can't install. 



Not worth re-installing over. The error message you received is pretty clear what the problem is.

new crontab file is missing newline before EOF, can't install.
Simply make sure the last character in the file is a NEWLINE, aka a <return> or <enter>.  The crontab file must end with <return> <EOF>.  If there is anything other than a <return> at the end of that file, it will be rejected by the OS.   

-k9dc




-- 
Charles L. Alfano
WA2GUG
ARRL VE, Instructor


Re: new crontab file is missing newline before EOF, can't install.

David Cameron - IRLP
 

The problem is likely any custom crontabs you have added in /home/irlp/custom/custom.crons.

You may have made the file on a windows machine, and then moved it to Linux. That will cause weird characters to exist in it.

Google the program dos2unix for more info on a converter you can use.

Dave Cameron
VE7LTD

On 2020-01-10 09:10, k9dc wrote:
What file are you looking at and how are you looking at it? It should
just be text.
'crontab -l’ to list it; ‘crontab -e’ to edit
-k9dc

On Jan 10, 2020, at 11:58, Charlie Wa2gug <wa2gug@...> wrote:
Dave thanks for reply. I tried looking at the file with an editor. It is unreadable. To me it looks curopt.
Can it be regenerated?
Charlie wa2gug
ARRL FIELD INSTRUCTOR, VE
-------- Original message --------
From k9dc <Dave@...>
Date: 01/10/2020 11:19 (GMT-05:00)
To IRLP@irlp.groups.io
Subject Re: [IRLP] new crontab file is missing newline before EOF, can't install.
Not worth re-installing over. The error message you received is pretty clear what the problem is.

new crontab file is missing newline before EOF, can't install.
Simply make sure the last character in the file is a NEWLINE, aka a <return> or <enter>. The crontab file must end with <return> <EOF>.
If there is anything other than a <return> at the end of that file, it will be rejected by the OS.
-k9dc


Re: new crontab file is missing newline before EOF, can't install.

k9dc
 

What file are you looking at and how are you looking at it? It should just be text.

'crontab -l’ to list it; ‘crontab -e’ to edit

-k9dc

On Jan 10, 2020, at 11:58, Charlie Wa2gug <wa2gug@...> wrote:

Dave thanks for reply. I tried looking at the file with an editor. It is unreadable. To me it looks curopt.
Can it be regenerated?


Charlie wa2gug
ARRL FIELD INSTRUCTOR, VE



-------- Original message --------
From k9dc <Dave@...>
Date: 01/10/2020 11:19 (GMT-05:00)
To IRLP@irlp.groups.io
Subject Re: [IRLP] new crontab file is missing newline before EOF, can't install.



Not worth re-installing over. The error message you received is pretty clear what the problem is.

new crontab file is missing newline before EOF, can't install.
Simply make sure the last character in the file is a NEWLINE, aka a <return> or <enter>. The crontab file must end with <return> <EOF>. If there is anything other than a <return> at the end of that file, it will be rejected by the OS.

-k9dc


Re: new crontab file is missing newline before EOF, can't install.

Charlie Wa2gug
 

Dave thanks for reply. I tried looking at the file with an editor. It is unreadable.  To me it looks curopt. 
Can it be regenerated?


Charlie wa2gug
ARRL FIELD INSTRUCTOR, VE



-------- Original message --------
From k9dc <Dave@...>
Date: 01/10/2020 11:19 (GMT-05:00)
To IRLP@irlp.groups.io
Subject Re: [IRLP] new crontab file is missing newline before EOF, can't install.



Not worth re-installing over. The error message you received is pretty clear what the problem is.

> new crontab file is missing newline before EOF, can't install.

Simply make sure the last character in the file is a NEWLINE, aka a <return> or <enter>.  The crontab file must end with <return> <EOF>.  If there is anything other than a <return> at the end of that file, it will be rejected by the OS.  

-k9dc


> On Jan 10, 2020, at 09:16, wa2gug@... wrote:
>
> I just had to rebuild my config. in my router. Ran ./scripts/update files and got this:
>
> new crontab file is missing newline before EOF, can't install.
>
> Any ideas? Was thinking of doing a fresh install
> 73
> Charlie wa2gug







Re: new crontab file is missing newline before EOF, can't install.

k9dc
 

Not worth re-installing over. The error message you received is pretty clear what the problem is.

new crontab file is missing newline before EOF, can't install.
Simply make sure the last character in the file is a NEWLINE, aka a <return> or <enter>. The crontab file must end with <return> <EOF>. If there is anything other than a <return> at the end of that file, it will be rejected by the OS.

-k9dc


On Jan 10, 2020, at 09:16, wa2gug@... wrote:

I just had to rebuild my config. in my router. Ran ./scripts/update files and got this:

new crontab file is missing newline before EOF, can't install.

Any ideas? Was thinking of doing a fresh install
73
Charlie wa2gug


new crontab file is missing newline before EOF, can't install.

Charlie Wa2gug
 

I just had to rebuild my config. in my router. Ran ./scripts/update files and got this:

new crontab file is missing newline before EOF, can't install.

Any ideas? Was thinking of doing a fresh install
73
Charlie wa2gug


Re: Redirecting EchoIRLP incoming connections??

John
 

My bad, Tim

try /home/EchoIRLP/scripts/echo_update_hosts

NB: the command line IS case sensitive !!

Even then, if this is Dave's node config, that might be wrong too.
The file you need to run to update the Echolink hosts is called
echo_update_hosts and it should be found in the EchoIRLP/scripts folder.

What are you seeing listed as the Echolink IP address for your two systems?
That's what I am pointing at, but if there's a problem with your porting,
the script above will not fix it.


73 John

On 10/01/2020 4:17:36 PM, Timothy Mc Bain - VK3MIT (irlp.lists.vk3mit@...) wrote:
Thank you John - there seems to be a problem with the path for that command - I'm getting a "no such file or directory" warning. Definitely running as repeater.
Tim.
-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of John
Sent: Friday, 10 January 2020 3:21 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

>FIX it?
Arrr.. I'm not sure at the mo, but if you did see the same address as I did, by searching for the IP address listed in /home/EchoIRLP/echo_hosts of both systems, that *might* be the issue.
Can I place $10 each way?
Note that data down with the date/time of those files, then run as repeater: /home/EchoIRLP/echo_update_hosts from each stn, and see if the data changes?
HTH
John
On 10/01/2020 1:44 pm, Timothy Mc Bain - VK3MIT wrote:
Many thanks John VK4JJW and John G.;
I have run the "update files" script on both nodes successfully, and, other than a very old "rsync" warning on node 6363 - which is an "embedded" node, several years old, also from Dave C. - all was ok.
I then ran troubleshoot on both machines, and apart from


Re: Redirecting EchoIRLP incoming connections??

Timothy Mc Bain - VK3MIT
 

Thank you John - there seems to be a problem with the path for that command - I'm getting a "no such file or directory" warning. Definitely running as repeater.

Tim.

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of John
Sent: Friday, 10 January 2020 3:21 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??


>FIX it?

Arrr.. I'm not sure at the mo, but if you did see the same address as I did, by searching for the IP address listed in /home/EchoIRLP/echo_hosts of both systems, that *might* be the issue.
Can I place $10 each way?

Note that data down with the date/time of those files, then run as repeater: /home/EchoIRLP/echo_update_hosts from each stn, and see if the data changes?

HTH
John

On 10/01/2020 1:44 pm, Timothy Mc Bain - VK3MIT wrote:
Many thanks John VK4JJW and John G.;

I have run the "update files" script on both nodes successfully, and, other than a very old "rsync" warning on node 6363 - which is an "embedded" node, several years old, also from Dave C. - all was ok.

I then ran troubleshoot on both machines, and apart from the usual EchoIRLP corruption warning, everything was good on both nodes.

I'm perplexed by your IP address information, John (G); on the
assumption that the IP addressing is the problem - and heavens knows
how that was changed - where would I find the IP address setting so I
can check it / FIX it? (Both nodes are on static IP's from iIINET)

Many thanks - Tim.
VK3MIT

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of John
Sent: Friday, 10 January 2020 1:36 PM
To: IRLP <IRLP@irlp.groups.io>
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

Tim,

Have a look at the IP address for echolink stns 290314 & 350851.
You'll find that info in /home/EchoIRLP/echo_hosts

On my stn 6163 they both are listed with the same IP address, and my listings are updated for today.

73 John

On 10/01/2020 11:59:48 AM, Timothy Mc Bain - VK3MIT (irlp.lists.vk3mit@...) wrote:
Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.
Its node 6364 / 290314 that is mis-behaving.

When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".

I don’t know if I've stuffed something up - I did have to
unfortunately block an IRLP node that was causing ongoing
interference and other issues for us - I may have broken something
with that process? I have just cleared out all the node blocking data
for both IRLP and EchoLink. (Was only one station that was blocked,
but had IRLP and EchoLink running, so both systems for that one
station were blocked - now completely un-blocked)

I have re-booted the Pi several times.

The nodes are 300 kms apart, on their own internet connections, both
are wired connections (as distinct from wi-fi) and are on a DSL type
connection via







Re: Redirecting EchoIRLP incoming connections??

John
 

FIX it?
Arrr.. I'm not sure at the mo, but if you did see the same address as I did,
by searching for the IP address listed in /home/EchoIRLP/echo_hosts
of both systems, that *might* be the issue.
Can I place $10 each way?

Note that data down with the date/time of those files,
then run as repeater: /home/EchoIRLP/echo_update_hosts
from each stn, and see if the data changes?

HTH
John

On 10/01/2020 1:44 pm, Timothy Mc Bain - VK3MIT wrote:
Many thanks John VK4JJW and John G.;
I have run the "update files" script on both nodes successfully, and, other than a very old "rsync" warning on node 6363 - which is an "embedded" node, several years old, also from Dave C. - all was ok.
I then ran troubleshoot on both machines, and apart from the usual EchoIRLP corruption warning, everything was good on both nodes.
I'm perplexed by your IP address information, John (G); on the assumption that the IP addressing is the problem - and heavens knows how that was changed - where would I find the IP address setting so I can check it / FIX it? (Both nodes are on static IP's from iIINET)
Many thanks - Tim.
VK3MIT
-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of John
Sent: Friday, 10 January 2020 1:36 PM
To: IRLP <IRLP@irlp.groups.io>
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??
Tim,
Have a look at the IP address for echolink stns 290314 & 350851.
You'll find that info in /home/EchoIRLP/echo_hosts
On my stn 6163 they both are listed with the same IP address, and my listings are updated for today.
73 John

On 10/01/2020 11:59:48 AM, Timothy Mc Bain - VK3MIT (irlp.lists.vk3mit@...) wrote:
Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.
Its node 6364 / 290314 that is mis-behaving.

When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".

I don’t know if I've stuffed something up - I did have to
unfortunately block an IRLP node that was causing ongoing interference
and other issues for us - I may have broken something with that
process? I have just cleared out all the node blocking data for both
IRLP and EchoLink. (Was only one station that was blocked, but had
IRLP and EchoLink running, so both systems for that one station were
blocked - now completely un-blocked)

I have re-booted the Pi several times.

The nodes are 300 kms apart, on their own internet connections, both
are wired connections (as distinct from wi-fi) and are on a DSL type
connection via


Re: Redirecting EchoIRLP incoming connections??

Timothy Mc Bain - VK3MIT
 

Many thanks John VK4JJW and John G.;

I have run the "update files" script on both nodes successfully, and, other than a very old "rsync" warning on node 6363 - which is an "embedded" node, several years old, also from Dave C. - all was ok.

I then ran troubleshoot on both machines, and apart from the usual EchoIRLP corruption warning, everything was good on both nodes.

I'm perplexed by your IP address information, John (G); on the assumption that the IP addressing is the problem - and heavens knows how that was changed - where would I find the IP address setting so I can check it / FIX it? (Both nodes are on static IP's from iIINET)

Many thanks - Tim.
VK3MIT

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of John
Sent: Friday, 10 January 2020 1:36 PM
To: IRLP <IRLP@irlp.groups.io>
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

Tim,

Have a look at the IP address for echolink stns 290314 & 350851.
You'll find that info in /home/EchoIRLP/echo_hosts

On my stn 6163 they both are listed with the same IP address, and my listings are updated for today.

73 John

On 10/01/2020 11:59:48 AM, Timothy Mc Bain - VK3MIT (irlp.lists.vk3mit@...) wrote:
Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.
Its node 6364 / 290314 that is mis-behaving.

When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".

I don’t know if I've stuffed something up - I did have to
unfortunately block an IRLP node that was causing ongoing interference
and other issues for us - I may have broken something with that
process? I have just cleared out all the node blocking data for both
IRLP and EchoLink. (Was only one station that was blocked, but had
IRLP and EchoLink running, so both systems for that one station were
blocked - now completely un-blocked)

I have re-booted the Pi several times.

The nodes are 300 kms apart, on their own internet connections, both
are wired connections (as distinct from wi-fi) and are on a DSL type
connection via


Re: Redirecting EchoIRLP incoming connections??

David McAnally
 

Could you have multiple EchoLink systems with the same call-L or call-R setup? Be sure each node is configured with it's own unique EchoLink call/node number. You cannot have multiple EchoLink nodes with the same call-L, or with the same call-R, configuration. In other words, I can only have one WD5M-R Echolink system active. Normal EchoIRLP systems have the configuration files in /home/EchoIRLP/custom/ directory. I believe you said this was Dave's implementation, in which case it may differ.

David M.
WD5M


Re: Redirecting EchoIRLP incoming connections??

John
 

Tim,

Have a look at the IP address for echolink stns 290314 & 350851.
You'll find that info in /home/EchoIRLP/echo_hosts

On my stn 6163 they both are listed with the same IP address,
and my listings are updated for today.

73 John

On 10/01/2020 11:59:48 AM, Timothy Mc Bain - VK3MIT (irlp.lists.vk3mit@...) wrote:
Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.
Its node 6364 / 290314 that is mis-behaving.
When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".
I don’t know if I've stuffed something up - I did have to unfortunately block an IRLP node that was causing ongoing interference and other issues for us - I may have broken something with that process? I have just cleared out all the node blocking data for both IRLP and EchoLink. (Was only one station that was blocked, but had IRLP and EchoLink running, so both systems for that one station were blocked - now completely un-blocked)
I have re-booted the Pi several times.
The nodes are 300 kms apart, on their own internet connections, both are wired connections (as distinct from wi-fi) and are on a DSL type connection via


Re: Redirecting EchoIRLP incoming connections??

John VK4JJW
 

On 10/01/2020 12:15 pm, Timothy Mc Bain - VK3MIT wrote:
No, the nodes are many many miles apart, quite independent of each other. I think its something that I may have stuffed up unknowingly. Still got the big sign out front saying “LEARNING” !!
Thanks heaps – Tim.
VK3MIT

Reckon it may have something to do with the PGP keys Tim.
For each node, do a troubleshoot-irlp while not connected to anything.

The section about the PGP Key tests should look like this:

*PGP Key Tests*
***************

Updating pgp keyring ... done.
------------------------------------------------------------------------------
TEST No. 5 REPORT - PASS - Your Public PGP key exists in the keyring.
------------------------------------------------------------------------------

------------------------------------------------------------------------------
TEST No. 6 REPORT - PASS - Your secret keyring only contains one secret
PGP key.
------------------------------------------------------------------------------

------------------------------------------------------------------------------
TEST No. 7 REPORT - PASS - Your Secret PGP key matches your node's stationID.
------------------------------------------------------------------------------

------------------------------------------------------------------------------
TEST No. 8 REPORT - PASS - Your Secret PGP Hash matches the key in the public
keyring.
------------------------------------------------------------------------------



Have a go at that and see what happens!


HTH

JW
--

EchoIRLP
IRLP Node 6527
EchoLink Node 96527

DMR 5054314


http://www.vk4jjw.info


Re: Redirecting EchoIRLP incoming connections??

Timothy Mc Bain - VK3MIT
 

No, the nodes are many many miles apart, quite independent of each other. I think its something that I may have stuffed up unknowingly. Still got the big sign out front saying “LEARNING” !!

 

Thanks heaps – Tim.

VK3MIT

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of James Hall
Sent: Friday, 10 January 2020 1:13 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

 

Had this happen when 2 nodes on same router. Ports are forwarded to one computer so when you call in to the other, audio is automatically steered to the one with the forwarded ports. Don't know if this your problem, but it sounds exactly like this scenario.

 

aloha

Jim wh7cd

 

Sent from the Cold Duck

 

 

On Thursday, January 9, 2020, 06:00:00 PM PST, Timothy Mc Bain - VK3MIT <irlp.lists.vk3mit@...> wrote:

 

 

Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.

Its node 6364 / 290314 that is mis-behaving.

When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".

I don’t know if I've stuffed something up - I did have to unfortunately block an IRLP node that was causing ongoing interference and other issues for us - I may have broken something with that process? I have just cleared out all the node blocking data for both IRLP and EchoLink. (Was only one station that was blocked, but had IRLP and EchoLink running, so both systems for that one station were blocked - now completely un-blocked)

I have re-booted the Pi several times.

The nodes are 300 kms apart, on their own internet connections, both are wired connections (as distinct from wi-fi) and are on a DSL type connection via a modem all of which has, until recently, been behaving flawlessly. Dunno what I've done....

Many thanks - Tim.
VK3MIT

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of k9dc
Sent: Friday, 10 January 2020 10:12 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

How about including the node numbers and the call symptoms, “If Node XXXX calls me, this happens.”  Your report is a little vague.  Also includes details about how the node is connected to the Internet. Do you have separate internet connections for each one?

-k9dc

> On Jan 9, 2020, at 18:07, Timothy Mc Bain - VK3MIT <irlp.lists.vk3mit@...> wrote:
>
> Hello Group;
>
> I'm looking after (insert here - trying!!) a club EchoIRLP Pi based node - one of Dave Camerons pre-built units.
>
> Somehow, perhaps via its own internal poltergeist, when the node receives an incoming connection request, it "diverts" - or something like that - and tries to connect to my own personal node.
>
> Each node is set up on its own ID number and different email address as normal. Each node is geographically separated, on its own internet connection, etc, but I can putty in to both.
>
> As far as I know, nothing has been done to cause this behaviour.
>
> Can someone assist with pointing me in the correct direction to fix this please? Perplexed here as to why and how this is happening!
>
> Many thanks - Tim.
> VK3MIT










Re: Redirecting EchoIRLP incoming connections??

James Hall
 

Had this happen when 2 nodes on same router. Ports are forwarded to one computer so when you call in to the other, audio is automatically steered to the one with the forwarded ports. Don't know if this your problem, but it sounds exactly like this scenario.

aloha
Jim wh7cd

Sent from the Cold Duck


On Thursday, January 9, 2020, 06:00:00 PM PST, Timothy Mc Bain - VK3MIT <irlp.lists.vk3mit@...> wrote:


Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.

Its node 6364 / 290314 that is mis-behaving.

When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".

I don’t know if I've stuffed something up - I did have to unfortunately block an IRLP node that was causing ongoing interference and other issues for us - I may have broken something with that process? I have just cleared out all the node blocking data for both IRLP and EchoLink. (Was only one station that was blocked, but had IRLP and EchoLink running, so both systems for that one station were blocked - now completely un-blocked)

I have re-booted the Pi several times.

The nodes are 300 kms apart, on their own internet connections, both are wired connections (as distinct from wi-fi) and are on a DSL type connection via a modem all of which has, until recently, been behaving flawlessly. Dunno what I've done....

Many thanks - Tim.
VK3MIT

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of k9dc
Sent: Friday, 10 January 2020 10:12 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

How about including the node numbers and the call symptoms, “If Node XXXX calls me, this happens.”  Your report is a little vague.  Also includes details about how the node is connected to the Internet. Do you have separate internet connections for each one?

-k9dc

> On Jan 9, 2020, at 18:07, Timothy Mc Bain - VK3MIT <irlp.lists.vk3mit@...> wrote:
>
> Hello Group;
>
> I'm looking after (insert here - trying!!) a club EchoIRLP Pi based node - one of Dave Camerons pre-built units.
>
> Somehow, perhaps via its own internal poltergeist, when the node receives an incoming connection request, it "diverts" - or something like that - and tries to connect to my own personal node.
>
> Each node is set up on its own ID number and different email address as normal. Each node is geographically separated, on its own internet connection, etc, but I can putty in to both.
>
> As far as I know, nothing has been done to cause this behaviour.
>
> Can someone assist with pointing me in the correct direction to fix this please? Perplexed here as to why and how this is happening!
>
> Many thanks - Tim.
> VK3MIT











Re: Redirecting EchoIRLP incoming connections??

Timothy Mc Bain - VK3MIT
 

Apologies, vague is about as good as I get at this hour!! I may have asked this on the wrong list - IRLP is working beautifully. Its on the EchoLink side of the node that the issue is occurring.

Its node 6364 / 290314 that is mis-behaving.

When a call is initiated to that node from either the iPhone EL app, or via an RF connection, it doesn't trigger node 6364 / 290314 at all, but connects straight away onto mine - 6363 / 350851. Nothing is heard on 6364. There is the usual connection message that comes out onto 6363 (instead of where it should on 6364) It is an immediate "divert".

I don’t know if I've stuffed something up - I did have to unfortunately block an IRLP node that was causing ongoing interference and other issues for us - I may have broken something with that process? I have just cleared out all the node blocking data for both IRLP and EchoLink. (Was only one station that was blocked, but had IRLP and EchoLink running, so both systems for that one station were blocked - now completely un-blocked)

I have re-booted the Pi several times.

The nodes are 300 kms apart, on their own internet connections, both are wired connections (as distinct from wi-fi) and are on a DSL type connection via a modem all of which has, until recently, been behaving flawlessly. Dunno what I've done....

Many thanks - Tim.
VK3MIT

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of k9dc
Sent: Friday, 10 January 2020 10:12 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Redirecting EchoIRLP incoming connections??

How about including the node numbers and the call symptoms, “If Node XXXX calls me, this happens.” Your report is a little vague. Also includes details about how the node is connected to the Internet. Do you have separate internet connections for each one?

-k9dc

On Jan 9, 2020, at 18:07, Timothy Mc Bain - VK3MIT <irlp.lists.vk3mit@...> wrote:

Hello Group;

I'm looking after (insert here - trying!!) a club EchoIRLP Pi based node - one of Dave Camerons pre-built units.

Somehow, perhaps via its own internal poltergeist, when the node receives an incoming connection request, it "diverts" - or something like that - and tries to connect to my own personal node.

Each node is set up on its own ID number and different email address as normal. Each node is geographically separated, on its own internet connection, etc, but I can putty in to both.

As far as I know, nothing has been done to cause this behaviour.

Can someone assist with pointing me in the correct direction to fix this please? Perplexed here as to why and how this is happening!

Many thanks - Tim.
VK3MIT


Re: Redirecting EchoIRLP incoming connections??

k9dc
 

How about including the node numbers and the call symptoms, “If Node XXXX calls me, this happens.” Your report is a little vague. Also includes details about how the node is connected to the Internet. Do you have separate internet connections for each one?

-k9dc

On Jan 9, 2020, at 18:07, Timothy Mc Bain - VK3MIT <irlp.lists.vk3mit@...> wrote:

Hello Group;

I'm looking after (insert here - trying!!) a club EchoIRLP Pi based node - one of Dave Camerons pre-built units.

Somehow, perhaps via its own internal poltergeist, when the node receives an incoming connection request, it "diverts" - or something like that - and tries to connect to my own personal node.

Each node is set up on its own ID number and different email address as normal. Each node is geographically separated, on its own internet connection, etc, but I can putty in to both.

As far as I know, nothing has been done to cause this behaviour.

Can someone assist with pointing me in the correct direction to fix this please? Perplexed here as to why and how this is happening!

Many thanks - Tim.
VK3MIT


Redirecting EchoIRLP incoming connections??

Timothy Mc Bain - VK3MIT
 

Hello Group;

I'm looking after (insert here - trying!!) a club EchoIRLP Pi based node - one of Dave Camerons pre-built units.

Somehow, perhaps via its own internal poltergeist, when the node receives an incoming connection request, it "diverts" - or something like that - and tries to connect to my own personal node.

Each node is set up on its own ID number and different email address as normal. Each node is geographically separated, on its own internet connection, etc, but I can putty in to both.

As far as I know, nothing has been done to cause this behaviour.

Can someone assist with pointing me in the correct direction to fix this please? Perplexed here as to why and how this is happening!

Many thanks - Tim.
VK3MIT


Re: clear_IRLP_GPIO

Ken Pokigo
 

Thank you so much Dave
Its extremely appreciated

73
Ken
KC2AYK

On Tuesday, January 7, 2020, 07:27:18 PM EST, David Cameron - IRLP <dcameron@...> wrote:


Attached:

#!/bin/bash

# In order: D0, D1, D2, D3, COS
INGPIO="4 25 9 24 10"
# In order: PTT, AUX1, AUX2, AUX3
OUTGPIO="17 18 22 23"

#Export all pins and set input/ouput
for i in ${INGPIO} ${OUTGPIO}; do
  if [ -d /sys/class/gpio/gpio${i} ] ; then
    echo "${i}" > /sys/class/gpio/unexport
    EXPORTS="${EXPORTS} ${i}"
  fi
done

if [ ! -z "${EXPORTS}" ] ; then
  echo "Clearing IRLP GPIO pins${EXPORTS}"
fi



On 2020-01-07 16:18, Ken Pokigo via Groups.Io wrote:
> I have a PI IRLP node and lost some files
>
> Does anyone one have the file 'clear_IRLP_GPIO' ?
> Its in the path    /home/irlp/custom
>
> Thanks
>
> Ken
> KC2AYK
>
>
> Links:
> ------
> [1] https://irlp.groups.io/g/IRLP/message/76579

> [2]
https://groups.io/mt/69517009/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