|
N1URO > SYSOP 10.10.16 16:40l 55 Lines 1964 Bytes #999 (0) @ WW
BID : 28156_N1URO
Read: GUEST
Subj: Re: ghost nodes
Path: IW8PGT<IZ3LSV<IK6ZDE<VE2PKT<N1URO
Sent: 161010/1531Z @:N1URO.#CCT.CT.USA.NOAM #:28156 [Unionville] $:28156_N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : SYSOP@WW
Hello Jean et al;
Ghost nodes occur from those locking their netrom routes, reloading stale
saved netrom tables, or perhaps from the excessive ping ponging of INP3
nodes which do not follow NetRom detrating standards (but gladly uses such
as a transport). Another reason why this may be occurring (as you stated) is
NetRom links set a too high of a quality and stations broadcasting tables
stating that they physically host their neighbor nodes on their own lan.
This has been an issue since the beginning of axip linking (axudp came many
years later). I still see my old nodes from 10 years ago still being
propagated out within the INP3 cloud. Lowering NetRom neighbor link quality
is half of what a sysop can do... but also raising min_obs and
worst_qual can help filter some of the underlaying nodes even ghost nodes
within the INP3 cloud from showing on your node.
My strong suggestion is the following:
For RF based NetRom nodes:
DefQual: 203
Min_Obs: 3
Dev_Obs: 5
WorstQl: 50
For axip based NetRom nodes:
DefQual: 203
Min_Obs: 4
Def_Obs: 5
WorstQl: 181
For INP3 Neighbors:
DefQual: 128
Min_Obs: 4
Def_Obs: 5
WorstQl: 127
We can't control what others do but we can control what we do. A schema of this
which I've tested well for over 3 years now does what should be done. We as
sysops must remember that it's not the number of nodes we carry that defines
us as a station, it's the integrity of those nodes we do carry that the end
user wants us to deliver. Offering end users nodes that don't exist anymore
is of no integrity, and presents your node as a non-functional node to them.
Users talk amongst themselves, so if they say to each other that your node
doesn't work, you'll lose servicing those users and they'll go elsewhere -
especially straight internet!
I may post a little something on this at:
https://www.eastnetpacket.org
73 de N1URO
EastNet Engineer and node developer of URONode
Read previous mail | Read next mail
| |