> Would you like the ability to totally control the way that pc frames
> leave your node. In other words, the default setting for a PC frame
> arriving in your node is to decrement this by 1 when passing it on,
> that is, if a PC frame arrives at you with a HOP of 10, you will
> send it on with a HOP of 9. Anything sent from your node locally is
> set to the HOP setting in your configuration. Would you like to be
> able to take in a PC frame and alter the HOP setting on the frame
> before passing it on? What do you see as the important factors in
> this?
It's a fact that clx nodes are tapping into cluster nets all around
the world, preferably with PCxx based links. These cluster nets
consist mainly of Pavilion cluster software. That software program
does not have the powerfull filtering features clx has. There are
some Pavilion sysops that are interested in receiving
PC10/11/12/16/17/19/21/23 originated in another region/continent and
don't want to forward those PCxx messages. This can't always be
setup with Pavilion. It could be when clx had total control of
outgoing HOPS.
> Does it worry you that a sysop could effectively decide who gets
> spots from his node with such a session, or do you see it as an
> advantage?
The disadvantage of total hop control can be that distant nodes will
not get your spots. Setting the correct values can prevent that ,
though.
73 de Aurelio-PA3EZL
terhi.victor@logonet.com