What troubles me is the Q&A from the CLX.TXT which I quote:
========================================================
Q. CLX does not report its own node connection list to other Pavillion
PacketCluster nodes? This hides the network behind CLX to their users.
Why don't you report this information (through PC38/PC39, PC19/PC21)?
A. The problem you describe (PC38) has in fact nothing to do with
PC38. It is only a compatibility issue and for that reason, CLX is
not sending any such information to a PacketCluster node. Here is why:
About 9 months ago CLX would send a list of connected nodes out to
every active link. Due to CLX's special ability to make multiple
connects into a network, some distant nodes already showed up in CLX's
Node list. We had a configuration like this:
DB0ABH-15
|
DB0SPC +-----------DB0BCC--------------OE1XHB
| |
| +--DB0SDX------(A)-----DB0CLX
| | |
+-HB9W-8-----------(P)-------+
We found out that whenever DB0CLX reported that it had connected
HB9W-8, DB0SDX would no longer try to establish its own connection to
HB9W-8. Obviously, the PacketCluster software anticipated that the
connection already existed.
We had this same situation between DB0BCC, DB0SDX and DB0CLX so it is
certainly a bug/problem in the Pavillion software (which does not know
about multiple links).
For this reason we decided that CLX would not report any network
information to neighbouring Pavillion nodes. However, it does fully
report to adjacent CLX nodes.
=======================================================
While the above is probably clear to CLX users, I am not sure if:
1) Will users on my CLX cluster be able to see who is signed on to
connected
Pavillion nodes?
2) If I am between two Pavillion nodes will a user on one of the Pavillion
nodes
not be able to see the users on the other Pavillion nodes?
3) Is any of this a configuration option, if I am willing to put up with
some problems
will I be able to add back the user list feature.
I ask all this because if CLX will not do this, then it will not be easy for
it to be
adopted into existing Pavillion networks, even if it is superior.
Ron Stordahl N5IN