| |
G0SYR > XROUTE 26.08.06 23:07l 69 Lines 2663 Bytes #999 (0) @ WW
BID : 64620G0SYR
Read: GUEST OE3GMW
Subj: Re: #TMP problems
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<DB0RES<LZ4NY<TU5EX<IW8PGT<VK4TRS<GB7YFS<
GB7CIP<GB7CIP<GB7CIP
Sent: 060826/2104Z @:GB7CIP.#32.GBR.EU $:64620G0SYR
T:From: g0syr <g0syr@gb7cip.ampr.org>
T:Newsgroups: ampr.packet.xrouter
T:Message-Id: <veniykv4cng5.1qc47g01mu62r$.dlg@40tude.net>
Hi Pete, Peter and all,
On Sat, 26 Aug 2006 15:50:00 +0000, g6kui%gb7dby.#23.gbr.eu@gb7cip.ampr.org
wrote:
> Thanks to further input from Bryan G0SYR and Peter G6HJP.
>
> Last point first.
> Bryan asks :-
> }
> } I wonder how you know the problem is generated at GB7WV as in my
> } observations it was almost impossible to tell where the problem came
> } from. I realise that it's the corrupt entry at GB7WV that causes you
> } the problem but how could you tell the entry was generated by XROUTER
> } at GB7WV and not received from another node ?
>
> As you have observed, there was and still is a corrupt entry at BLOX for
> GB7DBY.
> Since the correction of the entry at GB7WV:WOLVES a few days ago, the
> corrupt entry has not got back to GB7WV, so it is unlikely to have
> come via BLOX in the first place.
>
> How does the route quality of the corrupt entry get to such a high value
> in order for it to be able to propogate in the first place ?
I don't think the route has to have a high value necessarily as I think
nodes take the name heard in the last broadcast so the entries are valid
routes it's just that the name has been overwritten with the last heard
name.
> Mabe Bryan can throw a little more light onto the subject of multiple
> nodes with the same name ? There is/was a node near you called BASE that
> also shared it's name with another node of the same name. How did they
> co-exist ?
This was the opposite to the problem we have in that it was 2 nodes sharing
a single name which is OK, I think if you asked to connect to BASE then
you were connected to the first node in the table. The problem we have
is that there is a only one node as it's the callsign that defines the
node and it can only have one name which is the last name that was
received in a nodes broadcast. We had a similar problem when I changed
node name here when I went to XROUTER from X1J as I needed a simgle
common name changing from CATB22 to CATHAM but for months/years after
the old CATB22 name came back when a badly configured BPQ node rebooted
and loaded an old nodes table from it's HDD (It had not been configured to
regularly save its table to disk) It was just as difficult to fix the
problem as the current one.
>
> I've asked Paula to #TMP subject on the adgenda for 23rd September Conference.
>
> 73, Pete G6KUI
>
>
>
>
> Message sent with NPFPMS V2.54c
--
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
| |
