Node Owner


VK3AJ
 

Hi and seasons greetings from Down Under,

 

How can I find out who is connecting an IRLP reflector to my IRLP/EchoIRLP node through EchoLink.

 

We have theBridge conference *SCOUT-VK*  that is meant to be connected to our EchoIRLP 6372/VK3RAJ-R, but someone is connecting IRLP reflector 9307 to EchoLink before theBridge can establish our link.

 

Any assistance would be appreciated.

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

IRLP Node 6372 / EchoLink Node VK3RAJ-R

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 


Nosey Nick VA3NNW
 

Peter VK3AJ wrote:

Hi and seasons greetings from Down Under,

Hi Peter, compliments of the season to ya! Hope you're enjoying White Wine In The Sun!

 How can I find out who is connecting an IRLP reflector to my IRLP/EchoIRLP node through EchoLink.

Your ~repeater/log/messages (or messages.1 messages.2 messages.3 etc for older logs) should say something like:

Dec 02 2020 20:14:48 +0000 EchoIRLP: connected echolink THEIR-CALL 1
Dec 02 2020 20:14:56 +0000 EchoIRLP: connected speakfreely YOUR-CALL-R 2

Dec 02 2020 20:15:48 +0000 EchoIRLP: disconnected bye THEIR-CALL 1
Dec 02 2020 20:15:50 +0000 EchoIRLP: Node Disconnect from EchoLink 1234567 THEIR-CALL
Dec 02 2020 20:15:59 +0000 EchoIRLP: disconnected bye YOUR-CALL-R 0

Hope that helps?

Nick VA3NNW, custodian of node 2410

-- 
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer;    sig@...
Space is not merely curved - it is, in fact, completely bent.


 

On 23/12/20 4:30 pm, VK3AJ wrote:

Hi and seasons greetings from Down Under,

 

How can I find out who is connecting an IRLP reflector to my IRLP/EchoIRLP node through EchoLink.

 

We have theBridge conference *SCOUT-VK*  that is meant to be connected to our EchoIRLP 6372/VK3RAJ-R, but someone is connecting IRLP reflector 9307 to EchoLink before theBridge can establish our link.

OK, want to get 100% clear on what is going on, because as it is written, what you're describing is impossible.  It's not possible for someone to connect another IRLP reflector to Echolink as it's written with EchoIRLP.  EchoIRLP is specifically designed to prohibit that, and the way the system is designed, it's actually impossible with a stock EchoIRLP node.

Anyway, you will need to go through the logs to see what's happening, then we can work out what's going on.

 

Any assistance would be appreciated.

If need be, feel free to contact me off list, I know the internals of EchoIRLP very well (I did a lot of work on it). :)
-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


VK3AJ
 

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

This is usually because Experimental Node 9307 gets connected.

How can I export them from the IRLP node so I can attach them to an email?

 

73’s and Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

IRLP Node 6372

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Friday, 25 December 2020 13:57
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 23/12/20 4:30 pm, VK3AJ wrote:

Hi and seasons greetings from Down Under,

 

How can I find out who is connecting an IRLP reflector to my IRLP/EchoIRLP node through EchoLink.

 

We have theBridge conference *SCOUT-VK*  that is meant to be connected to our EchoIRLP 6372/VK3RAJ-R, but someone is connecting IRLP reflector 9307 to EchoLink before theBridge can establish our link.

OK, want to get 100% clear on what is going on, because as it is written, what you're describing is impossible.  It's not possible for someone to connect another IRLP reflector to Echolink as it's written with EchoIRLP.  EchoIRLP is specifically designed to prohibit that, and the way the system is designed, it's actually impossible with a stock EchoIRLP node.

Anyway, you will need to go through the logs to see what's happening, then we can work out what's going on.

 

Any assistance would be appreciated.

If need be, feel free to contact me off list, I know the internals of EchoIRLP very well (I did a lot of work on it). :)

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


Dave K9DC
 

*SCOUT-VK* is not an IRLP destination. We would have no idea here. You might get better answers from the Echolink team. Some Echolink conferences are configured to not allow Repeaters or EchoIRLP nodes to connect (I know, it makes no sense ro me either). You will need to find someone associated with *SCOUT-VK* and inquire about their policies.

9307 is not an experimental node. It is a full on IRLP reflector, channel 7 of 9300. http://status.irlp.net/?nodeid=9300

-k9dc

On Dec 27, 2020, at 07:11, VK3AJ <vk3aj@chaplin.net.au> wrote:

Hi Tony,

I’m not a Linux person and only know basic functions.
I’ve found the log files, but can’t really make much sense of them.
I can see the disconnects, but not the cause.
It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.
This is usually because Experimental Node 9307 gets connected.
How can I export them from the IRLP node so I can attach them to an email?

73’s and Regards,

Peter Chaplin
peter@chaplin.net.au
VK3AJ
Scout Radio & Electronics Service Unit
Repeater Coordinator
IRLP Node 6372
<image001.png>

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Friday, 25 December 2020 13:57
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

