Date   

Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

At 12/6/2018 03:12 PM, you wrote:
That case addition to your existing script looks good to me! :)Â

And it is good: connects to exp nodes now.

Thanks to everyone for their suggestions.

Bob NO6B


Re: Newsline on reflector 0016

 

Wait a minute... when you type bash -x scriptname what are you typing for scriptname?


>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Thursday, December 6, 2018, 7:15:02 PM EST, Dave Parks - WB8ODF via Groups.Io <wb8odf@...> wrote:


If you're using putty Highlight what you want and hit Control-C then you can paste it in wordpad or right here in email by hitting Control-V I'm mostly interested in the end of the debug output. 


>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Thursday, December 6, 2018, 7:10:07 PM EST, Dan Sellmeyer <dsellmeyer@...> wrote:


Dave

The way I play newsline here has always been just to connect to reflector 0016 and it plays. I tryed the bash -x decode 0016 and got connected with lots of stuff
showing across the screen. Trying to figuer out a way to copy and paste the text but can't seem to for some reason.


Re: Newsline on reflector 0016

 

If you're using putty Highlight what you want and hit Control-C then you can paste it in wordpad or right here in email by hitting Control-V I'm mostly interested in the end of the debug output. 


>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Thursday, December 6, 2018, 7:10:07 PM EST, Dan Sellmeyer <dsellmeyer@...> wrote:


Dave

The way I play newsline here has always been just to connect to reflector 0016 and it plays. I tryed the bash -x decode 0016 and got connected with lots of stuff
showing across the screen. Trying to figuer out a way to copy and paste the text but can't seem to for some reason.


Re: Newsline on reflector 0016

Dan Sellmeyer <dsellmeyer@...>
 

Dave

The way I play newsline here has always been just to connect to reflector 0016 and it plays. I tryed the bash -x decode 0016 and got connected with lots of stuff
showing across the screen. Trying to figuer out a way to copy and paste the text but can't seem to for some reason.


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

At 12/5/2018 11:14 PM, you wrote:
Bob,

Do you think there is any chance the environment file was ever edited with WIN SCP or some other non-Linux editor?
If so, then it's possible the Windows end-of-line sequence (CR-LF) made it into the environment file.
This is different than the Linux (Newline) which is actually just a single LF and you can't always see it.
This has caused strange problems for folks, but is fairly rare.
For this reason I usually try to edit node files directly on the target system using pico but I also use win32pad, which auto-detects the Unix LF-only text format & preserves it when editing.

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

 

That case addition to your existing script looks good to me! :) 


>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Thursday, December 6, 2018, 6:08:54 PM EST, no6b@... <no6b@...> wrote:


At 12/6/2018 12:12 AM, you wrote:
I have a custom_decode file as well.
It does several things, but that's not where the experimental-node vs station decision is made.

Actually I think it is, as there is a section near the bottom that differentiates between reflectors & nodes:

      # Decode Node Connections
      #
      # Whenever a connect command completes successfully,
      # the processing is terminated; otherwise, the command
      # is further processed for forwarding to the remote
      # node (if connected).
      #
      case ${CMD} in                        # Process the COMMAND
        9*)                                  # Connect to reflector
          $ECHO "Connecting to reflector."
          if ${SCRIPT}/connect_to_reflector ref${CMD} ; then
            exit 1
          fi
          ;;
        *)                                   # Connect to node
          $ECHO "Connecting to node."
          if ${SCRIPT}/call stn${CMD} ; then
            exit 1
          fi
          ;;
      esac

I'm not good at bash, but it seems to me that this code would use 'call' to call experimental nodes when in fact 'experimental_call' needs to be used.

I think the answer is to insert the following case above the '*' case:

        0*)                             # Connect to experimental node

          $ECHO "Connecting to experimental node."
          if ${SCRIPT}/experimental_call exp${CMD} ; then
            exit 1
          fi
          ;;

I'm not in a position to test it right now but will let you know when I do.

Thanks

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

At 12/6/2018 12:12 AM, you wrote:
I have a custom_decode file as well.
It does several things, but that's not where the experimental-node vs station decision is made.

