| |
G6KUI > XROUTE 26.08.06 18:13l 35 Lines 1170 Bytes #999 (0) @ WW
BID : 9537_G6KUI
Read: GUEST OE3GMW
Subj: Re: #TMP problems
Path: DB0FHN<DB0RGB<DB0PM<OE5XBL<OE2XUM<OE5XBR<OE1XAB<HG8LXL<7M3TJZ<DK0WUE<
GB7FCR<GB7MAX<GB7DBY<GB7DBY
Sent: 060826/1550z @:GB7DBY.#23.GBR.EU NPF2.54c [G6KUI PMS Alvaston Derby]
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 ?
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 ?
I've asked Paula to #TMP subject on the adgenda for 23rd September Conference.
73, Pete G6KUI
Message sent with NPFPMS V2.54c
Read previous mail | Read next mail
| |