On 23/12/20 4:30 pm, VK3AJ wrote:
Hi and seasons greetings from Down Under,

How can I find out who is connecting an IRLP reflector to my IRLP/EchoIRLP node through EchoLink.

We have theBridge conference *SCOUT-VK* that is meant to be connected to our EchoIRLP 6372/VK3RAJ-R, but someone is connecting IRLP reflector 9307 to EchoLink before theBridge can establish our link.
OK, want to get 100% clear on what is going on, because as it is written, what you're describing is impossible. It's not possible for someone to connect another IRLP reflector to Echolink as it's written with EchoIRLP. EchoIRLP is specifically designed to prohibit that, and the way the system is designed, it's actually impossible with a stock EchoIRLP node.

Anyway, you will need to go through the logs to see what's happening, then we can work out what's going on.


Any assistance would be appreciated.
If need be, feel free to contact me off list, I know the internals of EchoIRLP very well (I did a lot of work on it). :)


zl1vfo
 

If something is making the node reconnect at x:36 hrs, then it might be worth looking in the crontab

crontab -l should do it. (the -l is a lower case L)

Mine has this in it, which I think is fairly standard

SHELL=/bin/bash
TERM=xterm
BASH_ENV=/home/irlp/.profile
0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)
30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)
0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)
0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)
*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)
0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

As for copying text from the logs - just click and drag over the text to highlight the bits you want, and it is automatically copied to the clipboard. (Assuming that you are using PuTTY ) You can paste into an email from there..

73, Ian ZL1VFO Node 6950, 6611


 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 

I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).

How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.
-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


 

On 28/12/20 8:03 am, zl1vfo via groups.io wrote:

If something is making the node reconnect at x:36 hrs, then it might
be worth looking in the crontab

crontab -l should do it. (the -l is a lower case L)

Mine has this in it, which I think is fairly standard
That was my first thought as well.  I won't post my crontab here, it's
got a lot of extras in it. :)

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


VK3AJ
 

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

Dec 24 2020 16:36:35 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 16:36:37 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 16:36:47 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 16:36:49 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Dec 24 2020 17:18:59 +1100 EchoIRLP: connected echolink UX1LW 1

Dec 24 2020 17:19:07 +1100 EchoIRLP: disconnected bye UX1LW 0

Dec 24 2020 17:19:10 +1100 EchoIRLP: Node Disconnect from EchoLink 737478 UX1LW

Dec 24 2020 17:19:20 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 24 2020 17:19:21 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 22:25:24 +1100 EchoIRLP: connected echolink VK6EDY 1

Dec 24 2020 22:25:32 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 22:26:12 +1100 EchoIRLP: disconnected bye VK6EDY 1

Dec 24 2020 22:26:14 +1100 EchoIRLP: Node Disconnect from EchoLink 629000 VK6EDY

Dec 24 2020 22:26:23 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 03:01:14 +1100 decode: DTMF = A

Dec 25 2020 03:01:14 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 25 2020 04:00:56 +1100 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.

Dec 25 2020 10:42:05 +1100 stn6403 connect UNCOMP

Dec 25 2020 10:43:14 +1100 stn6403 disconnect

Dec 25 2020 13:32:17 +1100 EchoIRLP: connected echolink N5GFL 1

Dec 25 2020 13:32:25 +1100 EchoIRLP: disconnected bye N5GFL 0

Dec 25 2020 13:32:28 +1100 EchoIRLP: Node Disconnect from EchoLink 941866 N5GFL

Dec 25 2020 13:32:38 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 25 2020 13:32:38 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 14:48:51 +1100 EchoIRLP: connected echolink N3XQX 1

Dec 25 2020 14:48:59 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 25 2020 14:51:04 +1100 EchoIRLP: disconnected bye N3XQX 1

Dec 25 2020 14:51:06 +1100 EchoIRLP: Node Disconnect from EchoLink 635826 N3XQX

Dec 25 2020 14:51:15 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 26 2020 08:40:12 +1100 decode: DTMF = A

Dec 26 2020 08:40:13 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 11:03:22 +1100 decode: DTMF = 2898

Dec 26 2020 11:03:23 +1100 IRLP call initiated to stn2898

Dec 26 2020 11:03:23 +1100 noexist

Dec 26 2020 11:03:38 +1100 decode: DTMF = 713

Dec 26 2020 11:03:38 +1100 decode: Invalid command length: 713

Dec 26 2020 21:25:07 +1100 decode: DTMF = 0

Dec 26 2020 21:25:07 +1100 decode: Invalid command length: 0

Dec 26 2020 21:25:40 +1100 decode: DTMF = P

Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Monday, 28 December 2020 09:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 

I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).

How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.

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


Ed W6YJ
 

Peter,

Look in:

/home/irlp/custom/custom.crons

If it exists and you haven't checked there already.

Ed W6YJ


On 12/28/2020 2:01 AM, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

Dec 24 2020 16:36:35 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 16:36:37 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 16:36:47 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 16:36:49 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Dec 24 2020 17:18:59 +1100 EchoIRLP: connected echolink UX1LW 1

