"Remote already in this mode" will only be heard if the telemetry message setting is allowed/active. A COP_34 (common to be function 934) will disable telemetry such as this, along with a whole list of other useful telemetry messages. The infamous COP_35 will allow telemetry messages for about a minute and suppress them afterwards. COP_33 turns all telemetry messaging back on. tnx Mike / W5JR Alpharetta GA
On Mar 28, 2017, at 11:17 AM, Benjamin L. Naber <benjamin@project23d.com> wrote:
There wasn't an echo, delay wasn't any more than normal and we were not using permalinks. I was able to create the same situation again using *3
odd to me that it kept repeating the connection status of a remote node that was *not* a part of the loop.
I elected to take it a step further and see if I could create a mesh between three nodes. I was successful. And it was a mess, haha!
~Benjamin, KB9LFZ
On Tue, 2017-03-28 at 13:38 +0000, Monty wrote: Benjamin,
Is there an echo, besides the normal delayed audio, in this scenario? Seems to me, reading through your logs, that's the nodes are trying to connect but not actually connected. I have seen something similar, but not in a loop, when dealing with permalinks. The other Node is not connecting, due to some sort of discrepancy, but in the "web link view" it shows them connected, even though they are not.
May be way off base, but that is what I have seen. Also the only way something would change is if you update it. I don't believe we have auto update, yet.
Monty
On Mon, Mar 27, 2017 at 7:52 PM Benjamin L. Naber <benjamin@project23 d.com> wrote:
Not sure that was necessary..
In any event, before the Allstarlink server(s) were reset about five days ago prior to today, if the following: 28569 <-> 41575 <-> 45222
and 28569 were to connect to 45297, and the end users on 45297 didn't know or pay attention that it was connected, and the user on 45297 tried connecting to 45222, the 45297 node would respond with "Remote already in this mode"
Now, it does not do that.
There was the possibility the possibly allstarlink wasn't aware of connections made when external node connections were made, if the external nodes connected were in the rpt.conf. However, prior to five days ago, the above scenario would be the same.
Something change? What changes are being made to warrant the allstarlink servers being reset (evidence being the unused nodes all have the same last ke-up time)
~Benjamin, KB9LFZ
On Mon, 2017-03-27 at 20:54 -0500, Justin Reed wrote: I always wondered what would happen if some dipshit did this.
Question answered ;)
73, Justin NV8Q
On 3/27/2017 8:14 PM, Benjamin L. Naber wrote: Uh, I was under the impression this wasn't possible, have a look at a the picture.
If I don't break the connection using the almight *4 command, as someone on the 45297 insists on using the permanent link command, have a look-see at my node, 28569
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-u sers
To unsubscribe from this list please visit http://lists.allstar link.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-use rs
To unsubscribe from this list please visit http://lists.allstarli nk.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink .org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. --
Monty _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.o rg/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.