Date   
ipupdate script

Ramon Gandia
 

In the ~/scripts/ipupdate script there is a troublesome line:

NEWIPADDRESS=`${WGET} -q --timeout=2 -O- http://checkip.dyndns.org:8245 2>/dev/null \
| cut -d":" -f2 | cut -d" " -f2 | cut -d"<" -f1`

The problem is the --timeout=2 instance. With only 2 seconds grace period, the log gets
full of all sort of error messages. I changed it to 10 seconds, and that took care of it.

But of course, the script will soon be overwritten ... any way to gracefully get around this?

Ramon AL7X 3288 3289 7254

Re: ECHOIRLP assistance

David Cameron - IRLP
 

Couple of things about EchoIRLP
1) The password needs to be uppercase IN ALL CAPS in the tbd.conf file
2) Sometimes you need to wait a few minutes after its connected and installed before it starts to work.

You will get a lot of info by typing:

killall tbd

then:

tbd -ddd

The problem is EchoIRLP is no longer maintained. It was not written by IRLP, but we do what we can to help you get it running. As Debian moves forward, some scripts need changes in order to work. Those will need to be copied and supported by others and involve the use of SOX with deprecated arguments. This was discussed a few months ago.

Dave Cameron

On 2020-06-05 9:51 a.m., Rick Bates, NK7I wrote:
Chris,
"PC based node"?  The software being discussed in this group runs under a carefully limited operating system of linux, not Windows (just to be clear).
Not being logged into the echolink network is often the incorrect user and password OR not being registered within the network; check your config file(s) carefully, each must be EXACT.
Node not exists is a symptom of not being logged into the network OR it may be an incorrect command; does the command use a 'prefix', commonly an * (star)?
The (lack of) port opening (routing) may be another issue, but for the moment assume that they're open until the above is completed.
EchoIRLP works well, but to stop the constant random connects, no users speaking, I've limited my node to accepting only a few nodes from the echolink network.
[In the future, please add your call and node number to your signature when writing this group, so local specific help can be offered.  It's 'netiquette'.]
73,
Rick NK7I
7962
N ID
On 6/5/2020 9:38 AM, Chris Pitre wrote:
I appreciate the info, I 'm trying to do the install on a PC based node.

The Echolink node is not showing up the echolink user page ..nor does it let me connect to anything..says the node you are calling does not exist.

I have opened ports 5198 and 5199 on my router...I think.

This may be an easy process and perhaps im just overlooking the finest detail.

Re: ECHOIRLP assistance

Chris Pitre
 

Something is different between the new and the old box.

on the old box VE3TOM is on the echolink repeater list, on the new box it is not

The APRS script works

and the IRLP works.

and I hear audio

so that tells me that  something in the setup of the new box is not good.

The same ver 3 board is being used just moved from box to box.

Chris
VE3ZO

NODE 2803 

Re: ECHOIRLP assistance

Rick Szajkowski
 

That would narrow things down for sure , just make sure the ports are forwarded to the correct IP address on your lan , if both system have the same IP make sure that both are not on at the same time , would be better if the new one was not the same IP for testing ( or the old one ) 

I had a problem with Cogeco before I am now with eastlink with out problems 

Richard Szajkowski 
VA3 RZS VA3ZJ VE3BTE

On Jun 5, 2020, at 4:31 PM, Chris Pitre <ve3ctp@...> wrote:

Since I have the old computer still available I can plug it in and check to see if it works here, when the old computer was at the location it did in fact work.

IRLP
APRS Script 
and ECHOIRLP were fully functional

Re: ECHOIRLP assistance

Chris Pitre
 

Since I have the old computer still available I can plug it in and check to see if it works here, when the old computer was at the location it did in fact work.

IRLP
APRS Script 
and ECHOIRLP were fully functional

Re: ECHOIRLP assistance

Rick Szajkowski
 

Did it ever work ?? 

I would check with your ISP to see if anything changed , 

Good luck  

Richard Szajkowski 
VA3 RZS VA3ZJ VE3BTE

On Jun 5, 2020, at 4:01 PM, Chris Pitre <ve3ctp@...> wrote:

I live in Canada...my Inet provider is Cogeco, using an ARRIS router from them

Re: ECHOIRLP assistance

Chris Pitre
 

I live in Canada...my Inet provider is Cogeco, using an ARRIS router from them

Re: ECHOIRLP assistance

Allan Dunn, K1UCY
 

If your Internet is on Comcast, be aware they are implementing Advanced Security in some locations (like mine). If the Advanced Security under xFi is active, it has shut off your port forwarding. If you turn off Advanced Security by logging into your account and selecting xFi, there is an option to open port forwarding , but last time I tried it for my account, that feature did not work. The only option was to turn on DMZ on my router.  If you can still turn on port forwarding on your Comcast router, what I am writing does not (yet) apply to you. 


On Jun 5, 2020, at 2:00 PM, Chris Pitre <ve3ctp@...> wrote:

When I say PC based I mean that I am using a computer with an HDD not a raspPI.  I have Debian 10 installed on the HDD.

The prefix for ECHO IRLP is * 

I installed ECHOLink on the VE3III 2202 Node in Windsor many years ago on a computer based node using CentOS.

I never upgraded that to Debian and it works flawlessly.  The only reason for the upgrade on his node 2803 is purely due to the size of the old computer as compared to the new one.  The old one is a massive boatanchor.
The HDDS cannot be changed out due to the style of the connectors.



Chris
VE3ZO

IRLP 2803 VE3TOM repeater 
Leamington.ON

Re: ECHOIRLP assistance

Chris Pitre
 

When I say PC based I mean that I am using a computer with an HDD not a raspPI.  I have Debian 10 installed on the HDD.

The prefix for ECHO IRLP is * 

I installed ECHOLink on the VE3III 2202 Node in Windsor many years ago on a computer based node using CentOS.

I never upgraded that to Debian and it works flawlessly.  The only reason for the upgrade on his node 2803 is purely due to the size of the old computer as compared to the new one.  The old one is a massive boatanchor.
The HDDS cannot be changed out due to the style of the connectors.



Chris
VE3ZO

IRLP 2803 VE3TOM repeater 
Leamington.ON

Re: ECHOIRLP assistance

Rick NK7I
 

Chris,

"PC based node"?  The software being discussed in this group runs under a carefully limited operating system of linux, not Windows (just to be clear).

Not being logged into the echolink network is often the incorrect user and password OR not being registered within the network; check your config file(s) carefully, each must be EXACT.

Node not exists is a symptom of not being logged into the network OR it may be an incorrect command; does the command use a 'prefix', commonly an * (star)?

The (lack of) port opening (routing) may be another issue, but for the moment assume that they're open until the above is completed.

EchoIRLP works well, but to stop the constant random connects, no users speaking, I've limited my node to accepting only a few nodes from the echolink network.

[In the future, please add your call and node number to your signature when writing this group, so local specific help can be offered.  It's 'netiquette'.]

73,
Rick NK7I
7962
N ID

On 6/5/2020 9:38 AM, Chris Pitre wrote:
I appreciate the info, I 'm trying to do the install on a PC based node.

The Echolink node is not showing up the echolink user page ..nor does it let me connect to anything..says the node you are calling does not exist.

I have opened ports 5198 and 5199 on my router...I think.

This may be an easy process and perhaps im just overlooking the finest detail.


Re: ECHOIRLP assistance

Chris Pitre
 

I appreciate the info, I 'm trying to do the install on a PC based node.

The Echolink node is not showing up the echolink user page ..nor does it let me connect to anything..says the node you are calling does not exist.

I have opened ports 5198 and 5199 on my router...I think.

This may be an easy process and perhaps im just overlooking the finest detail.


Re: ECHOIRLP assistance

Craig - K1BDX - Node 8724
 

Here is another link for the embedded pi IRLP node

http://www.irlp.net/PiRLP4.html

On 6/5/20, Craig - K1BDX wrote:
Hi Chris.

I'm pretty sure that Dave Cameron's embedded pi node comes with
Echolink fully loaded and ready to go using Debian 10 on a raspberry
pi 4 computer. My understanding is that if you give him your echolink
info when you order it then he will set it up for you.

If I got any of this wrong, someone please jump in a correct me.

http://irlp.net/pi/



On 6/5/20, Chris Pitre <ve3ctp@...> wrote:
is there anyone that can assist with an ECHOIRLP installation for Debian
10
off list.

I don't think the group supports that software being installed on IRLP
computers.

IF it will not work with Debian, perhaps I can get assistance installing
CentOS, there is a message during the install process that it will not
get
past.

PCI 0 message.

Re: ECHOIRLP assistance

Chris Pitre
 

To be honest..I'm having difficulty installing anything on this..the aprs script will not work and I have no return audio from the test server.

I'm not well versed in Linux, however I recall setting up a CentOS IRLP system with aprs and Echoirlp many years ago and it seemed to go quite smoothly.

the trouble shoot script shows port 2093 still not open, however my router shows it is.


Re: ECHOIRLP assistance

Craig - K1BDX - Node 8724
 

Hi Chris.

I'm pretty sure that Dave Cameron's embedded pi node comes with
Echolink fully loaded and ready to go using Debian 10 on a raspberry
pi 4 computer. My understanding is that if you give him your echolink
info when you order it then he will set it up for you.

If I got any of this wrong, someone please jump in a correct me.

http://irlp.net/pi/

On 6/5/20, Chris Pitre <ve3ctp@...> wrote:
is there anyone that can assist with an ECHOIRLP installation for Debian 10
off list.

I don't think the group supports that software being installed on IRLP
computers.

IF it will not work with Debian, perhaps I can get assistance installing
CentOS, there is a message during the install process that it will not get
past.

PCI 0 message.



ECHOIRLP assistance

Chris Pitre
 

is there anyone that can assist with an ECHOIRLP installation for Debian 10 off list.

I don't think the group supports that software being installed on IRLP computers.

IF it will not work with Debian, perhaps I can get assistance installing CentOS, there is a message during the install process that it will not get past.

PCI 0  message.

Re: Experimental nodes

Craig - K1BDX - Node 8724
 

Craig - K1BDX - Node 8724 wrote:
So, if any of you were using ipxcore for a vpn or an experimental
reflector, I will be happy to help you move over to virmach.com [...]

On 6/4/20, Nosey Nick VA3NNW <irlp@...> wrote:
Forgive me for somewhat changing the subject, but it sounds like you'd
know... If someone wants to create a new special-purpose experimental
reflector from scratch, where is a good place to begin?
Hello, Nick.

An experimental reflector has to be run from a public IP address not
shared by any IRLP nodes. This usually rules out anyone putting a
reflector on their home internet unless multiple IPs are offered which
is not very common. So what we have been doing is renting a virtual
computer for $12.50 a year (a buck a month) which comes with its own
unique public IP address. There are two major parts to our
experimental reflectors, voice and activity lists. To simply
reflect voice packets you run a tiny little program called "sfreflect"
and you are done. If you also want a list of who is keying up the
reflector and another list showing who is listening to the reflector,
I wrote some scripts to handle that. You can see an example at these
links:

http://107.175.123.72/Chan_Zero_Node_Numbers.html

http://107.175.123.72/channel_0.html

So far we have built 9 experimental reflectors and you see a list of
them and others at this link

http://experimental.irlp.net/

If you want to have a reflector of your own, the easiest thing to do
is rent a virtual computer at virmach.com and select Debian 9 as the
operating system and they will email you a confirmation with the IP
address and the temporary root password. If you forward the IP and
the password to me, I will log in and load it up with a reflector for
you. If you just want to talk on your reflector then you are done.
However, if you are like me and you want to mess around with the
software then just keep a few copies of the original software and then
play around to your heart's content. If you mess anything up then you
simply rebuild the virtual debian 9 operating system with the push of
a button which wipes away any previous software and then upload your
copy of your reflector software and you are back in business.

Re: Experimental nodes

David Cameron - IRLP
 

As this is one way communications, there is no reason why you could not just run this from the PiRLP node, or another computer behind its same router. A TCP dump watcher could catch the connection and IP, and then a process could use imike to just stream the file to the end user.

For the DNS name, just use

stn1234.ip.irlp.net (replace 1234 with your node number)

This would not even affect your node in operation in any way, as the ispeaker process is filtered to the IP it is connected to....

It would be easier to use a separate IP, but it could be done without.

Dave Cameron

On 2020-06-04 4:59 p.m., Nosey Nick VA3NNW wrote:
Craig - K1BDX - Node 8724 wrote:
So, if any of you were using ipxcore for a vpn or an experimental
reflector, I will be happy to help you move over to virmach.com [...]
Forgive me for somewhat changing the subject, but it sounds like you'd
know... If someone wants to create a new special-purpose experimental
reflector from scratch, where is a good place to begin?
I'm very familiar with Linux, scripting, coding, and I do cloud
computing stuff for my day job. I have a PiRLP node, and know my way
around most of it. I have written a weather-bot script for my node which
reads out a short local weather report approx every hour in a very
polite voice (approx Alexa-like). I was considering extending it to
offer it to others in the form of an experimental node. Theory is they
could cron a "$SCRIPT/connect_to_reflector BLAH", my reflector would
check a cache / do a quick lookup of their node's LatLon, feed it into
the weather API I'm already using, and prepare and read back THEIR
weather instead of just mine.
... so where would I start?
Thanks!
Nick

Experimental nodes

Nosey Nick VA3NNW
 

Craig - K1BDX - Node 8724 wrote:
So, if any of you were using ipxcore for a vpn or an experimental
reflector, I will be happy to help you move over to virmach.com [...]
Forgive me for somewhat changing the subject, but it sounds like you'd
know... If someone wants to create a new special-purpose experimental
reflector from scratch, where is a good place to begin?

I'm very familiar with Linux, scripting, coding, and I do cloud
computing stuff for my day job. I have a PiRLP node, and know my way
around most of it. I have written a weather-bot script for my node which
reads out a short local weather report approx every hour in a very
polite voice (approx Alexa-like). I was considering extending it to
offer it to others in the form of an experimental node. Theory is they
could cron a "$SCRIPT/connect_to_reflector BLAH", my reflector would
check a cache / do a quick lookup of their node's LatLon, feed it into
the weather API I'm already using, and prepare and read back THEIR
weather instead of just mine.

... so where would I start?

Thanks!
Nick

--
"Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209.
use Std::Disclaimer; sig@...
Stalinism begins at home. -- Tom Neff

moderated Re: Is IPXcore dot com gone forever?? Two months early? What?

Teton Amateur Radio Repeater Association (TARRA)
 

I just thought I would pass this along that I got this afternoon:

Hello,

The recent outage was due to a mistake at our data center. The VPS serves are still set to be discontinued on July 31st.

Mick - W7CAT
Node 3464


----- Original Message -----
From: "Teton Amateur Radio Repeater Association (TARRA)"
To: IRLP@irlp.groups.io
Sent: Tuesday, June 02, 2020 06:57:51 PM
Subject: Re: [IRLP] Is IPXcore dot com gone forever?? Two months early? What?

>
> I sent an email to the three email addresses that I have for ipxcore and let them know my displeasure for shutting down two months earlier than they said they were going to. This afternoon everything is back up and running again!
>
> Mick - W7CAT Node 3464 ----- Original Message ----- From: Craig - K1BDX - Node 8724 To: IRLP@irlp.groups.io Sent: Monday, June 01, 2020 01:24:59 PM Subject: [IRLP] Is IPXcore dot com gone forever?? Two months early? What? > As far as I can tell, Ipxcore.com is gone forever. > > They were warning us that they were going out of business on July 31st > but it looks like everything stopped working yesterday May 31st. Not > very sporting of those old boys, eh? > > So, if any of you were using ipxcore for a vpn or an experimental > reflector, I will be happy to help you move over to virmach.com for > $12.50 a year > > Also, Dave Cameron, the experimental reflector list at > experimental.irlp.net has also vanished into internet oblivion, > however I have been planning for this event and the list is now on a > virmach maching at this IP address. At your convenience, please > reassign the subdomain experimental.irlp.net to this ip address > 172.245.36.230 > > Thanks! > > Before Dave Cameron makes that happen you can always access the > experimental list by its raw ip address here: > > > http://172.245.36.230/ > > > >
> --
>
> ? >
--

 

0

Re: IRLP with TheBridge EchoLink Conference Server

 

On 04/06/20 12:31, VK3AJ wrote:
Thanks for your response and info Dave, but it looks like Milt's was on the money.
Changed the REFLECTOR_TIMEOUT_VALUE to 0 and it's been up now for an 1 1/2 hours.
Yep, that should sort your issue.  A couple of other tips, if you want
to avoid accidentally "camping" on another Echolink conference or reflector:

1.  You could set the reflector timeout to the expected duration of
connections (good if you're doing regular nets).  For example, for a 2
hour net, set the timeout to 7200.

2.  If using DTMF to connect, you could setup a custom_decode entry to
connect that uses the "notimeout" parameter.  This would also allow you
to have a shorthand DTMF code, instead of having to key in the full
prefix+node number.  This also applies if you use "decode" over SSH to
make the connection.

3.  Alternatively, you could use echo_call directly with the optional
notimeout parameter from the command line.

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