Dec 24 2020 17:19:07 +1100 EchoIRLP: disconnected bye UX1LW 0

Dec 24 2020 17:19:10 +1100 EchoIRLP: Node Disconnect from EchoLink 737478 UX1LW

Dec 24 2020 17:19:20 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 24 2020 17:19:21 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 22:25:24 +1100 EchoIRLP: connected echolink VK6EDY 1

Dec 24 2020 22:25:32 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 22:26:12 +1100 EchoIRLP: disconnected bye VK6EDY 1

Dec 24 2020 22:26:14 +1100 EchoIRLP: Node Disconnect from EchoLink 629000 VK6EDY

Dec 24 2020 22:26:23 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 03:01:14 +1100 decode: DTMF = A

Dec 25 2020 03:01:14 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 25 2020 04:00:56 +1100 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.

Dec 25 2020 10:42:05 +1100 stn6403 connect UNCOMP

Dec 25 2020 10:43:14 +1100 stn6403 disconnect

Dec 25 2020 13:32:17 +1100 EchoIRLP: connected echolink N5GFL 1

Dec 25 2020 13:32:25 +1100 EchoIRLP: disconnected bye N5GFL 0

Dec 25 2020 13:32:28 +1100 EchoIRLP: Node Disconnect from EchoLink 941866 N5GFL

Dec 25 2020 13:32:38 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 25 2020 13:32:38 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 14:48:51 +1100 EchoIRLP: connected echolink N3XQX 1

Dec 25 2020 14:48:59 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 25 2020 14:51:04 +1100 EchoIRLP: disconnected bye N3XQX 1

Dec 25 2020 14:51:06 +1100 EchoIRLP: Node Disconnect from EchoLink 635826 N3XQX

Dec 25 2020 14:51:15 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 26 2020 08:40:12 +1100 decode: DTMF = A

Dec 26 2020 08:40:13 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 11:03:22 +1100 decode: DTMF = 2898

Dec 26 2020 11:03:23 +1100 IRLP call initiated to stn2898

Dec 26 2020 11:03:23 +1100 noexist

Dec 26 2020 11:03:38 +1100 decode: DTMF = 713

Dec 26 2020 11:03:38 +1100 decode: Invalid command length: 713

Dec 26 2020 21:25:07 +1100 decode: DTMF = 0

Dec 26 2020 21:25:07 +1100 decode: Invalid command length: 0

Dec 26 2020 21:25:40 +1100 decode: DTMF = P

Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Monday, 28 December 2020 09:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 

I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).

How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.

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


VK3AJ
 

Thanks for the suggestion.

I can’t find such file in either root or repeater.

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Ed W6YJ
Sent: Tuesday, 29 December 2020 10:18
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

Peter,

Look in:

/home/irlp/custom/custom.crons

If it exists and you haven't checked there already.

Ed W6YJ

 

On 12/28/2020 2:01 AM, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

Dec 24 2020 16:36:35 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 16:36:37 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 16:36:47 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 16:36:49 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Dec 24 2020 17:18:59 +1100 EchoIRLP: connected echolink UX1LW 1

Dec 24 2020 17:19:07 +1100 EchoIRLP: disconnected bye UX1LW 0

Dec 24 2020 17:19:10 +1100 EchoIRLP: Node Disconnect from EchoLink 737478 UX1LW

Dec 24 2020 17:19:20 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 24 2020 17:19:21 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 22:25:24 +1100 EchoIRLP: connected echolink VK6EDY 1

Dec 24 2020 22:25:32 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 22:26:12 +1100 EchoIRLP: disconnected bye VK6EDY 1

Dec 24 2020 22:26:14 +1100 EchoIRLP: Node Disconnect from EchoLink 629000 VK6EDY

Dec 24 2020 22:26:23 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 03:01:14 +1100 decode: DTMF = A

Dec 25 2020 03:01:14 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 25 2020 04:00:56 +1100 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.

Dec 25 2020 10:42:05 +1100 stn6403 connect UNCOMP

Dec 25 2020 10:43:14 +1100 stn6403 disconnect

Dec 25 2020 13:32:17 +1100 EchoIRLP: connected echolink N5GFL 1

Dec 25 2020 13:32:25 +1100 EchoIRLP: disconnected bye N5GFL 0

Dec 25 2020 13:32:28 +1100 EchoIRLP: Node Disconnect from EchoLink 941866 N5GFL

Dec 25 2020 13:32:38 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 25 2020 13:32:38 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 14:48:51 +1100 EchoIRLP: connected echolink N3XQX 1

Dec 25 2020 14:48:59 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 25 2020 14:51:04 +1100 EchoIRLP: disconnected bye N3XQX 1

Dec 25 2020 14:51:06 +1100 EchoIRLP: Node Disconnect from EchoLink 635826 N3XQX

Dec 25 2020 14:51:15 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 26 2020 08:40:12 +1100 decode: DTMF = A

Dec 26 2020 08:40:13 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 11:03:22 +1100 decode: DTMF = 2898