Actually I think it is, as there is a section near the bottom that differentiates between reflectors & nodes:

      # Decode Node Connections
      #
      # Whenever a connect command completes successfully,
      # the processing is terminated; otherwise, the command
      # is further processed for forwarding to the remote
      # node (if connected).
      #
      case ${CMD} in                      # Process the COMMAND
        9*)                                # Connect to reflector
          $ECHO "Connecting to reflector."
          if ${SCRIPT}/connect_to_reflector ref${CMD} ; then
            exit 1
          fi
          ;;
        *)                                 # Connect to node
          $ECHO "Connecting to node."
          if ${SCRIPT}/call stn${CMD} ; then
            exit 1
          fi
          ;;
      esac

I'm not good at bash, but it seems to me that this code would use 'call' to call experimental nodes when in fact 'experimental_call' needs to be used.

I think the answer is to insert the following case above the '*' case:

        0*)                             # Connect to experimental node
          $ECHO "Connecting to experimental node."
          if ${SCRIPT}/experimental_call exp${CMD} ; then
            exit 1
          fi
          ;;

I'm not in a position to test it right now but will let you know when I do.

Thanks

Bob NO6B


Re: Newsline on reflector 0016

 

I have a couple of questions Dan.

1). What are you using to get and play the news?

2). Is it downloading a file but seems to be the same one?

3). If it's NOT downloading are you seeing any error messages?

I'm thinking this is one of two things. Either you're getting (or trying to get) the wrong file at the wrong URL. Square Space moved the news.mp3 a while back.

Secondly Your wget command might be having a certificate issue. We went over that a few weeks back.

Can you run your script in debug mode and post your output? 

As user repeater type: bash -x "name of your script"



>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Thursday, December 6, 2018, 5:33:18 PM EST, Dan Sellmeyer <dsellmeyer@...> wrote:


I have searched the forms and looks like I am not the only one having problems with newsline.
I can connect to the reflector but the Newsline feed is way out of date from like last June this year.
Anyone know why its not getting updated ?

Thanks


Newsline on reflector 0016

Dan Sellmeyer <dsellmeyer@...>
 

I have searched the forms and looks like I am not the only one having problems with newsline.
I can connect to the reflector but the Newsline feed is way out of date from like last June this year.
Anyone know why its not getting updated ?

Thanks


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

David Cameron - IRLP
 

Whatever the custom decode script is doing where it strips the dtmf is the problem. Looks like quotes are being added which is affecting the way the decode script interprets the code. 

Post the lines of your custom decode script where the received / stripped is processed 

Dave Cameron 



Sent from my Bell Samsung device over Canada's largest network.

-------- Original message --------
From: no6b@...
Date: 12/5/18 11:31 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

At 12/5/2018 11:14 PM, you wrote:
Bob,
IRLP wants to make sure you are using the latest version of released software, so this automatic replacement is normal.
There is a way around this, but if the code were bad, it would be bad for everyone so I don't think it's your problem.
Do you think there is any chance the environment file was ever edited with WIN SCP or some other non-Linux editor?
If so, then it's possible the Windows end-of-line sequence (CR-LF) made it into the environment file.
This is different than the Linux (Newline) which is actually just a single LF and you can't always see it.

Doubt that's the problem, as it should affect other settings as well.  But I'll check it with a binary viewer.

Another question. Can you look at the IRLP messages file to tell us what the exact error messages are?
Imediatly after an experimental node connect attempt (and failure), try typing:
tail /home/irlp/log/messages
and show us the output.
That should tell us more precisely what is happening.

Dec 05 2018 22:48:14 -0800 decode: DTMF = 80070
Dec 05 2018 22:48:15 -0800 custom_decode: Received DTMF = "80070"
Dec 05 2018 22:48:15 -0800 custom_decode: Stripped/Translated DTMF = "80070"
Dec 05 2018 22:48:15 -0800 IRLP call initiated to stn0070
Dec 05 2018 22:48:16 -0800 noexist

Looks like the problem is the call to stn0070 instead of exp0070.

Maybe I need to make that decode script read-only so it doesn't get overwritten?

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Andy KB7B
 

I just tried adding a security prefix of 8 to my node and I was still able to connect to an experimental reflector.
It does appear something is going on in your custom_decode file though.


-Andy


From: "no6b@..." <no6b@...>
To: IRLP@irlp.groups.io
Sent: Thursday, December 6, 2018 4:32 PM
Subject: Re: [IRLP] Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

