[Dxspider-support] List of actions to do

Thu Feb 6 15:18:00 GMT 2025

Ian,
  I specifically went looking for your WIKI first. Noticed it was gone, and then asked for some help. I just figured you were done with maintaining it.

  Dirk, Kin and others are doing a lot of work updating features but no one is doing the documentation.

I'll just keep stumbling along until the whole thing is a broken mess. It's almost to that point from me.

  "Do this!!!"
  "Oh, what, I added this!!!"
  "Stop forwarding message."
  "Start forwarding messages..."

It's a confusing spaghetti pile of instructions with no clear step by step procedures. I don't have the knowledge of what needs to be done so I would be less than helpful writing things up.

I'll stop moaning for now.

Kelly

________________________________
From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> on behalf of Ian Maude via Dxspider-support <dxspider-support at tobit.co.uk>
Sent: Thursday, February 6, 2025 10:00 AM
To: The DXSpider Support list <dxspider-support at tobit.co.uk>
Cc: Ian Maude <maudeij at gmail.com>
Subject: Re: [Dxspider-support] List of actions to do

This one I will answer.  I originally wrote (with help) the DXSpider documentation back (I think) in 2003.  The cluster has moved on immensely since that time and I have not had the time to deal with it all.  Some time ago I created a wiki specifically with the aim of improving the documentation.  I invited others to help and, in reality, the only person who had any enthusiasm for it was Kin.
Recently, my web server was badly compromised by a PHP exploit and I have taken my websites down.  This includes the DXSpider wiki, which I believe to have escaped the issues.  Since that time, *nobody* has checked why it was down.  These questions look to me like perfect FAQ’s to add to such a site but I do not have the enthusiasm, nor the energy to continue with it.  The DXSpider directory tree includes txt and HTML versions of all the manuals but nobody looks to see.  The wiki included a filters primer (not mine) as well as a LOT of useful information, albeit some of it outdated.
If anyone would like to take on this task, I am happy to send the mediawiki database as it is, with the caveat that it must be carefully scanned before use, in order to continue the documentation project.
I confess to being somewhat irritated by questions about ‘where are the documents’ when a lot of them have been there all along and I have tried to move them forward.

73 Ian (G0VGS)

On 6 Feb 2025, at 14:45, Kelly Leavitt via Dxspider-support <dxspider-support at tobit.co.uk> wrote:

OK, so where are the documents that support how to do these steps? I'm not going to try to pour over the years' worth of messages in this group to make these things happen.

Configure filters and access permissions correctly - what does this EXPLICITLY mean
and this one too " Manage network traffic responsibly"

There needs to be some documentation for these steps or you're going to continue having nodes go out of date.

Kelly

________________________________
From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> on behalf of Kin via Dxspider-support <dxspider-support at tobit.co.uk>
Sent: Thursday, February 6, 2025 9:11 AM
To: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
Cc: Kin <ea3cv at cronux.net>
Subject: Re: [Dxspider-support] List of actions to do

Hi,

As I see no one has answered you, I would say something like this:

*Best practices guide for DXCluster network sysops*

1. Keep the node updated
Always make sure to use the latest stable version of the software.

2. Perform regular backups
Save copies of configuration files, logs, and databases to ensure recovery
in case of failure.

3. Monitor the node's status
Keep track of CPU and memory usage, as well as active connections with nodes
and users.

4. Maintain good communication with neighboring nodes and the community
If you detect connection problems, packet losses, or inappropriate network
usage, notify sysops for a quick resolution. Collaboration is key to the
system’s stability.

5. Manage network traffic responsibly
Avoid forwarding unnecessary packets that may overload the network.
Configure spot and announcement traffic correctly to avoid duplications,
loops, or congestion.
Perform periodic checks to ensure the proper functioning of node
interconnections.

6. Configure filters and access permissions correctly
Define clear access rules and permissions to avoid unwanted or malicious
connections, both for users and nodes.
Protect node interconnections through authentication.

7. Inform the community
It’s important to share details about your node, such as installation type,
node type, access data, sysop contact, and any other relevant information
for the network.
Similarly, report any anomalies, malfunctions, abuse, or hijacking attempts
you detect on the network.

8. Stay informed and participate in the community
Follow the changes, improvements, and proposals related to the network and
your node software. Use support and communication forums as a valuable tool
to improve the service.

9. Have a global vision before acting
Before making modifications to your node, analyze how they could affect the
network as a whole. Think not only about your node but also about the global
impact of changes.

10. Limit misuse of spots and announcements
Avoid excessive use of auto spots and announcements, and help keeping the
network free from insults, threats, political or religious content.

11. Experiment in closed environments
If you want to try new configurations or developments, do it first in an
isolated environment to avoid affecting the DXCluster network.

12. Act always within the ham radio ethics
Respect the rules and principles of amateur radio, promoting cooperation and
the good use of shared resources selflessly.

But the above does not exist, it is not written, it is a product of my
limited experience with network clusters and a few decades working in
network environments.

Kin EA3CV

-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
Gregor Surmann via Dxspider-support
Enviado el: miércoles, 5 de febrero de 2025 3:49
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Gregor Surmann <gs at funil.de>
Asunto: [Dxspider-support] List of actions to do

Hello guys!

I may be, somehow, slightly confused about what I should do or not do to
comply with the (unwritten or written) rules to keep my DO5SSB-2 node
running and alive.

I would prefer some short words or a list of things that I should
check/change/improve/etc. Could you provide some information, please?

Also my answers may be delayed, as I work full time.

Thank you all in advance!

73 de Gregor, DO5SSB

_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk<mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250206/5d0919bf/attachment-0001.htm>