Dec 26 2020 11:03:23 +1100 IRLP call initiated to stn2898

Dec 26 2020 11:03:23 +1100 noexist

Dec 26 2020 11:03:38 +1100 decode: DTMF = 713

Dec 26 2020 11:03:38 +1100 decode: Invalid command length: 713

Dec 26 2020 21:25:07 +1100 decode: DTMF = 0

Dec 26 2020 21:25:07 +1100 decode: Invalid command length: 0

Dec 26 2020 21:25:40 +1100 decode: DTMF = P

Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Monday, 28 December 2020 09:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 


I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).


How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.

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


Bob DeMattia, K1IW
 

There should be a file there.  However, the table you sent out earlier was the result of a crontab -l command, so it would have included anything in custom.crons anyways.



On Tue, Dec 29, 2020 at 3:26 AM VK3AJ <vk3aj@...> wrote:

Thanks for the suggestion.

I can’t find such file in either root or repeater.

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Ed W6YJ
Sent: Tuesday, 29 December 2020 10:18
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

Peter,

Look in:

/home/irlp/custom/custom.crons

If it exists and you haven't checked there already.

Ed W6YJ

 

On 12/28/2020 2:01 AM, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

Dec 24 2020 16:36:35 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 16:36:37 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 16:36:47 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 16:36:49 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Dec 24 2020 17:18:59 +1100 EchoIRLP: connected echolink UX1LW 1

Dec 24 2020 17:19:07 +1100 EchoIRLP: disconnected bye UX1LW 0

Dec 24 2020 17:19:10 +1100 EchoIRLP: Node Disconnect from EchoLink 737478 UX1LW

Dec 24 2020 17:19:20 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 24 2020 17:19:21 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 22:25:24 +1100 EchoIRLP: connected echolink VK6EDY 1

Dec 24 2020 22:25:32 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 22:26:12 +1100 EchoIRLP: disconnected bye VK6EDY 1

Dec 24 2020 22:26:14 +1100 EchoIRLP: Node Disconnect from EchoLink 629000 VK6EDY

Dec 24 2020 22:26:23 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 03:01:14 +1100 decode: DTMF = A

Dec 25 2020 03:01:14 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 25 2020 04:00:56 +1100 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.

Dec 25 2020 10:42:05 +1100 stn6403 connect UNCOMP

Dec 25 2020 10:43:14 +1100 stn6403 disconnect

Dec 25 2020 13:32:17 +1100 EchoIRLP: connected echolink N5GFL 1

Dec 25 2020 13:32:25 +1100 EchoIRLP: disconnected bye N5GFL 0

Dec 25 2020 13:32:28 +1100 EchoIRLP: Node Disconnect from EchoLink 941866 N5GFL

Dec 25 2020 13:32:38 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 25 2020 13:32:38 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 14:48:51 +1100 EchoIRLP: connected echolink N3XQX 1

Dec 25 2020 14:48:59 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 25 2020 14:51:04 +1100 EchoIRLP: disconnected bye N3XQX 1

Dec 25 2020 14:51:06 +1100 EchoIRLP: Node Disconnect from EchoLink 635826 N3XQX

Dec 25 2020 14:51:15 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 26 2020 08:40:12 +1100 decode: DTMF = A

Dec 26 2020 08:40:13 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 11:03:22 +1100 decode: DTMF = 2898

Dec 26 2020 11:03:23 +1100 IRLP call initiated to stn2898

Dec 26 2020 11:03:23 +1100 noexist

Dec 26 2020 11:03:38 +1100 decode: DTMF = 713

Dec 26 2020 11:03:38 +1100 decode: Invalid command length: 713

Dec 26 2020 21:25:07 +1100 decode: DTMF = 0

Dec 26 2020 21:25:07 +1100 decode: Invalid command length: 0

Dec 26 2020 21:25:40 +1100 decode: DTMF = P

Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Monday, 28 December 2020 09:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 


I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).


How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.

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


Randy N9NWA
 

FYI

I had to create my own custom.cron file.
when I purchased the pi.

Raspberry PI

Randy N9NWA
Node 5370


Sent from Xfinity Connect Application


-----Original Message-----

From: bob.groupsio@...
To: IRLP@irlp.groups.io
Sent: 2020-12-29 2:39:47 PM
Subject: Re: [IRLP] Node Owner

There should be a file there.  However, the table you sent out earlier was the result of a crontab -l command, so it would have included anything in custom.crons anyways.



On Tue, Dec 29, 2020 at 3:26 AM VK3AJ <vk3aj@...> wrote:

Thanks for the suggestion.

I can’t find such file in either root or repeater.

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Ed W6YJ
Sent: Tuesday, 29 December 2020 10:18
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

Peter,

Look in:

/home/irlp/custom/custom.crons

If it exists and you haven't checked there already.

Ed W6YJ

 

On 12/28/2020 2:01 AM, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

Dec 24 2020 16:36:35 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 16:36:37 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 16:36:47 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 16:36:49 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Dec 24 2020 17:18:59 +1100 EchoIRLP: connected echolink UX1LW 1

