| |
G0SYR > XROUTE 25.08.06 15:20l 76 Lines 3198 Bytes #999 (0) @ WW
BID : 37636G0SYR
Read: OE3GMW GUEST
Subj: Re: #TMP problems
Path: DB0FHN<DB0RGB<OK0PPL<OK0PAD<OK0PCC<SR6BBA<SR1BSZ<TU5EX<IW8PGT<CX2SA<
GB7YFS<GB7CIP<GB7CIP<GB7CIP
Sent: 060825/1311Z @:GB7CIP.#32.GBR.EU $:37636G0SYR
T:From: g0syr <g0syr@gb7cip.ampr.org>
T:Newsgroups: ampr.packet.xrouter
T:Message-Id: <1dvo4youcm83t$.h0ptll4uc1wf$.dlg@40tude.net>
On Fri, 25 Aug 2006 11:14:00 +0000, g6kui%gb7dby.#23.gbr.eu@gb7cip.ampr.org
wrote:
> Thanks to Bryan G0SYR for replying to my bulletin.
> Since my original bulletin, I've been told that there is a setting within
> XRouter that disables the #TMP propergation. As I'm not familiar with the
> inner workings of XRouter then I'm in no place to comment about it.
>
> From what Bryan says, the problem is not confined to XRouter as Xnet
> seems to also have the problem.
>
> }
> } Hi Pete and all,
> } I may be wrong but I don't think this is a feature of XROUTER. I wrote
> } several bulletins about these #TMP entries probably a year or so ago and
> } did some investigation into them. As far as I'm aware XROUTER's tempory
> } entries are created WITHOUT the node name and are processed normally.
> } I did not fully trace the problem back to which node software/version
> } is causing the problem as it appeared to be more than one, as I have seen
> } both #TEMP and #TMP and #tmp and #temp versions of the corrupted entries.
> }
> } Here is the top of my nodes list today,
> }
> } GB7CP:CATHAM} Nodes:
> } #tmp:GB7TUT-1 #tmp:EI3RCW-8 #tmp:GB7WE #tmp:2E1GOR
> } #tmp:G0WKL-1 #tmp:G0WKL-2 #tmp:GB7DY-7 #tmp:GB7WE-8
> } #tmp:GB7GH-7 #tmp:GB3KD #tmp:G7DIR-2 #tmp:G0WKL-3
> } #tmp:G8LWS-1 #tmp:GB7WS-2 #tmp:GB7WV #TMP:GB7SYP-1
> } #tmp:G1NNA-8 #tmp:GB7NNA #tmp:GB7FD #TMP:GB7YDX-8
> } #tmp:G6TJZ-8 #TMP:GB7AYR
> }
> } The problem seems to be getting worse so maybe node software causing
> } the problem is being installed at more node sites.
> }
>
> Well my problem was generated at GB7WV, which uses XRouter.
>
> I don't know how many nodes in the UK use Xnet,if any, but a good number
> certainly use XRouter.
>
> It's now reaching a point that NETROM is becoming useless, so we need to
> sort out the problem and put in the fixes.
>
> Maybe we could discuss this #TMP problem at the forthcoming UK Packet
> Conference on 23rd September ?
>
> That reminds me, I must reply to Paula about me attending the conference.
>
> 73, Pete G6KUI
>
>
>
> Message sent with NPFPMS V2.54c
Hi Pete and all,
That's interesting could you ask for more information about configuring
XROUTER to stop propagation of them as I would be interested and don't
know of a way to prevent their propagation so more details would be
useful. Of course they are not only propagating through XROUTER nodes as
they are seen as valid entries by all nodes once they have been sent
in a nodes broadcast by the offending station.
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 ?
--
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
| |
