| |
W0RLI > NODES 11.04.05 05:20l 81 Lines 3288 Bytes #999 (0) @ WW
BID : 2D51W0RLI
Read: GUEST DK3HG DH8GHH
Subj: Re: #TMP netrom node entries
Path: DB0FHN<DB0MRW<DB0FSG<HB9EAS<HB9AK<K1UOL<N7QDN<n7qdn<ka7agh<w0rli
Sent: 050411/0023 11602@w0rli.or.usa.noam
These are normal internal entries created by some of the *NOS
software. They mark the node entry as temporary. This might occur
for example if you cleared your node list so as to allow it to rebuild
Each connect from a remote node that has not yet been heard about
in a node broadcast will result in one such entry. These entries are
normally given a route quality of zero, and are never broadcast.
You will see markers other than #TMP (e.g. #TEMP, ######,
or no alias at all) depending on the particular version of *NOS.
If you see these in a node broadcast, contact the station involved
and tell them to shut down, there software is seriously broken.
Oh, wait ... you are talking about Land Line Lid connections!
Of course they are all screwed up. The folks that did the software
to route NET/ROM over IP / UDP appear to have no clue how
the NET/ROM protocol works. Take a cudgel to them.
--
... Hank
http://home.earthlink.net/~horedson
http://home.earthlink.net/~w0rli
<G0SYR@GB7CIP.#32.GBR.EU> wrote in message news:32687G0SYR...
> T:From: g0syr <g0syr@gb7cip.ampr.org>
> T:Newsgroups: ampr.packet.nodes
> T:Message-Id: <epp60hj6qyy1$.7k2rq5rfmz0i$.dlg@40tude.net>
>
> Hi All,
>
> I wonder if anyone has noticed these node table entries that I
> captured on my local netrom node this morning
>
>
> #TMP:G0MBA-1 #TMP:VK4TTT-14 #TMP:GM0FTJ-4 #TMP:G7BUG-9
> #TMP:N0LBA #TMP:ZL1BQ-14 #TMP:GB7BED-8 #TMP:GB7BED-9
> #TMP:IK5CKL-14 #TMP:G7DIR-2 #TMP:GB7DID #TMP:M1CMN-2
> #TMP:G8PZT #TMP:GB7SYP-1 #TMP:ZL2AQY-2 #TMP:ZL2AL-2
> #TMP:ZL2AQY-10 #TMP:GB7WE
>
> Now I have seen a few of these before but not looked into
> the matter. Does anyone know how these entries are created
> and where they might come from ??
>
> They are very annoying as they reduce the apparent
> reliability of the network as while they exist they
> overwrite the valid entries so a normal request to
> connect to 'KIDDER' for example results in a
> 'no such node' response even though a connect to
> G8PZT will still connect ok.
> I'm not sure how long these corrupt entries will last in
> the table. It is hard to track the source as because of
> the way netrom works I suspect that nodes broadcasts
> from the genuine node correct the entries each hour
> but those corrections take several hours to be passed
> around the network so if I visit other neighbouring
> nodes I see a seeming random occurence of these entries
> with no real idea of where they entered the network.
>
> While writing this I wonder if there could be a version
> of node software out there that might give those tempory
> entries that are created when a distant 'unknown' node
> makes a connection and creates those tempory entries that
> usually appear at the top of the table without a name.
> I wonder if software could exist that actually gives those
> entries a tempory name of #TMP and then sends them out out
> in its nodes broadcasts to overwrite the genuine name on
> the network.
>
> I'd be interested in anyone elses thoughts or observations
> as it would be good to find a fix for this problem.
>
>
> --
> 73 de Bryan g0syr.ampr.org [ 44.131.244.60 ]
> Amprnet mail g0syr@gb7cip.ampr.org
> AX25 mail G0SYR@GB7CIP.#32.GBR.EU
> Internet Mail g0syr@beeb.net
Read previous mail | Read next mail
| |