Dec 24 2020 17:19:07 +1100 EchoIRLP: disconnected bye UX1LW 0

Dec 24 2020 17:19:10 +1100 EchoIRLP: Node Disconnect from EchoLink 737478 UX1LW

Dec 24 2020 17:19:20 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 24 2020 17:19:21 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 22:25:24 +1100 EchoIRLP: connected echolink VK6EDY 1

Dec 24 2020 22:25:32 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 22:26:12 +1100 EchoIRLP: disconnected bye VK6EDY 1

Dec 24 2020 22:26:14 +1100 EchoIRLP: Node Disconnect from EchoLink 629000 VK6EDY

Dec 24 2020 22:26:23 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 03:01:14 +1100 decode: DTMF = A

Dec 25 2020 03:01:14 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 25 2020 04:00:56 +1100 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.

Dec 25 2020 10:42:05 +1100 stn6403 connect UNCOMP

Dec 25 2020 10:43:14 +1100 stn6403 disconnect

Dec 25 2020 13:32:17 +1100 EchoIRLP: connected echolink N5GFL 1

Dec 25 2020 13:32:25 +1100 EchoIRLP: disconnected bye N5GFL 0

Dec 25 2020 13:32:28 +1100 EchoIRLP: Node Disconnect from EchoLink 941866 N5GFL

Dec 25 2020 13:32:38 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 25 2020 13:32:38 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 14:48:51 +1100 EchoIRLP: connected echolink N3XQX 1

Dec 25 2020 14:48:59 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 25 2020 14:51:04 +1100 EchoIRLP: disconnected bye N3XQX 1

Dec 25 2020 14:51:06 +1100 EchoIRLP: Node Disconnect from EchoLink 635826 N3XQX

Dec 25 2020 14:51:15 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 26 2020 08:40:12 +1100 decode: DTMF = A

Dec 26 2020 08:40:13 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 11:03:22 +1100 decode: DTMF = 2898

Dec 26 2020 11:03:23 +1100 IRLP call initiated to stn2898

Dec 26 2020 11:03:23 +1100 noexist

Dec 26 2020 11:03:38 +1100 decode: DTMF = 713

Dec 26 2020 11:03:38 +1100 decode: Invalid command length: 713

Dec 26 2020 21:25:07 +1100 decode: DTMF = 0

Dec 26 2020 21:25:07 +1100 decode: Invalid command length: 0

Dec 26 2020 21:25:40 +1100 decode: DTMF = P

Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Monday, 28 December 2020 09:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 


I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).


How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.

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




 

On 28/12/20 9:01 pm, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

Yeah, it is a different world.  This is more systems administration, which is still a different skill set.  Happy learning. :)  It will take a bit of

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

OK, that helps.  Fairly standard, by the looks of it.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

OK, something is still not making sense with your description, but that's possibly not your fault, given there's a lot of third party information in there.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

Looks pretty standard, nothing out of the ordinary there.

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

This looks like something disrupted the Internet connection, and then the link to *SCOUT-VK* re-established when it came back up.

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

That could be anything, even noise.

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Hmm, the conference attempted to reconnect when someone was using the repeater locally.


Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

Looks like someone is connecting you to 9307.  Possibly a pirate or misbehaving amateur?
-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


 

It's in /home/irlp/custom/custom.crons .  However, the contents of this file are merged into repeater's contab (what crontab -l displays) by the update script when it's run as $SCRIPT/update files, so the output of crontab -l will cover that.  That output also shows all of the user's scheduled jobs that are actually running.  Anyway, your crontab looks fine, all standard stuff.

On 29/12/20 7:25 pm, VK3AJ wrote:

Thanks for the suggestion.

I can’t find such file in either root or repeater.

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Ed W6YJ
Sent: Tuesday, 29 December 2020 10:18
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

Peter,

Look in:

/home/irlp/custom/custom.crons

If it exists and you haven't checked there already.

Ed W6YJ

 

On 12/28/2020 2:01 AM, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

Dec 24 2020 16:36:35 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 16:36:37 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 16:36:47 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 16:36:49 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Dec 24 2020 17:18:59 +1100 EchoIRLP: connected echolink UX1LW 1

Dec 24 2020 17:19:07 +1100 EchoIRLP: disconnected bye UX1LW 0

Dec 24 2020 17:19:10 +1100 EchoIRLP: Node Disconnect from EchoLink 737478 UX1LW

Dec 24 2020 17:19:20 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 24 2020 17:19:21 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 22:25:24 +1100 EchoIRLP: connected echolink VK6EDY 1

Dec 24 2020 22:25:32 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 22:26:12 +1100 EchoIRLP: disconnected bye VK6EDY 1

Dec 24 2020 22:26:14 +1100 EchoIRLP: Node Disconnect from EchoLink 629000 VK6EDY

Dec 24 2020 22:26:23 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 03:01:14 +1100 decode: DTMF = A

Dec 25 2020 03:01:14 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 25 2020 04:00:56 +1100 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.

