| |
N1URO > NODES 10.04.05 02:54l 16 Lines 677 Bytes #999 (0) @ WW
BID : 35354_N1URO
Read: GUEST DK3HG DH8GHH
Subj: Re: #TMP netrom node entries
Path: DB0FHN<DB0RGB<DB0SL<DB0FSG<HB9EAS<HB9AJ<HB9AK<K1UOL<K1UOL<K2PUT<
N1URO
Sent: 050409/2031Z @:N1URO.#WMA.MA.USA.NOAM #:35354 [Springfield] $:35354_N1URO
From: N1URO@N1URO.#WMA.MA.USA.NOAM
To : NODES@WW
Those #TMP:xx#xxx nodes entries you see are what's known in the netrom
world as "slime trails". Slime nodes occur when a sysop of a netrom node
allows unlisted nodes to make netrom connects to it. Many node ops feel its
ok to allow slime node connects however as you pointed out, this is not really
good practice to do. In time, if the node does not connect through, they'll
eventually get dropped from the table you see them on.
Here in the northeast USA we don't permit slime trails in the few netrom
systems that are still up. Another way to eliminate such is to use FlexNet
which doesn't do netrom :)
73 de Brian N1URO
Read previous mail | Read next mail
| |
