From: Roger Harris (wodru@pandemicstudios.com)
Date: Sat Jan 13 2001 - 15:02:39 EET
Having only recently attempted to set up a Linux node, I find that the
method of calculating Netrom route qualities is somewhat inconsistent with
that the rest of the (non-linux) network.
After a quick trawl through the archives, I see that this has already been
mentioned:
On Mon, 9 Oct 2000, Stewart Wilkinson wrote:
> It has a problem with the handling of received NODES broadcasts,
> specifically it accepts and adds NODEs from a heard broadcast that, after
> the normal degrading have an effective quality lower than the worst
> quality for the port.
>
> Actually it processes any NODE that is broadcast by the neighbor at a
> quality value at or above the worst_qual defined for the port.
Tomi Manninen replied:
> The code currently compares the quality in the received broadcast against
> the worst_quality parameter and drops the route if needed and after that
> calculates the local quality.
> Now the spec is a bit unclear here but I agree that this behaviour is
> somewhat confusing and it would probably be better to change the
> behaviour.
Well, having playing with "The Net" and BPQ nodes for a number of years, I
can confirm that the normal behaviour of a node appears to be to calculate
the local quality first, and then to drop the route if the result is less
than the worst quality. In most cases, Sysops set worst_quality to 10,
which means that no node table should ever contain an entry with a quality
of less than 10.
If it is not done in this way, users can see nodes in the table which have
very little chance of ever working.
I hope this is helpful. I'm currently using the version of netromd from
ax25tool-0.0.6-24 which comes with the SuSE 7.0 distribution. Has there
been an update recently?
Many thanks
Roger
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to umi.igktsk@mfi-inkasso.de
This archive was generated by hypermail 2b30 : Sat Jan 13 2001 - 15:25:22 EET