At 12/5/2018 11:14 PM, you wrote:
Bob,
IRLP wants to make sure you are using the latest version of released software, so this automatic replacement is normal.
There is a way around this, but if the code were bad, it would be bad for everyone so I don't think it's your problem.
Do you think there is any chance the environment file was ever edited with WIN SCP or some other non-Linux editor?
If so, then it's possible the Windows end-of-line sequence (CR-LF) made it into the environment file.
This is different than the Linux (Newline) which is actually just a single LF and you can't always see it.

Doubt that's the problem, as it should affect other settings as well.  But I'll check it with a binary viewer.

Another question. Can you look at the IRLP messages file to tell us what the exact error messages are?
Imediatly after an experimental node connect attempt (and failure), try typing:
tail /home/irlp/log/messages
and show us the output.
That should tell us more precisely what is happening.

Dec 05 2018 22:48:14 -0800 decode: DTMF = 80070
Dec 05 2018 22:48:15 -0800 custom_decode: Received DTMF = "80070"
Dec 05 2018 22:48:15 -0800 custom_decode: Stripped/Translated DTMF = "80070"
Dec 05 2018 22:48:15 -0800 IRLP call initiated to stn0070
Dec 05 2018 22:48:16 -0800 noexist

Looks like the problem is the call to stn0070 instead of exp0070.

Maybe I need to make that decode script read-only so it doesn't get overwritten?

Bob NO6B



Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Andy KB7B
 

I have a custom_decode file as well.
It does several things, but that's not where the experimental-node vs station decision is made.
You just want to make sure there's nothing that might grab the 00xx codes and do something else with them.


-Andy


From: "no6b@..." <no6b@...>
To: IRLP@irlp.groups.io
Sent: Thursday, December 6, 2018 4:56 PM
Subject: Re: [IRLP] Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

I think I found the problem: we have a custom_decode file & it doesn't have the code to distinguish exp nodes from stns.  However when I tried to change stn to exp in that file I got a "nopgpkey" error in the log when attempting a connection.

?!

Bob NO6B



Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Andy KB7B
 

Are you using a security prefix of 8 for your node?

-Andy


From: "no6b@..." <no6b@...>
To: IRLP@irlp.groups.io
Sent: Thursday, December 6, 2018 4:56 PM
Subject: Re: [IRLP] Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

I think I found the problem: we have a custom_decode file & it doesn't have the code to distinguish exp nodes from stns.  However when I tried to change stn to exp in that file I got a "nopgpkey" error in the log when attempting a connection.

?!

Bob NO6B



Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

I think I found the problem: we have a custom_decode file & it doesn't have the code to distinguish exp nodes from stns.  However when I tried to change stn to exp in that file I got a "nopgpkey" error in the log when attempting a connection.

?!

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

At 12/5/2018 11:14 PM, you wrote:
Bob,
IRLP wants to make sure you are using the latest version of released software, so this automatic replacement is normal.
There is a way around this, but if the code were bad, it would be bad for everyone so I don't think it's your problem.
Do you think there is any chance the environment file was ever edited with WIN SCP or some other non-Linux editor?
If so, then it's possible the Windows end-of-line sequence (CR-LF) made it into the environment file.
This is different than the Linux (Newline) which is actually just a single LF and you can't always see it.

Doubt that's the problem, as it should affect other settings as well.  But I'll check it with a binary viewer.

Another question. Can you look at the IRLP messages file to tell us what the exact error messages are?
Imediatly after an experimental node connect attempt (and failure), try typing:
tail /home/irlp/log/messages
and show us the output.
That should tell us more precisely what is happening.

Dec 05 2018 22:48:14 -0800 decode: DTMF = 80070
Dec 05 2018 22:48:15 -0800 custom_decode: Received DTMF = "80070"
Dec 05 2018 22:48:15 -0800 custom_decode: Stripped/Translated DTMF = "80070"
Dec 05 2018 22:48:15 -0800 IRLP call initiated to stn0070
Dec 05 2018 22:48:16 -0800 noexist

Looks like the problem is the call to stn0070 instead of exp0070.

Maybe I need to make that decode script read-only so it doesn't get overwritten?

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Andy KB7B
 

Bob,

IRLP wants to make sure you are using the latest version of released software, so this automatic replacement is normal.
There is a way around this, but if the code were bad, it would be bad for everyone so I don't think it's your problem.

Do you think there is any chance the environment file was ever edited with WIN SCP or some other non-Linux editor?

If so, then it's possible the Windows end-of-line sequence (CR-LF) made it into the environment file.
This is different than the Linux (Newline) which is actually just a single LF and you can't always see it.
This has caused strange problems for folks, but is fairly rare.

