[App_rpt-users] Quick question on usability

Jim Duuuude telesistant at hotmail.com
Tue May 29 13:13:27 EDT 2012

No, normally (non-command) initiated ID's are always local.

The problem you are (most likely) seeing is that the command (the *80) in this case is getting
re-distributed to all connected nodes in the normal manner, even though the link(s)
is(are) connected in monitor-only mode.

Darn you for finding a design flaw!! :-)

I will attempt to verify that locally-initiated commands on a monitor-connected link
get distributed. If they do, they wont for long.. :-)


From: adamson_alan at hotmail.com
To: App_rpt-users at ohnosec.org
Date: Tue, 29 May 2012 13:06:25 -0400
Subject: [App_rpt-users] Quick question on usability

Quick question on usability

I don't want to be a bad operator at the moment… As I go about checking bandwidth and jitter, etc on my setup… I'd like to connect to an active Hub, but just in eavesdrop mode.

But I've noticed that if I connect with the *2 command, that if I inadvertently then do a *80, that the ID goes out on the link that was connected with the *2.

Is this true anytime my node decides to ID?


App_rpt-users mailing list
App_rpt-users at ohnosec.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20120529/fda6aa80/attachment.html>

More information about the App_rpt-users mailing list