Dec 25 2020 10:42:05 +1100 stn6403 connect UNCOMP

Dec 25 2020 10:43:14 +1100 stn6403 disconnect

Dec 25 2020 13:32:17 +1100 EchoIRLP: connected echolink N5GFL 1

Dec 25 2020 13:32:25 +1100 EchoIRLP: disconnected bye N5GFL 0

Dec 25 2020 13:32:28 +1100 EchoIRLP: Node Disconnect from EchoLink 941866 N5GFL

Dec 25 2020 13:32:38 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 1

Dec 25 2020 13:32:38 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 25 2020 14:48:51 +1100 EchoIRLP: connected echolink N3XQX 1

Dec 25 2020 14:48:59 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 25 2020 14:51:04 +1100 EchoIRLP: disconnected bye N3XQX 1

Dec 25 2020 14:51:06 +1100 EchoIRLP: Node Disconnect from EchoLink 635826 N3XQX

Dec 25 2020 14:51:15 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 26 2020 08:40:12 +1100 decode: DTMF = A

Dec 26 2020 08:40:13 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 11:03:22 +1100 decode: DTMF = 2898

Dec 26 2020 11:03:23 +1100 IRLP call initiated to stn2898

Dec 26 2020 11:03:23 +1100 noexist

Dec 26 2020 11:03:38 +1100 decode: DTMF = 713

Dec 26 2020 11:03:38 +1100 decode: Invalid command length: 713

Dec 26 2020 21:25:07 +1100 decode: DTMF = 0

Dec 26 2020 21:25:07 +1100 decode: Invalid command length: 0

Dec 26 2020 21:25:40 +1100 decode: DTMF = P

Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Monday, 28 December 2020 09:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 27/12/20 11:11 pm, VK3AJ wrote:

Hi Tony,

 

I’m not a Linux person and only know basic functions.

I recommend node owners become more proficient with Linux over time, it can really help. 


I’ve found the log files, but can’t really make much sense of them.

I can see the disconnects, but not the cause.

It appears that something causes a disconnect and reconnect each hour at x:36 and if someone sets up an alternate call during this disconnect/reconnect cycle, they take control and my automatic connection to *SCOUT-VK* then fails at every attempt.

That looks like a cron job (scheduled events).  Log in as repeater and post the output of

crontab -l

It's almost certainly not someone else doing it, from your description.

This is usually because Experimental Node 9307 gets connected.

That's a reflector, not an experimental node (Experimental nodes are 0xxx).


How can I export them from the IRLP node so I can attach them to an email?

Use WinSCP on your Windows machine to copy the files.  I'm assuming you use Windows for your email, etc.

-- 
73 de Tony VK3JED/VK3IRL



73's Ian - K6IAN


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


VK3AJ
 

Hi Tony,

 

Thanks for your review and feedback.

 

Looks like I need to investigate if something is disrupting the Internet connection.

 

Is there a setting that can be changed to stop connections from local RF?

Since our intention is for the node to be permanently connected to *SCOUT-VK* to allow Scouting contacts to call in via IRLP or Echolink, there is no need for local RF users to be able to initiate via DTMF locally.

 

Regards,

 

Peter Chaplin

peter@...

VK3AJ

Scout Radio & Electronics Service Unit

Repeater Coordinator

 

 

No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Tony Langdon
Sent: Wednesday, 30 December 2020 19:47
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 28/12/20 9:01 pm, VK3AJ wrote:

Hi Tony/et al,

 

My apologies for calling 9307 an experimental node.

Today’s new learning has been how to tell the difference.

 

I’m learning how to navigate around Linux, but the coding I struggle with. I’m an RF Tech, not a computer programmer.

Yeah, it is a different world.  This is more systems administration, which is still a different skill set.  Happy learning. :)  It will take a bit of

 

The IRLP node is a Standard Pi3 from DC with EchoIRLP enabled.

I understand that neither theBridge or EchoIRLP are supported here.

OK, that helps.  Fairly standard, by the looks of it.

What I’m trying to find out is how Reflector 9307 is ending up connected to VK3RAJ-R as I’ve heard complaints on air from those using 9307 for a net of my node interfering with their net.

I’ve also received an email from a US amateur who for some reason is being cc’d on node blocked/unblocked messages regarding the interference with the net.

As a consequence, I’ve disabled the node until I can get to the bottom of what’s happening.

Any assistance is greatly appreciated.

OK, something is still not making sense with your description, but that's possibly not your fault, given there's a lot of third party information in there.

 

Here is the output of my Crontab

 

repeater@stn6372:~/$ crontab -l

SHELL=/bin/bash

TERM=xterm

BASH_ENV=/home/irlp/.profile

0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1)

30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1)

0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1)

0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1)

*/15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1)

0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1)

repeater@stn6372:~/$

Looks pretty standard, nothing out of the ordinary there.

 

And here is output from the Messages file.

I suspect the DTMF is a local pirate trying to workout what digits disconnect the node. I’ve had trouble in the past where the pirate connects to the *IRELAND* Echolink conference and leaves it connected.

