Clusse 0.30b, released 23.2.1996
- New sysop command LINK. Three parameters: Connect, Disconnect and
Hold. The last tells clusse to disconnect a link and not reconnect,
until it is restarted or adviced to do so using the Connect parameter.
- Added partial decoding of IP and TCP frames inside AX.25 packets for
the monitoring window. Only tried it out in datagram mode. JNOS and
Clusse run fine together under Win95 using the same TNC. I used the
BPQHOST interface for attaching JNOS to BPQ.
- The PC link module now forwards remote database PC messages.
- Added support for PC38, which makes it a LOT harder to create a
cluster loop by telling Clusse to link twice to the same cluster
network segment. If Clusse receives a PC38 when linking, and the
message includes a node callsign which is already in the node table,
the link is disconnected and set to "held" state (clusse won't try to
relink). Several similar cases are also handled. This should make
Clusse very robust against loops and crashes caused by them.
- Changed the handshaking order (the way how two cluster nodes
exchange the user/node tables on linkup) to be more compliant with
the PacketCluster (TM). It worked before, because PacketCluster
does not care too much about the exact syntax of the protocol, so
there wasn't any problem, but some other software using the
protocol might not have worked with Clusse.
- Added a "listen-only" linking mode. You can now link to two or more
nodes which are already linked via some other route, but only one of
the links will be "active". The "listening" links only receive DX spots,
announcements and WWV data, no information is really sent to those
links, and the received data is not sent to other PC links. No
looping occurs! Using listen-mode links requires additional callsigns
(or SSID's with the same callsign) to be used (one per link). 8-(
I took the idea from clx. Keep up the good work, guys!
- Wrote some documentation about PC links and PC network topology.
Read section 4 of clusse.doc carefully before linking anywhere.
links.ini has some new documentation, update yours.
- When PacketCluster distributed a node add message (PC19) which had
the same node twice (which i didn't quite expect), 0.30a got into an
internal loop, got stuck, and had to be rebooted. The action line
always said "Node added". Fixed.
© Heikki Hannikainen <firstname.lastname@example.org>