<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Ian,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
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.<br>
<br>
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dirk, Kin and others are doing a lot of work updating features but no one is doing the documentation.<br>
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I'll just keep stumbling along until the whole thing is a broken mess. It's almost to that point from me.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
"Do this!!!"</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
"Oh, what, I added this!!!"</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
"Stop forwarding message."</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
"Start forwarding messages..."</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
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.<br>
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I'll stop moaning for now.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Kelly<br>
<br>
<br>
</div>
<div id="appendonsend"></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div dir="ltr" id="divRplyFwdMsg"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> Dxspider-support <dxspider-support-bounces@tobit.co.uk> on behalf of Ian Maude via Dxspider-support <dxspider-support@tobit.co.uk><br>
<b>Sent:</b> Thursday, February 6, 2025 10:00 AM<br>
<b>To:</b> The DXSpider Support list <dxspider-support@tobit.co.uk><br>
<b>Cc:</b> Ian Maude <maudeij@gmail.com><br>
<b>Subject:</b> Re: [Dxspider-support] List of actions to do</span>
<div> </div>
</div>
<div>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.</div>
<div>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.</div>
<div>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.</div>
<div>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.</div>
<div><br>
</div>
<div>73 Ian (G0VGS)</div>
<div><br>
</div>
<blockquote>
<div>On 6 Feb 2025, at 14:45, Kelly Leavitt via Dxspider-support <dxspider-support@tobit.co.uk> wrote:</div>
<br>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
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.</div>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
Configure filters and access permissions correctly - what does this EXPLICITLY mean</div>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
and this one too " Manage network traffic responsibly"</div>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
There needs to be some documentation for these steps or you're going to continue having nodes go out of date.<br>
<br>
Kelly</div>
<div style="font-family:Helvetica;font-size:18px;text-decoration:none" id="x_appendonsend">
</div>
<div style="text-align: left; text-indent: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<hr style="text-align: left; text-indent: 0px; display: inline-block; width: 667.375px;">
<div style="font-family:Helvetica;font-size:18px;text-decoration:none" dir="ltr" id="x_divRplyFwdMsg">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"><b>From:</b> Dxspider-support <dxspider-support-bounces@tobit.co.uk> on behalf of Kin via Dxspider-support <dxspider-support@tobit.co.uk><br>
<b>Sent:</b> Thursday, February 6, 2025 9:11 AM<br>
<b>To:</b> 'The DXSpider Support list' <dxspider-support@tobit.co.uk><br>
<b>Cc:</b> Kin <ea3cv@cronux.net><br>
<b>Subject:</b> Re: [Dxspider-support] List of actions to do</span>
<div> </div>
</div>
<div style="text-align: left; text-indent: 0px; font-family: Helvetica; font-size: 11pt;">
Hi,<br>
<br>
As I see no one has answered you, I would say something like this:<br>
<br>
<br>
*Best practices guide for DXCluster network sysops*<br>
<br>
1. Keep the node updated<br>
Always make sure to use the latest stable version of the software.<br>
<br>
2. Perform regular backups<br>
Save copies of configuration files, logs, and databases to ensure recovery<br>
in case of failure.<br>
<br>
3. Monitor the node's status<br>
Keep track of CPU and memory usage, as well as active connections with nodes<br>
and users.<br>
<br>
4. Maintain good communication with neighboring nodes and the community<br>
If you detect connection problems, packet losses, or inappropriate network<br>
usage, notify sysops for a quick resolution. Collaboration is key to the<br>
system’s stability.<br>
<br>
5. Manage network traffic responsibly<br>
Avoid forwarding unnecessary packets that may overload the network.<br>
Configure spot and announcement traffic correctly to avoid duplications,<br>
loops, or congestion.<br>
Perform periodic checks to ensure the proper functioning of node<br>
interconnections.<br>
<br>
6. Configure filters and access permissions correctly<br>
Define clear access rules and permissions to avoid unwanted or malicious<br>
connections, both for users and nodes.<br>
Protect node interconnections through authentication.<br>
<br>
7. Inform the community<br>
It’s important to share details about your node, such as installation type,<br>
node type, access data, sysop contact, and any other relevant information<br>
for the network.<br>
Similarly, report any anomalies, malfunctions, abuse, or hijacking attempts<br>
you detect on the network.<br>
<br>
8. Stay informed and participate in the community<br>
Follow the changes, improvements, and proposals related to the network and<br>
your node software. Use support and communication forums as a valuable tool<br>
to improve the service.<br>
<br>
9. Have a global vision before acting<br>
Before making modifications to your node, analyze how they could affect the<br>
network as a whole. Think not only about your node but also about the global<br>
impact of changes.<br>
<br>
10. Limit misuse of spots and announcements<br>
Avoid excessive use of auto spots and announcements, and help keeping the<br>
network free from insults, threats, political or religious content.<br>
<br>
11. Experiment in closed environments<br>
If you want to try new configurations or developments, do it first in an<br>
isolated environment to avoid affecting the DXCluster network.<br>
<br>
12. Act always within the ham radio ethics<br>
Respect the rules and principles of amateur radio, promoting cooperation and<br>
the good use of shared resources selflessly.<br>
<br>
<br>
But the above does not exist, it is not written, it is a product of my<br>
limited experience with network clusters and a few decades working in<br>
network environments.<br>
<br>
Kin EA3CV<br>
<br>
<br>
-----Mensaje original-----<br>
De: Dxspider-support <dxspider-support-bounces@tobit.co.uk> En nombre de<br>
Gregor Surmann via Dxspider-support<br>
Enviado el: miércoles, 5 de febrero de 2025 3:49<br>
Para: The DXSpider Support list <dxspider-support@tobit.co.uk><br>
CC: Gregor Surmann <gs@funil.de><br>
Asunto: [Dxspider-support] List of actions to do<br>
<br>
Hello guys!<br>
<br>
I may be, somehow, slightly confused about what I should do or not do to<br>
comply with the (unwritten or written) rules to keep my DO5SSB-2 node<br>
running and alive.<br>
<br>
I would prefer some short words or a list of things that I should<br>
check/change/improve/etc. Could you provide some information, please?<br>
<br>
Also my answers may be delayed, as I work full time.<br>
<br>
Thank you all in advance!<br>
<br>
73 de Gregor, DO5SSB<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" id="OWAb0e76fe5-7b80-5034-7767-ed02de341c91" class="x_OWAAutoLink" data-auth="NotApplicable">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" id="OWA6f563046-e680-ae5c-2a80-6417de8f87e5" class="x_OWAAutoLink" data-auth="NotApplicable">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></div>
<span style="font-family: Helvetica; font-size: 18px;">_______________________________________________</span><br>
<span style="font-family: Helvetica; font-size: 18px;">Dxspider-support mailing list</span><br>
<span style="font-family: Helvetica; font-size: 18px;"><a href="mailto:Dxspider-support@tobit.co.uk" id="OWA52e21c63-3c1a-e283-fb34-ba78cd9e14c4" class="OWAAutoLink" style="text-align: left;">Dxspider-support@tobit.co.uk</a></span><br>
<span style="font-family: Helvetica; font-size: 18px;"><a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" id="OWAce916ddf-c445-108e-e3bb-039c5caab3bd" class="OWAAutoLink" style="text-align: left;" data-auth="NotApplicable">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></span></blockquote>
<br>
</body>
</html>