When I setup the *SCOUT-VK* conference using theBridge, I disabled the ability for RF users to disconnect the IRLP node and I set the *SCOUT-VK* conference to connect and stay connected to VK3RAJ-R which is part of a network of 5 repeaters that Scouts Victoria have linked.

 

Dec 24 2020 14:36:46 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 14:36:56 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

Dec 24 2020 15:36:33 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 1

Dec 24 2020 15:36:35 +1100 EchoIRLP: Node Disconnect from EchoLink 516518 *SCOUT-VK*

Dec 24 2020 15:36:46 +1100 EchoIRLP: disconnected bye VK3RAJ-R 0

Dec 24 2020 15:36:47 +1100 EchoIRLP: connected echolink *SCOUT-VK* 1

Dec 24 2020 15:36:57 +1100 EchoIRLP: connected speakfreely VK3RAJ-R 2

This looks like something disrupted the Internet connection, and then the link to *SCOUT-VK* re-established when it came back up.

Dec 24 2020 16:09:07 +1100 decode: DTMF = 1

Dec 24 2020 16:09:07 +1100 decode: Invalid command length: 1

That could be anything, even noise.

Dec 24 2020 16:36:49 +1100 EchoIRLP: Busy Local

Dec 24 2020 16:36:56 +1100 EchoIRLP: sent_chat VK3RAJ-R>System is busy with local traffic. Please try again later.

Dec 24 2020 16:36:57 +1100 EchoIRLP: playbackcomplete *SCOUT-VK* playback complete

Dec 24 2020 16:37:39 +1100 EchoIRLP: disconnected rtcp_timeout *SCOUT-VK* 0

Hmm, the conference attempted to reconnect when someone was using the repeater locally.



Dec 26 2020 21:25:40 +1100 decode: The command contains a bad digit (S,P,A,B,C,D)

Dec 26 2020 21:27:15 +1100 decode: DTMF = 9307

Dec 26 2020 21:27:20 +1100 Node Connected to reflector ref9300 on channel 7

Dec 26 2020 21:27:54 +1100 decode: DTMF = 73

Looks like someone is connecting you to 9307.  Possibly a pirate or misbehaving amateur?

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


 

On 30/12/20 8:59 pm, VK3AJ wrote:

Hi Tony,

 

Thanks for your review and feedback.

 

Looks like I need to investigate if something is disrupting the Internet connection.

 

Is there a setting that can be changed to stop connections from local RF?

Since our intention is for the node to be permanently connected to *SCOUT-VK* to allow Scouting contacts to call in via IRLP or Echolink, there is no need for local RF users to be able to initiate via DTMF locally.

Yes, you can tweak custom_decode to dump all DTMF codes, except for a select few (e.g. a command to enable DTMF).  Here's how I do it.  The following lines need to go near the top of custom_decode, before any other lines starting with if [ "$1"...


if [ "$1" = "12345S" ] ; then touch ${LOCAL}/nodtmf ; exit 1 ; fi
# Put any DTMF commands you want while DTMF is disabled in here
if [ -f ${LOCAL}/nodtmf ] ; then exit 1 ; fi
if [ "$1" = "12345P" ] ; then rm -f ${LOCAL}/nodtmf ; exit 1 ; fi
# rest of custom_decode follows.


