> Here is a response I received from Jim WU3V. Jim is a 'super cluster site'
> which a lot of
> clusters connect to via telnet for the purpose of providing their area radio
> connected clusters
> with services. Jim is telling me as follows:
>
> > ====
> > Ron it does not interface too well with packclus. There are a number of
> > bugs that create havoc in our network. The latest is some messages with a
> > hop count of 255 that will make the rounds of the systems until someone
> > manually disconnects the offending clx nodes. I know they are working on a
> > fix, but until that is done I am accepting no connects from clx nodes into
> > the megacluster.
> > Jim WU3V
> > ===
>
> He is refering to CLX. He says 'I know they are working on a fix....' so I
> guess he is
> refering to you? The main problem is apparently loops which result in the
> same
> information circulating endlessly.
>
> I do want to bring up CLX, connect it to a 'super site' via telnet and via
> radio to local
> users and other nearby PacketClusters, but if what Jim tells me is true (at
> least he thinks
> it is true) it doesn't sound like I will be able to get permission to
> connect via telnet as
> I wish.
>
> Are you making changes which will permit CLX to operate in a mode which will
> eliminate these "problems" when used with conventional PacketCluster?
Dear Ron,
I am copying this message to the CLX mailing list. We have been in contact
with Jim (WU3V) several times but from the notes I have here, we are
not currently working on the problem he describes, that is - we are not
really aware of it.
As long as we have no detailed description and feed back from somebody
who is having the problem, there's nothing we can do. We don't have this
problem with circulating spots and after all it may be a configuration
issue at the offending CLX node. CLX does have several configuation
options and it should always possible to make the connection RX-only,
never sending anything except the initialization. This way, CLX will
not produce any problems at all.
This is a message to all of you trying and working with CLX: If you have
a problem, please get in contact with us and try to describe the
situation you observe as clearly as possible. Don't believe that somebody
else will have reported that problem to us. Don't sit back and wait for
the next version, hoping that your problem will be fixed then. Coding
is one side of the story, but making a bug obvious and/or reproducible
goes before any change of the code. So this is where you can help us with
the development of CLX if you take the time.
Please send follow-ups also to the mailing list, Ron.
73 Ben, DL6RAI
--
[] clx - PacketCluster Software for Linux
[] c/o Bernhard ("Ben") Buettner, DL6RAI
[] Internet: yfgszmqh.spnsjec@futuretrade.com
[] Packet: DL6RAI @ DB0AAB.#BAY.DEU.EU