| |
ZL3TPN > PING 27.01.05 12:24l 22 Lines 1022 Bytes #999 (0) @ WW
BID : ZL3TPN328678
Read: GUEST DG0TM DL5GCC
Subj: Looking interesting
Path: DB0FHN<DB0RGB<DB0MRW<DB0HOT<OK0PBX<OK0PHK<OK0NAG<OK0PPL<DB0RES<DK0WUE<
7M3TJZ<F6CDD<N2BQF<VK6HGR<ZL2TZE<ZL2TZE<ZL2SUN
Sent: 050128/0947Z @:ZL2SUN.#70.NZL.OC #:27000 [Nelson, NZ] $:ZL3TPN328678
From: ZL3TPN@ZL2SUN.#70.NZL.OC
To : PING@WW
Thanks for the info on PING so far...some have strayed and it would be nice if
they can agree to dis-agree. You all have some knowledge I'm finding very
interesting, like how ping can help resolve routes by returning the path and
will also show the timing involved, all automatically if avalible or manually
by sysops (thankyou sysops).
Can this PING test be useful to find if an address is being corrupted like
G0TFD is seeing? Or why a path is not reversible? -( or is that the
intenet-links fuzzing it?)
Is the topic of corruption of addresses needing to be investigate to see if
there is a viris or vandal affecting SP and SB's getting to their proper...
destination. If we have to start sending SP to @WW to send a msg. that must
load the bandwidth problem...if it is a problem......just let's not all try to
PING all over the place...not untill Friday night anyhow. Ta - from Nick
T4 1.5à23
Read previous mail | Read next mail
| |
