At PA3GOJ-8 we did some tests regarding clx's HOP control per link. Here's what
we found:
Situation: three links, A=passive_clx_pcxx, B=passive_clx_pcxx,
C=passive_non-clx_user
In clx_par: dx/10 wwv/10 etc..
in cluster_par: dx/1 wwv/1 etc.. for all three links
Action: incoming "DX de" on the user link C. CLX converts the line into PC11
and sends it to link A and B with HOP=9
incoming PC11 (e.g. HOP 34) on link A. CLX forwards the spot to link B
with HOP 33.
Generated DX spot by LOCAL user. PC11 spot is send to link A and B with
HOP 1.
Conclusion. Incoming hops from user link are send to (active) clx links with
HOPS = HOP-1 of dx/# setting in clx_par file.
Incoming hops on protocol link are forwarded with HOP-1 regardless settings in
clx_par or cluster_par
Locally generated spots are send according settings in cluster_par
Wonder if any of you have the same experiences.. ? I have the feeling something
is not working as it should.
73 de Aurelio-PA3EZL
ejf.suwz@netstarnetworks.com