Cluster Monitor
Latest version 1.22
This Window's program is for local or remote monitoring of a Dx Cluster running under Windows. It has been tested with AR Cluster, CC Cluster, and Dx Spider nodes. It requires my "winsock.exe" program to be running in the cluster machine. This monitor.exe program connects to the winsock.exe program via telnet at the IP and Port address shown in the "Settings" form.
The winsock.exe program prevents lockups of AR Clusters when connections occur too quickly.
The winsock.exe program prevents lockouts of Dx Spider users (Window's version) when too many try to connect to the same cluster.
Settings Form
The Settings form is overlayed on the right side of the form shown below. The IP address and Port number need to match those of the winsock.exe program.
Connections
|
|
There are three items per socket. These are: Incoming IP
Incoming Port
User Call
|
Data across the top of the form. The numbers in the brackets are the numbers from the example.
- Links = Number of telnet connections. (21)
- Time in seconds between loops of main program. (.17212) Will jump up when a user connects and stay there for a short period of time. This prevents new connections from occuring before the cluster is ready for them.
- Latest AR User program version. (2.186)
- ARU Version. (checked) Find what version number of ARU is being used.
- Number of connections using ARU. (17)
- Number of user connections not using ARU. (1)
- Number of node connections. (3)
- Number of unknown programs connected. (0)
- Number of "probes". (25) Probes are connections that don't respond when asked for a callsign.
Clicking on any call will lock monitoring on that user's stream as shown below. Normally the monitoring follows the last connected stream. To restore the "Auto" mode, click on "Manual".
Placing the mouse curser over a callsign will display the user's stream number. Over the port, the version number of the user's program will be shown.
Monitor Form
Blue is incoming, Red is outgoing
MixW Problem
Users of the MixW program can set the web cluster settings in such a way that dx clusters receive continuous connect attempts with "GET /DXS//HFDX25.HTML? HTTP/1.1, USER-AGENT: WEBCL" as the callsign. This really gets in the way of monitoring what is happening with the cluster. In self defense, any IP sending this "callsign" will be temporarily locked out. This lockout will persist until the winsock.exe program is restarted, which may be a long time. This lockout also prevents the user from connecting with his real callsign as a normal user.