I think it is time to make clear how the hop setting are working after
all. In fact, it is not very hard to understand.
1. The settings in the clx_par file are fallback values used when nothing
is specified for that specific link in the cluster_par file.
2. The settings are used ONLY for spots generated at your local site.
3. Hop counters in incoming spots (PC11) are decremented by one and then
sent on. I am currently not sure with which hop settings spots coming
from a user link are created.
These are the basic rules. This is how it works today with CLX 4.00.
The philosophy behind this was originally that we did not like to give
full control to a single node in the network about letting spots die
before they reach the peripheral parts of the network. This had been a
problem of the AK1A software in the past, where nodes on the edge of
the EU PacketCluster network did not receive any spots because someone
in front of them had reduced the hop counter to a small value. So they
did not see the spots at all.
On the other side we now have problems with loops and unmanagable
networks again due to some people not understanding or simply ignoring
the concepts. We get fed with (probably unwanted) spots from one side
and we can do nothing against it. Your node is even happily forwarding
them to the rest of the network.
73 Ben, DL6RAI (@work)
-- Bernhard Buettner - Systemmanagement, LFK-FTE4 Telefon: 089/607-26921 Email: xidz.elyzkozkh@floco2.com Fax: 089/607-22172