On Jun 7, 2020, at 15:16, Fred via groups.io <w5mgm=aol.com@groups.io> wrote:

To add to what David McAnally said once you set your DNS in /etc/resolv.conf run this command chattr +i /etc/resolv.conf This will lock the /etc/resolv.conf file down so the dns doesn’t change on you.

On Jun 6, 2020, at 23:44, Ramon Gandia <rfg8yg@xalaska.com> wrote:

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

On Jun 7, 2020, at 1:55 PM, David McAnally <David.McAnally@...> wrote:



That command should rarely take more than 2 seconds. I suggest checking your DNS or network performance. Use a fast DNS resolver, such as google (8.8.8.8) or quad9 (9.9.9.9). See /etc/resolv.conf

David M.

WD5M

On Sat, Jun 6, 2020 at 10:44 PM Ramon Gandia <rfg8yg@...> wrote:

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

On 6/6/20 8:44 PM, Ramon Gandia wrote:

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?

One would certainly want to make a note of it in the system logbook in
case the file needs to be edited in the future, but changing the file's
attributes to "immutable" would certainly accomplish the task. First
examine the existing attributes, make the change and then verify:

$ lsattr ~/scripts/ipupdate
--------------e---- ~/scripts/ipupdate
$ chattr +i ~/scripts/ipupdate
$ lsattr ~/scripts/ipupdate
----i---------e---- ~/scripts/ipupdate

Almost convinced that this isn't for beginners..
Nothing else seems to be working now..the APRS script, is still not functioning,  I have no audio coming back from the test server.

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.

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

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