[App_rpt-users] Any way to stop crossing to specific nodes?

[Bote Man]

As a newbie who has barely scratched the surface of understanding
Allstar, I find it next to impossible to trace every last node that is
connected together. 

I know there is the graphical node link list, and while it shows what
the possibilities are I find it too unwieldy for practical, regular use.

For example, I view Lu's node status web page and it might show 5 nodes
connected. I click on each one of those only to find a couple other
connections on each one. There must be an automated way to determine the
sum total of all nodes that happen to be connected together to form a
network at that instant. I just don't know what it is, if it even exists
now.

Being able to aggregate this information seems like the first step in
developing a watchdog that prevents ring-around-the-rosy loops.

That's my 0.000002 cents worth.


Bote, W4NUD
http://www.botecomm.com/bote/radio – my hobby radio pages
http://www.trackstreamer.com – my streaming scanner feeds
http://ialerts1.com – hobbyist incident alerting network w/maps



> -----Original Message-----
> From: Tony Langdon, VK3JED
> Sent: Monday, 29 August, 2011 19:18
> 
> At 04:03 AM 8/30/2011, Lu Vencl wrote:
> >I had an incident that occurred several nights ago where one user
> >unbenounced to him cross connected the WINSYSTEM and VOIPWX net
> >together in the middle of the night. No matter how many times I try
> >to explain this caution to users, they still on occasion make the
> >error as one of the distant node might be connected to another
> >network and it is not readily visible to the user of another node.
> >I would like to know if there are any provisions to help prevent
> >this from happening.
> 
> Is it possible to have the Echolink "CONF" flag set when connected to
> Echolink and some other system, or more than one Echolink node at the
> same time?  This will at least allow Echolink conferences with
> anti-conferencing measures to disconnect such accidental cross links
> automatically.  The best behaviour would be to emulate the behaviour
> of the Windows Echolink client in this respect.
> 
> 
> 73 de VK3JED / VK3IRL
> http://vkradio.com
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users