Another question. Can you look at the IRLP messages file to tell us what the exact error messages are?
Imediatly after an experimental node connect attempt (and failure), try typing:

tail /home/irlp/log/messages

and show us the output.
That should tell us more precisely what is happening.


-Andy


From: "no6b@..." <no6b@...>
To: IRLP@irlp.groups.io
Sent: Thursday, December 6, 2018 3:57 PM
Subject: Re: [IRLP] Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

OK I think I found the problem: a typo in the decode script:

${SCRIPT}/experimental_call exp"${CMD}"

whereas normal codes are called using

${SCRIPT}/call "stn${CMD}"

So I think the 1st line should read

${SCRIPT}/experimental_call "exp${CMD}"

I edited the suspect line with pico (as su) saved it, then cat'd it to make sure I did save it.  Then I run rc.irlp, but after running that the original script file is restored so my edit is overwritten.  So the problem remains.

Bob NO6B



Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

OK I think I found the problem: a typo in the decode script:

${SCRIPT}/experimental_call exp"${CMD}"

whereas normal codes are called using

${SCRIPT}/call "stn${CMD}"

So I think the 1st line should read

${SCRIPT}/experimental_call "exp${CMD}"

I edited the suspect line with pico (as su) saved it, then cat'd it to make sure I did save it.  Then I run rc.irlp, but after running that the original script file is restored so my edit is overwritten.  So the problem remains.

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

At 12/5/2018 08:53 PM, you wrote:
Bob,
Two more thoughts.
1. After changing anything in the /home/irlp/custom/environment file,
(including export ALLOW_EXPERIMENTAL_NODES=YES)
be sure to reboot the node or run /home/irlp/custom/rc.irlp
so the changes take effect.

As I mentioned previously, this was changed many years ago so I'm certain the node has been rebooted many times with this change in place.  However, it has never worked.  I haven't pursued the issue until now because up to this point I had no pressing need to connect to an experimental reflector.

2. It's also possible you are just having a DTMF issue.
You can test this by running the readinput program
as user "repeater".
Then key a radio and press some DTMF keys.
You should see COS ACTIVE when the radio is keyed
as well as any DTMF presses that are decoded followed by
COS INACTIVE when the transmitter un-keys.
Be sure the DTMF 0 is decoded reliably.
Typing a <Ctrl-C> will exit the readinput program
and bring you back to a $ prompt.

DTMF is decoding fine, but still not able to connect.

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Bob Dengler
 

At 12/5/2018 08:07 PM, you wrote:
No, that date should be fine.
Mine is 4053 bytes in size.
A couple more things to check...
Are you using a DTMFPREFIX in the /home/irlp/custom/environment file for security?
If so, I believe you still need to enter it before connecting to an experimental node.

Yes, prefix is 8; tried with & w/o.

Are you running EchoIRLP on the node?
If so, what prefix are you using for Echolink connects?

A, though I don't know if EchoIRLP is enabled.  We've had problems with it in the past & I don't consider it an essential feature.

Bob NO6B


Re: Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

Andy KB7B
 

Bob,

Two more thoughts.

1. After changing anything in the /home/irlp/custom/environment file,
(including export ALLOW_EXPERIMENTAL_NODES=YES)
be sure to reboot the node or run /home/irlp/custom/rc.irlp
so the changes take effect.

2. It's also possible you are just having a DTMF issue.
You can test this by running the readinput program
as user "repeater".

Then key a radio and press some DTMF keys.
You should see COS ACTIVE when the radio is keyed
as well as any DTMF presses that are decoded followed by
COS INACTIVE when the transmitter un-keys.
Be sure the DTMF 0 is decoded reliably.

Typing a <Ctrl-C> will exit the readinput program
and bring you back to a $ prompt.


-Andy


From: "no6b@..." <no6b@...>
To: IRLP@irlp.groups.io
Sent: Thursday, December 6, 2018 12:59 PM
Subject: Re: [IRLP] Trouble connecting to experimental reflectors (yes I set export ALLOW_EXPERIMENTAL_NODES=YES in environment)

At 12/5/2018 07:30 PM, you wrote:
Bob,
Check to see if you have the file /home/irlp/scripts/exp-x-reference
This is where the experimental nodes seem to be defined.
-Andy KB7B

Thanks Andy.  Yes we have that file, dated Oct. 6 2018.  Is it too stale?

Bob NO6B


4081 - 4100 of 78931