[Dxspider-support] List of actions to do

Thu Feb 6 15:34:28 GMT 2025

Don't be condescending...

I've read all of those. Your linked manuals are out of date, at least to my poor eyes.

e.g. There's no mention of the crontab to auto update the server. There's no mention of badip

I've been

  *
TCP/IP networking since the 80's
  *
running Linux before version 1
  *
running dxspider servers for years.

You keep adding features and caveats, but there is no clear, step-by-step list of best practices for keeping the cluster up-to-date and secure.

Kelly

________________________________
From: Kin <ea3cv at cronux.net>
Sent: Thursday, February 6, 2025 10:06 AM
To: Kelly Leavitt <kelly at catcorner.org>; 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
Subject: RE: [Dxspider-support] List of actions to do

Hi,

First things first

### Key skills of a Node Administrator:** **## **1.

1. Networking and communication protocols**

- Concepts of TCP/IP networking, DNS, routing and NAT.

- Protocols used in the specific network (e.g. Telnet, SSH, HTTP, DXCluster, etc.).

- Configuration and administration of ports, firewalls and VPNs.

2. Operating systems and server administration**.

- Use and management of Linux/Unix and Windows Server based systems.

- Handling of administration commands, processes and system logs.

- Installation and configuration of node software.

3. IT security and access management**.

- Authentication and access control methods.

- Protection against attacks such as DoS, spoofing and unauthorised access.

- Configuration of encryption and security certificates.

4. Databases and storage**

- Management of configuration files, activity logs and system logs.

- Basic database skills (SQL, NoSQL, JSON files, etc.).

- Data backup and recovery procedures.

5. Diagnostics and troubleshooting**.

- Network monitoring and traffic analysis tools (Wireshark, Netstat, Ping, Traceroute, etc.).

- Identification of connectivity and node stability problems.

- Troubleshooting node software or node configurations.

6. Automation and scripting**

- Programming in Bash, Python or Perl to automate maintenance and monitoring tasks.

- Creation of scripts for log management, traffic analysis or software updates.

7. Coordination and community management**

- Communication with other network administrators and users.

- Management of usage policies and documentation of procedures.

- Participation in technical community forums and mailing lists.

In the context of **DXCluster**, a node administrator must also know how the system works, its interconnection architecture, spot and filter management, as well as best practices to avoid abuses and optimise information traffic.

The second of the first

Option 1:

Chrome -> Google -> manual administrator dxspider

Respuesta -> http://www.dxcluster.org/main/adminmanual_en.html

The DXSpider Administration Manual v1.51

Ian Maude, G0VGS, (g0vgs at gb7mbc.net), and Charlie Carroll, K1XX, (k1xx at ptcnh.net)

Option 2:

Linux terminal

cd /home/sysop/spider

find . -name *manual*

./html/adminmanual_en-8.html

./html/adminmanual_en-6.html

./html/usermanual_en-11.html

./html/usermanual_en-2.html

./html/adminmanual_en-4.html

./html/adminmanual_en-11.html

./html/usermanual_en-4.html

./html/adminmanual_en-3.html

./html/usermanual_en-10.html

./html/adminmanual_en-9.html

./html/usermanual_en-8.html

./html/adminmanual_en-5.html

./html/usermanual_en-1.html

./html/usermanual_en-5.html

./html/usermanual_en-9.html

./html/usermanual_en-12.html

./html/adminmanual_en-1.html

./html/usermanual_en-3.html

./html/adminmanual_en-7.html

./html/adminmanual_en.html

./html/adminmanual_en-10.html

./html/usermanual_en.html

./html/usermanual_en-6.html

./html/usermanual_en-7.html

./html/adminmanual_en-2.html

./txt/adminmanual_en.txt

./txt/usermanual_en.txt

./sgml/usermanual_en.sgml

./sgml/adminmanual_en.sgml

./sgml/adminmanual.sgml

./sgml/usermanual.sgml

find . -name *Note*

./cmd/Notes.txt

find . -name *Change*

./spider-web/Changes

./Changes

Kin EA3CV

De: Kelly Leavitt <kelly at catcorner.org>
Enviado el: jueves, 6 de febrero de 2025 15:46
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
CC: Kin <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] List of actions to do

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250206/4342a392/attachment-0001.htm>