What it does is looks for a 0 byte file in $LOCAL, and if it exists, aborts DTMF decoding.  You can do a number of things like reverse the logic (abort if the file doesn't exist), or you can have rc.irlp create run "touch ${LOCAL}/nodtmf" after enabling the node during startup

If you are 100% sure you'll never want to enable DTMF commands (think carefully here!), you could simply use:

exit 1

before any of the if statements.

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


Steve Jones
 

Tony,

   Quick correction for your code..  the “ rm -f $LOCAL/nodtmf… “  line has to go before the “if [ -f $LOCAL/nodtmf ]; then exit 1..” line as the removal will never happen as the exit will occur before it..

 

Steve  VK2YLD

   Node 6732

 

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Tony Langdon
Sent: Friday, 1 January 2021 8:31 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 30/12/20 8:59 pm, VK3AJ wrote:

Hi Tony,

 

Thanks for your review and feedback.

 

Looks like I need to investigate if something is disrupting the Internet connection.

 

Is there a setting that can be changed to stop connections from local RF?

Since our intention is for the node to be permanently connected to *SCOUT-VK* to allow Scouting contacts to call in via IRLP or Echolink, there is no need for local RF users to be able to initiate via DTMF locally.

Yes, you can tweak custom_decode to dump all DTMF codes, except for a select few (e.g. a command to enable DTMF).  Here's how I do it.  The following lines need to go near the top of custom_decode, before any other lines starting with if [ "$1"...

 

if [ "$1" = "12345S" ] ; then touch ${LOCAL}/nodtmf ; exit 1 ; fi
# Put any DTMF commands you want while DTMF is disabled in here
if [ -f ${LOCAL}/nodtmf ] ; then exit 1 ; fi
if [ "$1" = "12345P" ] ; then rm -f ${LOCAL}/nodtmf ; exit 1 ; fi
# rest of custom_decode follows.

 

What it does is looks for a 0 byte file in $LOCAL, and if it exists, aborts DTMF decoding.  You can do a number of things like reverse the logic (abort if the file doesn't exist), or you can have rc.irlp create run "touch ${LOCAL}/nodtmf" after enabling the node during startup

If you are 100% sure you'll never want to enable DTMF commands (think carefully here!), you could simply use:

exit 1

before any of the if statements.

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


 

On 1/1/21 9:40 am, Steve Jones wrote:

Tony,

   Quick correction for your code..  the “ rm -f $LOCAL/nodtmf… “  line has to go before the “if [ -f $LOCAL/nodtmf ]; then exit 1..” line as the removal will never happen as the exit will occur before it..

Thanks Steve.  I had to make some changes in the name of clarity and got it backwards.  Good catch. :)  Here's the corrected version.

if [ "$1" = "12345S" ] ; then rm -f ${LOCAL}/nodtmf ; exit 1 ; fi
# Put any DTMF commands you want while DTMF is disabled in here
if [ -f ${LOCAL}/nodtmf ] ; then exit 1 ; fi
if [ "$1" = "12345P" ] ; then touch ${LOCAL}/nodtmf ; exit 1 ; fi
# rest of custom_decode follows.

 

Steve  VK2YLD

   Node 6732

 

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Tony Langdon
Sent: Friday, 1 January 2021 8:31 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 30/12/20 8:59 pm, VK3AJ wrote:

Hi Tony,

 

Thanks for your review and feedback.

 

Looks like I need to investigate if something is disrupting the Internet connection.

 

Is there a setting that can be changed to stop connections from local RF?

Since our intention is for the node to be permanently connected to *SCOUT-VK* to allow Scouting contacts to call in via IRLP or Echolink, there is no need for local RF users to be able to initiate via DTMF locally.

Yes, you can tweak custom_decode to dump all DTMF codes, except for a select few (e.g. a command to enable DTMF).  Here's how I do it.  The following lines need to go near the top of custom_decode, before any other lines starting with if [ "$1"...

 

if [ "$1" = "12345S" ] ; then touch ${LOCAL}/nodtmf ; exit 1 ; fi
# Put any DTMF commands you want while DTMF is disabled in here
if [ -f ${LOCAL}/nodtmf ] ; then exit 1 ; fi
if [ "$1" = "12345P" ] ; then rm -f ${LOCAL}/nodtmf ; exit 1 ; fi
# rest of custom_decode follows.


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


DougH
 

A simple request --- if the subject matter is changed or should be made more representative of the actual subject can you please ammend the message subject accordingly and not highjack a previous post. There is little chance of anyone with the subject addressed with the above ever finding a solution provided herein! Think 'SEARCH' it might just be you!

D

On 01/01/2021 00:53, Tony Langdon wrote:
On 1/1/21 9:40 am, Steve Jones wrote:

Tony,

   Quick correction for your code..  the “ rm -f $LOCAL/nodtmf… “  line has to go before the “if [ -f $LOCAL/nodtmf ]; then exit 1..” line as the removal will never happen as the exit will occur before it..

Thanks Steve.  I had to make some changes in the name of clarity and got it backwards.  Good catch. :)  Here's the corrected version.

if [ "$1" = "12345S" ] ; then rm -f ${LOCAL}/nodtmf ; exit 1 ; fi
# Put any DTMF commands you want while DTMF is disabled in here
if [ -f ${LOCAL}/nodtmf ] ; then exit 1 ; fi
if [ "$1" = "12345P" ] ; then touch ${LOCAL}/nodtmf ; exit 1 ; fi
# rest of custom_decode follows.

 

Steve  VK2YLD

   Node 6732

 

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Tony Langdon
Sent: Friday, 1 January 2021 8:31 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Node Owner

 

On 30/12/20 8:59 pm, VK3AJ wrote:

Hi Tony,

 

Thanks for your review and feedback.

 

Looks like I need to investigate if something is disrupting the Internet connection.

 

Is there a setting that can be changed to stop connections from local RF?

Since our intention is for the node to be permanently connected to *SCOUT-VK* to allow Scouting contacts to call in via IRLP or Echolink, there is no need for local RF users to be able to initiate via DTMF locally.

Yes, you can tweak custom_decode to dump all DTMF codes, except for a select few (e.g. a command to enable DTMF).  Here's how I do it.  The following lines need to go near the top of custom_decode, before any other lines starting with if [ "$1"...

 

if [ "$1" = "12345S" ] ; then touch ${LOCAL}/nodtmf ; exit 1 ; fi
# Put any DTMF commands you want while DTMF is disabled in here
if [ -f ${LOCAL}/nodtmf ] ; then exit 1 ; fi
if [ "$1" = "12345P" ] ; then rm -f ${LOCAL}/nodtmf ; exit 1 ; fi
# rest of custom_decode follows.


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


Virus-free. www.avg.com