<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Chuck is correct. We have a weekly net on one of our hubs and there
is one node that connects to the hub for the net. It is attempting
to reconnect every 5 or 10 minutes. <br>
On most of the nodes that connect for the net we have set up the
telemetry for "timed telemetry" in the rpt.conf file.<br>
<br>
telemdefault=2 ; timed local telemetry<br>
<br>
This turns off the connection announcements during the net unless
you issue a command locally then the telemetry is enabled for about
5 minutes then goes silent.<br>
But not all of the nodes have this setting so those nodes will spew
out the "remote already in this mode" messages.<br>
<br>
It is very annoying. Unfortunately the telemetry setting is not the
fix but a band aid solution. <br>
<br>
In our case we know the offending node # but cant get a hold of the
owner to tell then to fix it. <br>
And on top of that they are connecting with a persistent connection
to the hub so we can t dump them at our end.<br>
<br>
I dont know what the problem with their node is unless they are
running some sort of script or cron job that does the reconnection
instead of the normal ilink commands for persistent connection.<br>
<br>
In the functions stanza:<br>
<br>
<br>
91=ilink,13 ; establish perm link to xxxx<br>
92=ilink,11 ; disconnect perm link xxxx<br>
<br>
So instead of using *3(NODE) to connect you would use *91(NODE) or
*92(NODE ) to disconnect a persistent link.<br>
*1(NODE) will not disconnect a persistent link, must use the *92 in
that case.<br>
<br>
<br>
If the perm connections are done using this method then there should
be no reconnection messages sent to all the other connected nodes.
The node will attempt to reconnect silently to keep a persistent
connection.<br>
<br>
hope this helps.<br>
<br>
Jon VA3RQ<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/4/2018 10:10 AM, Chuck Kraly
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEqnB0SBKV+_MM2+pVsfWATwkCxAh9ZbW-VL6RXLBZunPX3M9Q@mail.gmail.com">
<div dir="ltr">
<div>
<div>That is the telemetry message and indicates that
auto-connect or re-connect is on SOMEWHERE on your
connections. It is annoying as heck if you do not have
control over the node that is spewing it, and you have no
control over it. A hub we used to connect to did this all
the time and cannot re-connect due to this....our users
screamed about the messages...<br>
</div>
Chuck K0XM<br>
</div>
BYRG<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jan 4, 2018 at 9:06 AM, Bryan
Taylor <span dir="ltr"><<a href="mailto:overnite@me.com"
target="_blank" moz-do-not-send="true">overnite@me.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hopefully a quick question,<br>
<br>
For a few days now I have one allstar node playing the
“remote already in this mode” message about every 10
minutes. Anybody have any idea as to what could be causing
it or where I could look to see what is causing it? It never
did it before. I did add a new node to the network a few
days ago but I did add the new node to it’s nodes stanza. It
only connects to a hub node directly.<br>
<br>
There is nothing in the log files that points to anything.<br>
<br>
Google doesn’t find anything helpful either.<br>
<br>
Thanks<br>
Bryan<br>
Sent from my iPhone<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>