DXSpider Documentation Wiki - User contributions [en-gb]

Download DXSpider v1.57 Mojo

2026-03-11T14:02:54Z

EA3CV:

== Download DXSpider v1.57 Mojo ==

While the official '''DXSpider''' repository is currently unavailable, the latest version can be downloaded from the following repository.

The original documentation refers to cloning the repository with:

{| style="width:auto; margin-left:1.6em; border:1px solid #ccc; background:#f8f8f8;"
| style="padding:8px;" | <code style="border:0; background:transparent;">git clone git://scm.dxcluster.org/scm/spider</code>
|}

At the moment this can be replaced with:

{| style="width:auto; margin-left:1.6em; border:1px solid #ccc; background:#f8f8f8;"
| style="padding:8px;" | <code style="border:0; background:transparent;">git clone https://github.com/EA3CV/dxspider</code>
|}

This repository provides access to the '''DXSpider Mojo branch (v1.57)'''.

If you want to update an existing installation from the '''Master branch (1.55)''' to the '''Mojo branch (1.57)''', please see [[DXSpider_MOJO_Version_Update_Script]].

If you want to automate the installation, you can see:
[https://github.com/EA3CV/dxspider_update] update_dxspider_alternative.sh

Download DXSpider v1.57 Mojo

2026-03-11T10:11:13Z

EA3CV:

== Download DXSpider v1.57 Mojo ==

While the official '''DXSpider''' repository is currently unavailable, the latest version can be downloaded from the following repository.

The original documentation refers to cloning the repository with:

{| style="width:auto; margin-left:1.6em; border:1px solid #ccc; background:#f8f8f8;"
| style="padding:8px;" | <code style="border:0; background:transparent;">git clone git://scm.dxcluster.org/scm/spider</code>
|}

At the moment this can be replaced with:

{| style="width:auto; margin-left:1.6em; border:1px solid #ccc; background:#f8f8f8;"
| style="padding:8px;" | <code style="border:0; background:transparent;">git clone https://github.com/EA3CV/dxspider.git</code>
|}

This repository provides access to the '''DXSpider Mojo branch (v1.57)'''.

If you want to update an existing installation from the '''Master branch (1.55)''' to the '''Mojo branch (1.57)''', please see [[DXSpider_MOJO_Version_Update_Script]].

If you want to automate the installation, you can see:
[https://github.com/EA3CV/dxspider_update] update_dxspider_alternative.sh

Download DXSpider v1.57 Mojo

2026-03-11T10:09:17Z

EA3CV:

== Download DXSpider v1.57 Mojo ==

While the official '''DXSpider''' repository is currently unavailable, the latest version can be downloaded from the following repository.

The original documentation refers to cloning the repository with:

{| style="width:auto; margin-left:1.6em; border:1px solid #ccc; background:#f8f8f8;"
| style="padding:8px;" | <code style="border:0; background:transparent;">git clone git://scm.dxcluster.org/scm/spider</code>
|}

At the moment this can be replaced with:

{| style="width:auto; margin-left:1.6em; border:1px solid #ccc; background:#f8f8f8;"
| style="padding:8px;" | <code style="border:0; background:transparent;">git clone https://github.com/EA3CV/dxspider.git</code>
|}

This repository provides access to the '''DXSpider Mojo branch (v1.57)'''.

If you want to update an existing installation from the '''Master branch (1.55)''' to the '''Mojo branch (1.57)''', please see [[DXSpider_MOJO_Version_Update_Script]].

If you want to automate the installation, you can see:
[https://github.com/EA3CV/dxspider_update/blob/main/update_dxspider_alternative.sh update_dxspider_alternative.sh]

Download DXSpider v1.57 Mojo

2026-03-11T09:59:55Z

EA3CV: Temporal Download

== Download DXSpider v1.57 Mojo ==

While the official '''DXSpider''' repository is currently unavailable, the latest version can be downloaded from the following repository.

The original documentation refers to cloning the repository with:

<pre>
git clone git://scm.dxcluster.org/scm/spider
</pre>

At the moment this can be replaced with:

<pre>
git clone https://github.com/EA3CV/dxspider.git
</pre>

This repository provides access to the '''DXSpider Mojo branch (v1.57)'''.

If you want to update an existing installation from the '''Master branch (1.55)''' to the '''Mojo branch (1.57)''', please see:

[[DXSpider_MOJO_Version_Update_Script]]

Node configuration for user access

2025-04-28T05:36:43Z

EA3CV:

===User Registration===
----
There are two types of user in a DXSpider node, a registered user and an unregistered user.
By default, all users belong to the unregistered category.

===Node in UNREGISTERED Mode===
----
This is the default way of working, but not necessarily the best.

The global variable that sets the node type is '''$main::reqreg'''
and its default value is '''0'''.
<pre>
set/var $main::reqreg = 0
</pre>

In this mode the sysop doesn't have to register users, but if they are registered, then it will simply be a database entry.
Both types of user will have the same capabilities to send and receive SPOTS, ANN, etc

===Node in REGISTRATION Mode===
----
To activate registration, the global variable '''$main::reqreg''' must be set to '''1'''.
The way to change it is

<pre>
set/var $main::reqreg = 1
</pre>

When this mode is activated, only users that the sysop has registered will be able to send and receive SPOTS, ANN, etc. Unregistered users will only be able to receive information.

The way to register/unregister a user is as follows:
<pre>
set/register <call>
unset/register <call>
</pre>

You can check which users we have registered using

<pre>
sh/register <call>
</pre>

A specific login banner for registered users can be shown. The file containing it is the following

<pre>
/spider/_local_data/motd
</pre>

When an unregistered user starts the login process, they can be sent a different file that can be configured to say that they are not registered and how to register should they wish to do so. This file is ...

<pre>
/spider/local_data/motd_nor
</pre>

===Password Usage===
----
By default, a user does not get prompted for a password at login. For additional security, a user can request a password be set for them. They simply need to request a password that they provide to the sysop.

It should be noted that this only works on the node they regularly use. Their password is not propagated across the network for security reasons.

For a user to be assigned a password, the sysop needs to use the command ...

<pre>
set/password <call> <string>
</pre>

and the user can change his password with the command

<pre>
set/password
Enter old password:
Enter new password:
Re-enter new password:
Password changed
</pre>

===Node in NO PASSWORD Mode===
----
The global variable '''$main::passwdreq''' is set to '''0''' by default. This does not mean that they cannot have a password set, only that users are not forced to have a password.

To see the value of the variable use ...

<pre>
sh/var $main::passwdreq
</pre>

===Node in PASSWORD Mode===
----
If we set the '''$main::passwdreq''' variable to '''1''', we will force any user logging in to the node to use a password as well as their callsign, otherwise they will not be able to access the node.

The node will not establish the session if there is no positive authentication.

To set this mode of operation:

<pre>
set/var $main::passwdreq = 1
</pre>

===How To protect your cluster node (Recommended configuration)===

----
One way to control the correct use of our node, is to use the combination of registration and password as follows.

We enable the registration for all the users

<pre>
set/var $main::reqreg = 1
</pre>

The beauty of this is that people who try to login with callsigns like ID1OT or even using random callsigns cannot post spots or announcements from the node.

<pre>
set/var $main::passwdreq = 0
</pre>

Of course, a user may wish to have a password set to increase their security on the node, meaning that unless someone also knows the password, their call cannot be used by someone else unless they know the password.

<pre>
set/register <call>
set/password <call> <string>
</pre>

It is strongly suggested that sysops enable registration to try and combat the increasing misuse on the cluster network

===Make Changes Permanent===
----
Although sysops can enable or disable these variables at any time from the console, this will only be enabled until the node is restarted. if we want to keep them during the startup of the node, we must edit the file ...

<pre>
/spider/scripts/startup
</pre>

and include the following lines
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

The changes to this file will not take effect until there is a reboot, so we can activate it manually the first time from the console by typing
<pre>
set/var $main::reqreg = 1
set/var $main::passwdreq = 0
</pre>

DXSpider Registration Support System

2025-04-13T18:05:14Z

EA3CV:

= DXSpider Registration Support System =

📡 '''DXSpider Registration Support System''' provides a user-friendly way for sysops to manage registration requests via '''email''' and/or '''Telegram''', with clear messages and configurable templates in '''Spanish and English''' (default).

== 📌 Purpose ==

This system adds simple tools to support '''registration and password management''' on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort, while keeping a record of all registration requests and their acceptance or denial.
It is not allowed to send more than 10 messages per day per IP.

== ⚙️ Features ==

* Users send requests via a simple command: <code>msg_sysop</code>
* Sysops receive Telegram alerts and emails
* Sysops can approve (<code>auth_register</code>) or reject (<code>deny_reg</code>) registrations
* Sends multilingual confirmation/denial messages to users
* Configurable templates for email content (Spanish/English)

== 📥 Commands Usage ==

The system uses three main commands for managing user registrations:

=== msg_sysop ===
Used by the user to send a registration request.

<pre>
msg_sysop <user_call> REGISTER <user_email> <comments>
</pre>

Example:
<pre>
msg_sysop EA1ZZZ REGISTER ea1zzz@example.net I would like to join the cluster
</pre>

=== auth_register ===
Used by the sysop to approve and register the user.

<pre>
auth_reg <user_call>
</pre>

Example:
<pre>
auth_reg EA1ZZZ
</pre>

=== deny_register ===
Used by the sysop to reject a registration request.

<pre>
deny_reg <user_call>
</pre>

Example:
<pre>
deny_reg EA1ZZZ
</pre>

== 📢 How It Works: Full Example ==

=== REGISTRATION REQUEST (msg_sysop) ===

'''User input from Telnet:'''
<pre>
msg_sysop XX0ABC REGISTER xx0abc@domain.com Requesting access
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Response to user
! style="width:50%; vertical-align:top;" | To sysop via email
|-
|
<pre>
Message sent to sysop.
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
Message: Requesting access
</pre>
|
<pre>
Subject: Msg received from XX0ABC (REGISTER) to EA3CV-2

New message via msg_sysop command:

Node: EA3CV-2
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
IP: 1.2.3.4
Message: Requesting access
</pre>
|-
! style="vertical-align:top;" | To user via email
! style="vertical-align:top;" | To sysop via Telegram
|-
|
<pre>
Asunto: Msg del sysop de / Msg from sysop of EA3CV-2

En breve recibira una respuesta.
Saludos.

You will receive a response shortly.
Regards,

Kin EA3CV
</pre>
|
<pre>
📡 Message from DXSpider command:
Date: 13 April 2025 16:35:02
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
Sent by: EA3CV
IP: 1.2.3.4
Requesting access
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,00000000-000000,PENDING ,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

=== REGISTRATION APPROVAL (auth_register) ===

'''Sysop input from Console:'''
<pre>
auth_reg XX0ABC
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Sysop output
! style="width:50%; vertical-align:top;" | To user via email
|-
|
<pre>
Registration completed for XX0ABC
Email: joaquin@cronux.net
IP: 127.0.0.1
Pass: u$2wGVX=
</pre>
|
<pre>
Asunto: Aceptada su solicitud de registro / Registration accepted XX0ABC at EA3CV-2

Se ha aceptado su solicitud de registro

Usuario: XX0ABC
Password: u$2wGVX=

Use el comando `set/password` para cambiar la contraseña si lo desea.
Disfrute.

Your registration request has been approved.

User: XX0ABC
Password: u$2wGVX=

You can use the `set/password` command to change your password if you wish.
Enjoy.

Kin EA3CV
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,20250413-164558,ACCEPTED,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

=== REGISTRATION DENIAL (deny_register) ===

'''Sysop input from Console:'''
<pre>
deny_reg XX0ABC
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Sysop output
! style="width:50%; vertical-align:top;" | To user via email
|-
|
<pre>
Registration denied for XX0ABC
Email: joaquin@cronux.net
IP: 127.0.0.1
</pre>
|
<pre>
Asunto: Denegada su solicitud de registro / Registration denied XX0ABC at EA3CV-2

Se ha denegado su solicitud de registro.

Si cree que esto es un error, puede contactar con el administrador.
Gracias.

Your registration request has been denied.

If you believe this is a mistake, please contact the administrator.
Thank you.

Kin EA3CV
</pre>
|-
! colspan="2" style="vertical-align:top;" | To sysop via Telegram
|-
|
<pre>
❌ DENIED registration of XX0ABC from 127.0.0.1
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,20250413-165008,DENIED ,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

== 📂 Scripts Included ==

All scripts go in <code>/spider/local_cmd/</code>

* [https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl msg_sysop.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl auth_register.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl deny_register.pl]

Also required:

* [https://github.com/EA3CV/dxspider_info/blob/main/Local.pm Local.pm] → to <code>/spider/local/Local.pm</code>

== 🧩 Configuration: DXVars.pm ==

Append to <code>/spider/local/DXVars.pm</code>:

<syntaxhighlight lang="perl">
# Telegram config
$id = "123456789";
$token = "123456789:ABCDEF-TOKEN";

# Email SMTP config
$email_enable = 1;
$email_from = 'you@example.com';
$email_smtp = 'smtp.example.com';
$email_port = 587; # Port 587 for STARTTLS/Port 465 for SSL)
$email_user = 'your_user';
$email_pass = 'your_pass';
</syntaxhighlight>

== 📑 Files Used ==

* <code>/spider/local_data/pending_reg.txt</code> — Automatically created
* <code>/spider/local_cmd/*.pl</code> — Command scripts
* <code>/spider/local/Local.pm</code> — Email & Telegram logic
* <code>/spider/local/DXvars.pm</code> — Email and Telegram variables

== 🔧 Installation ==

# Copy the scripts to <code>/spider/local_cmd/</code>
# Edit <code>/spider/local/DXVars.pm</code> with your email and Telegram settings
# Install required Perl modules (see below)
# Restart the DXSpider node

== 📦 Required Perl Modules ==

Install with CPAN (from Linux shell):

<syntaxhighlight lang="bash">
cpan Net::SMTP
cpan Net::SMTP::SSL
cpan Net::MQTT::Simple
</syntaxhighlight>

== ✏️ Template Customization ==

Each script includes variables where you can '''modify the bilingual message content'''. Look for blocks like:

<syntaxhighlight lang="perl">
my $msg_text_ok = <<"EMAIL";
...
EMAIL
</syntaxhighlight>

== ✅ Commands Summary ==

{| class="wikitable"
! Command !! Description
|-
| <code>msg_sysop</code> || User sends registration request
|-
| <code>auth_register</code> || Sysop approves and registers the user
|-
| <code>deny_reg</code> || Sysop denies the request
|}

== 👤 Author ==

'''Kin EA3CV''' — [mailto:ea3cv@cronux.net ea3cv@cronux.net] April 2025

DXSpider Registration Support System

2025-04-13T18:02:34Z

EA3CV:

= DXSpider Registration Support System =

📡 '''DXSpider Registration Support System''' provides a user-friendly way for sysops to manage registration requests via '''email''' and/or '''Telegram''', with clear messages and configurable templates in '''Spanish and English''' (default).

== 📌 Purpose ==

This system adds simple tools to support '''registration and password management''' on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort, while keeping a record of all registration requests and their acceptance or denial.

== ⚙️ Features ==

* Users send requests via a simple command: <code>msg_sysop</code>
* Sysops receive Telegram alerts and emails
* Sysops can approve (<code>auth_register</code>) or reject (<code>deny_reg</code>) registrations
* Sends multilingual confirmation/denial messages to users
* Configurable templates for email content (Spanish/English)

== 📥 Commands Usage ==

The system uses three main commands for managing user registrations:

=== msg_sysop ===
Used by the user to send a registration request.

<pre>
msg_sysop <user_call> REGISTER <user_email> <comments>
</pre>

Example:
<pre>
msg_sysop EA1ZZZ REGISTER ea1zzz@example.net I would like to join the cluster
</pre>

=== auth_register ===
Used by the sysop to approve and register the user.

<pre>
auth_reg <user_call>
</pre>

Example:
<pre>
auth_reg EA1ZZZ
</pre>

=== deny_register ===
Used by the sysop to reject a registration request.

<pre>
deny_reg <user_call>
</pre>

Example:
<pre>
deny_reg EA1ZZZ
</pre>

== 📢 How It Works: Full Example ==

=== REGISTRATION REQUEST (msg_sysop) ===

'''User input from Telnet:'''
<pre>
msg_sysop XX0ABC REGISTER xx0abc@domain.com Requesting access
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Response to user
! style="width:50%; vertical-align:top;" | To sysop via email
|-
|
<pre>
Message sent to sysop.
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
Message: Requesting access
</pre>
|
<pre>
Subject: Msg received from XX0ABC (REGISTER) to EA3CV-2

New message via msg_sysop command:

Node: EA3CV-2
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
IP: 1.2.3.4
Message: Requesting access
</pre>
|-
! style="vertical-align:top;" | To user via email
! style="vertical-align:top;" | To sysop via Telegram
|-
|
<pre>
Asunto: Msg del sysop de / Msg from sysop of EA3CV-2

En breve recibira una respuesta.
Saludos.

You will receive a response shortly.
Regards,

Kin EA3CV
</pre>
|
<pre>
📡 Message from DXSpider command:
Date: 13 April 2025 16:35:02
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
Sent by: EA3CV
IP: 1.2.3.4
Requesting access
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,00000000-000000,PENDING ,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

=== REGISTRATION APPROVAL (auth_register) ===

'''Sysop input from Console:'''
<pre>
auth_reg XX0ABC
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Sysop output
! style="width:50%; vertical-align:top;" | To user via email
|-
|
<pre>
Registration completed for XX0ABC
Email: joaquin@cronux.net
IP: 127.0.0.1
Pass: u$2wGVX=
</pre>
|
<pre>
Asunto: Aceptada su solicitud de registro / Registration accepted XX0ABC at EA3CV-2

Se ha aceptado su solicitud de registro

Usuario: XX0ABC
Password: u$2wGVX=

Use el comando `set/password` para cambiar la contraseña si lo desea.
Disfrute.

Your registration request has been approved.

User: XX0ABC
Password: u$2wGVX=

You can use the `set/password` command to change your password if you wish.
Enjoy.

Kin EA3CV
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,20250413-164558,ACCEPTED,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

=== REGISTRATION DENIAL (deny_register) ===

'''Sysop input from Console:'''
<pre>
deny_reg XX0ABC
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Sysop output
! style="width:50%; vertical-align:top;" | To user via email
|-
|
<pre>
Registration denied for XX0ABC
Email: joaquin@cronux.net
IP: 127.0.0.1
</pre>
|
<pre>
Asunto: Denegada su solicitud de registro / Registration denied XX0ABC at EA3CV-2

Se ha denegado su solicitud de registro.

Si cree que esto es un error, puede contactar con el administrador.
Gracias.

Your registration request has been denied.

If you believe this is a mistake, please contact the administrator.
Thank you.

Kin EA3CV
</pre>
|-
! colspan="2" style="vertical-align:top;" | To sysop via Telegram
|-
|
<pre>
❌ DENIED registration of XX0ABC from 127.0.0.1
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,20250413-165008,DENIED ,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

== 📂 Scripts Included ==

All scripts go in <code>/spider/local_cmd/</code>

* [https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl msg_sysop.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl auth_register.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl deny_register.pl]

Also required:

* [https://github.com/EA3CV/dxspider_info/blob/main/Local.pm Local.pm] → to <code>/spider/local/Local.pm</code>

== 🧩 Configuration: DXVars.pm ==

Append to <code>/spider/local/DXVars.pm</code>:

<syntaxhighlight lang="perl">
# Telegram config
$id = "123456789";
$token = "123456789:ABCDEF-TOKEN";

# Email SMTP config
$email_enable = 1;
$email_from = 'you@example.com';
$email_smtp = 'smtp.example.com';
$email_port = 587; # Port 587 for STARTTLS/Port 465 for SSL)
$email_user = 'your_user';
$email_pass = 'your_pass';
</syntaxhighlight>

== 📑 Files Used ==

* <code>/spider/local_data/pending_reg.txt</code> — Automatically created
* <code>/spider/local_cmd/*.pl</code> — Command scripts
* <code>/spider/local/Local.pm</code> — Email & Telegram logic
* <code>/spider/local/DXvars.pm</code> — Email and Telegram variables

== 🔧 Installation ==

# Copy the scripts to <code>/spider/local_cmd/</code>
# Edit <code>/spider/local/DXVars.pm</code> with your email and Telegram settings
# Install required Perl modules (see below)
# Restart the DXSpider node

== 📦 Required Perl Modules ==

Install with CPAN (from Linux shell):

<syntaxhighlight lang="bash">
cpan Net::SMTP
cpan Net::SMTP::SSL
cpan Net::MQTT::Simple
</syntaxhighlight>

== ✏️ Template Customization ==

Each script includes variables where you can '''modify the bilingual message content'''. Look for blocks like:

<syntaxhighlight lang="perl">
my $msg_text_ok = <<"EMAIL";
...
EMAIL
</syntaxhighlight>

== ✅ Commands Summary ==

{| class="wikitable"
! Command !! Description
|-
| <code>msg_sysop</code> || User sends registration request
|-
| <code>auth_register</code> || Sysop approves and registers the user
|-
| <code>deny_reg</code> || Sysop denies the request
|}

== 👤 Author ==

'''Kin EA3CV''' — [mailto:ea3cv@cronux.net ea3cv@cronux.net] April 2025

DXSpider Registration Support System

2025-04-13T18:01:06Z

EA3CV:

= DXSpider Registration Support System =

📡 '''DXSpider Registration Support System''' provides a user-friendly way for sysops to manage registration requests via '''email''' and/or '''Telegram''', with clear messages and configurable templates in '''Spanish and English''' (default).

== 📌 Purpose ==

This system adds simple tools to support '''registration and password management''' on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort, while keeping a record of all registration requests and their acceptance or denial.

== ⚙️ Features ==

* Users send requests via a simple command: <code>msg_sysop</code>
* Sysops receive Telegram alerts and emails
* Sysops can approve (<code>auth_register</code>) or reject (<code>deny_reg</code>) registrations
* Sends multilingual confirmation/denial messages to users
* Configurable templates for email content (Spanish/English)

== 📥 Commands Usage ==

The system uses three main commands for managing user registrations:

=== msg_sysop ===
Used by the user to send a registration request.

<pre>
msg_sysop <user_call> REGISTER <user_email> <comments>
</pre>

Example:
<pre>
msg_sysop EA1ZZZ REGISTER ea1zzz@example.net I would like to join the cluster
</pre>

=== auth_register ===
Used by the sysop to approve and register the user.

<pre>
auth_reg <user_call>
</pre>

Example:
<pre>
auth_reg EA1ZZZ
</pre>

=== deny_register ===
Used by the sysop to reject a registration request.

<pre>
deny_reg <user_call>
</pre>

Example:
<pre>
deny_reg EA1ZZZ
</pre>

== 📢 How It Works: Full Example ==

=== REGISTRATION REQUEST (msg_sysop) ===

'''User input from Telnet:'''
<pre>
msg_sysop XX0ABC REGISTER xx0abc@domain.com Requesting access
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Response to user
! style="width:50%; vertical-align:top;" | To sysop via email
|-
|
<pre>
Message sent to sysop.
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
Message: Requesting access
</pre>
|
<pre>
Subject: Msg received from XX0ABC (REGISTER) to EA3CV-2

New message via msg_sysop command:

Node: EA3CV-2
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
IP: 1.2.3.4
Message: Requesting access
</pre>
|-
! style="vertical-align:top;" | To user via email
! style="vertical-align:top;" | To sysop via Telegram
|-
|
<pre>
Asunto: Msg del sysop de / Msg from sysop of EA3CV-2

En breve recibira una respuesta.
Saludos.

You will receive a response shortly.
Regards,

Kin EA3CV
</pre>
|
<pre>
📡 Message from DXSpider command:
Date: 13 April 2025 16:35:02
Call: XX0ABC
Subject: REGISTER
Email: xx0abc@domain.com
Sent by: EA3CV
IP: 1.2.3.4
Requesting access
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,00000000-000000,PENDING ,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

=== REGISTRATION APPROVAL (auth_register) ===

'''Sysop input from Console:'''
<pre>
auth_reg XX0ABC
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Sysop output
! style="width:50%; vertical-align:top;" | To user via email
|-
|
<pre>
Registration completed for XX0ABC
Email: joaquin@cronux.net
IP: 127.0.0.1
Pass: u$2wGVX=
</pre>
|
<pre>
Asunto: Aceptada su solicitud de registro / Registration accepted XX0ABC at EA3CV-2

Se ha aceptado su solicitud de registro

Usuario: XX0ABC
Password: u$2wGVX=

Use el comando `set/password` para cambiar la contraseña si lo desea.
Disfrute.

Your registration request has been approved.

User: XX0ABC
Password: u$2wGVX=

You can use the `set/password` command to change your password if you wish.
Enjoy.

Kin EA3CV
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,20250413-164558,ACCEPTED,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

=== REGISTRATION DENIAL (deny_register) ===

'''Sysop input from Console:'''
<pre>
deny_reg XX0ABC
</pre>

{| class="wikitable" style="width:100%"
|-
! style="width:50%; vertical-align:top;" | Sysop output
! style="width:50%; vertical-align:top;" | To user via email
|-
|
<pre>
Registration denied for XX0ABC
Email: joaquin@cronux.net
IP: 127.0.0.1
</pre>
|
<pre>
Asunto: Denegada su solicitud de registro / Registration denied XX0ABC at EA3CV-2

Se ha denegado su solicitud de registro.

Si cree que esto es un error, puede contactar con el administrador.
Gracias.

Your registration request has been denied.

If you believe this is a mistake, please contact the administrator.
Thank you.

Kin EA3CV
</pre>
|-
! colspan="2" style="vertical-align:top;" | To sysop via Telegram
|-
|
<pre>
❌ DENIED registration of XX0ABC from 127.0.0.1
</pre>
|}

'''Entry in pending_reg.txt:'''
<pre>
20250413-163500,20250413-165008,DENIED ,XX0ABC,u$2wGVX=,1.2.3.4,xx0abc@domain.com
</pre>

== 📂 Scripts Included ==

All scripts go in <code>/spider/local_cmd/</code>

* [https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl msg_sysop.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl auth_register.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl deny_register.pl]

Also required:

* [https://github.com/EA3CV/dxspider_info/blob/main/Local.pm Local.pm] → to <code>/spider/local/Local.pm</code>

== 🧩 Configuration: DXVars.pm ==

Append to <code>/spider/local/DXVars.pm</code>:

<syntaxhighlight lang="perl">
# Telegram config
$id = "123456789";
$token = "123456789:ABCDEF-TOKEN";

# Email SMTP config
$email_enable = 1;
$email_from = 'you@example.com';
$email_smtp = 'smtp.example.com';
$email_port = 587;
$email_user = 'your_user';
$email_pass = 'your_pass';
</syntaxhighlight>

== 📑 Files Used ==

* <code>/spider/local_data/pending_reg.txt</code> — Automatically created
* <code>/spider/local_cmd/*.pl</code> — Command scripts
* <code>/spider/local/Local.pm</code> — Email & Telegram logic
* <code>/spider/local/DXvars.pm</code> — Email and Telegram variables

== 🔧 Installation ==

# Copy the scripts to <code>/spider/local_cmd/</code>
# Edit <code>/spider/local/DXVars.pm</code> with your email and Telegram settings
# Install required Perl modules (see below)
# Restart the DXSpider node

== 📦 Required Perl Modules ==

Install with CPAN (from Linux shell):

<syntaxhighlight lang="bash">
cpan Net::SMTP
cpan Net::SMTP::SSL
cpan Net::MQTT::Simple
</syntaxhighlight>

== ✏️ Template Customization ==

Each script includes variables where you can '''modify the bilingual message content'''. Look for blocks like:

<syntaxhighlight lang="perl">
my $msg_text_ok = <<"EMAIL";
...
EMAIL
</syntaxhighlight>

== ✅ Commands Summary ==

{| class="wikitable"
! Command !! Description
|-
| <code>msg_sysop</code> || User sends registration request
|-
| <code>auth_register</code> || Sysop approves and registers the user
|-
| <code>deny_reg</code> || Sysop denies the request
|}

== 👤 Author ==

'''Kin EA3CV''' — [mailto:ea3cv@cronux.net ea3cv@cronux.net] April 2025

DXSpider Kin's Helper Script Info

2025-04-11T17:59:23Z

EA3CV:

The following are resources to help with Kin EA3CV's scripts on[https://github.com/EA3CV/dxspider%20info GitHub].

* [https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository Setting up the EA3CV contributions repository]
* [https://wiki.dxcluster.org/wiki/Updating_Public_IP_and/or_Local_IPs_(set/update_ip) Updating Public IP and/or/Local IPs]
* [https://wiki.dxcluster.org/wiki/List_of_nodes_for_mobile_use List of nodes for mobile use (mnodes)]
* [https://wiki.dxcluster.org/wiki/List_of_users_for_mobile_use List of users for mobile use (musers)]
* [https://wiki.dxcluster.org/wiki/Node_configuration_for_user_access Node configuration for user access]
* [https://wiki.dxcluster.org/wiki/Configure_node_with_Dynamic_IP_(Mojo_branch) Configure node with Dynamic IP]
* [https://wiki.dxcluster.org/wiki/Configure_Node_with_more_than_one_local_IP_(Mojo_branch) Configure Node with more than one local IP]
* [https://wiki.dxcluster.org/wiki/Create_a_secure_connection_between_nodes Create a secure connection between nodes]
* [https://wiki.dxcluster.org/wiki/DXSpider_MOJO_Version_Update_Script DXSpider MOJO Version Update Script]
* [https://wiki.dxcluster.org/wiki/Sending_messages_to_the_sysop_via_Telegram Sending messages to the sysop via Telegram ]
* [https://wiki.dxcluster.org/wiki/Node_Backup_and_Update_with_check_build Node Backup and Update with check_build ]
* [https://wiki.dxcluster.org/wiki/DXSpider_Registration_Support_System DXSpider Registration Support System]

DXSpider Registration Support System

2025-04-11T17:13:43Z

EA3CV:

= DXSpider Registration Support System =

📡 '''DXSpider Registration Support System''' provides a user-friendly way for sysops to manage registration requests via '''email''' and/or '''Telegram''', with clear messages and configurable templates in '''Spanish and English'''.

== 📌 Purpose ==

This system adds simple tools to support '''registration and password management''' on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort.

== ⚙️ Features ==

* Users send requests via a simple command: <code>msg_sysop</code>
* Sysops receive Telegram alerts and emails
* Sysops can approve (<code>auth_register</code>) or reject (<code>deny_reg</code>) registrations
* Sends multilingual confirmation/denial messages to users
* Configurable templates for email content (Spanish/English)

== 💬 How It Works ==

1. '''User''' sends a message:
<pre>
msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request</pre>

2. '''Sysop receives:'''
* 📧 Email with request details
* 📱 Telegram notification (optional)

3. '''Sysop approves:'''
<pre>
auth_register EA0ABC-2</pre>

4. '''User receives confirmation email''', e.g.:
<pre>
Subject: Registration accepted EA0ABC-2 at EA3CV-3
User: EA0ABC-2
Password: 5B54gqGz</pre>

5. '''Or sysop denies:'''
<pre>
deny_reg EA0ABC-2</pre>

6. '''User receives denial notice''', e.g.:
<pre>
Subject: Access request denied for EA0ABC-2 on EA3CV-3</pre>

== 📂 Scripts Included ==

All scripts go in <code>/spider/local_cmd/</code>

* [https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl msg_sysop.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl auth_register.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl deny_register.pl]

Also required:

* [https://github.com/EA3CV/dxspider_info/blob/main/Local.pm Local.pm] → to <code>/spider/local/Local.pm</code>

== 🧩 Configuration: DXVars.pm ==

Append to <code>/spider/local/DXVars.pm</code>:

<syntaxhighlight lang="perl">
# Telegram config
$id = "123456789";
$token = "123456789:ABCDEF-TOKEN";

# Email SMTP config
$email_enable = 1;
$email_from = 'you@example.com';
$email_smtp = 'smtp.example.com';
$email_port = 587; # Port 587 for STARTTLS/Port 465 for SSL)
$email_user = 'your_user';
$email_pass = 'your_pass';
</syntaxhighlight>

== 📑 Files Used ==

* <code>/spider/local_data/pending_reg.txt</code> — Automatically created
* <code>/spider/local_cmd/*.pl</code> — Command scripts
* <code>/spider/local/Local.pm</code> — Email & Telegram logic

== 🔧 Installation ==

# Copy the scripts to <code>/spider/local_cmd/</code>
# Edit <code>/spider/local/DXVars.pm</code> with your email and Telegram settings
# Install required Perl modules (see below)
# Restart the DXSpider node

== 📦 Required Perl Modules ==

Install with CPAN (from Linux shell):

<syntaxhighlight lang="bash">
cpan Net::SMTP
cpan Net::SMTP::SSL
cpan Net::MQTT::Simple
cpan JSON
</syntaxhighlight>

== ✏️ Template Customization ==

Each script includes variables where you can '''modify the bilingual message content'''. Look for blocks like:

<syntaxhighlight lang="perl">
my $msg_text_ok = <<"EMAIL";
...
EMAIL</syntaxhighlight>

You can change these to fit your tone and language.

== 📧 Example Messages ==

=== Request Received ===
<pre>
Subject: Message received for EA3CV-3 sysop

En breve recibira una respuesta.
Saludos.

You will receive a response shortly.
Regards,

Kin EA3CV</pre>

=== Confirmation Message ===
<pre>
Subject: Registration accepted EA0ABC-2 at EA3CV-3

Se ha aceptado su solicitud de registro

Usuario: EA0ABC-2
Password: 5B54gqGz

Use el comando `set/password` para cambiar la contraseña si lo desea.
Disfrute.

Your registration request has been approved.

User: EA0ABC-2
Password: 5B54gqGz

You can use the `set/password` command to change your password if you wish.
Enjoy.

Kin EA3CV</pre>

=== Denial Message ===
<pre>
Subject: Access request denied for EA0ABC-2 on EA3CV-3

Lamentamos informarle que su solicitud de acceso para EA0ABC-2 ha sido denegada en EA3CV-3.

No cumple con los criterios requeridos.
Puede intentarlo más adelante si lo desea.

We regret to inform you that your access request for EA0ABC-2 has been denied on EA3CV-3.

It does not meet the required criteria.
You may try again later if you wish.

Kin EA3CV</pre>

=== Telegram Notifications ===

* Incoming request:
<pre>
📡 Message from DXSpider command:
Call: EA0ABC-2
Subject: REGISTER
Email: name@domain.net
Sent by: EA3CV
IP: 1.2.3.4</pre>

* Approval:
<pre>
✅ Registered EA0ABC-2 in EA3CV-3</pre>

* Denial:
<pre>
❌ Registration denied for EA0ABC-2 on EA3CV-3</pre>

== ✅ Commands Summary ==

{| class="wikitable"
! Command !! Description
|-
| <code>msg_sysop</code> || User sends registration request (and anothers)
|-
| <code>auth_register</code> || Sysop approves and registers the user
|-
| <code>deny_reg</code> || Sysop denies the request
|}

== 👤 Author ==
'''Kin EA3CV''' — [mailto:ea3cv@cronux.net ea3cv@cronux.net] April 2025

DXSpider Registration Support System

2025-04-11T17:08:33Z

EA3CV:

= DXSpider Registration Support System =

📡 '''DXSpider Registration Support System''' provides a user-friendly way for sysops to manage registration requests via '''email''' and/or '''Telegram''', with clear messages and configurable templates in '''Spanish and English'''.

== 📌 Purpose ==

This system adds simple tools to support '''registration and password management''' on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort.

== ⚙️ Features ==

* Users send requests via a simple command: <code>msg_sysop</code>
* Sysops receive Telegram alerts and emails
* Sysops can approve (<code>auth_register</code>) or reject (<code>deny_reg</code>) registrations
* Sends multilingual confirmation/denial messages to users
* Configurable templates for email content (Spanish/English)

== 💬 How It Works ==

1. '''User''' sends a message:
<pre>
msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request</pre>

2. '''Sysop receives:'''
* 📧 Email with request details
* 📱 Telegram notification (optional)

3. '''Sysop approves:'''
<pre>
auth_register EA0ABC-2</pre>

4. '''User receives confirmation email''', e.g.:
<pre>
Subject: Registration accepted EA0ABC-2 at EA3CV-3
User: EA0ABC-2
Password: 5B54gqGz</pre>

5. '''Or sysop denies:'''
<pre>
deny_reg EA0ABC-2</pre>

6. '''User receives denial notice''', e.g.:
<pre>
Subject: Access request denied for EA0ABC-2 on EA3CV-3</pre>

== 📂 Scripts Included ==

All scripts go in <code>/spider/local_cmd/</code>

* [https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl msg_sysop.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl auth_register.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl deny_register.pl]

Also required:

* [https://github.com/EA3CV/dxspider_info/blob/main/Local.pm Local.pm] → to <code>/spider/local/Local.pm</code>

== 🧩 Configuration: DXVars.pm ==

Append to <code>/spider/local/DXVars.pm</code>:

<syntaxhighlight lang="perl">
# Telegram config
$id = "123456789";
$token = "123456789:ABCDEF-TOKEN";

# Email SMTP config
$email_enable = 1;
$email_from = 'you@example.com';
$email_smtp = 'smtp.example.com';
$email_port = 587; # Port 587 for STARTTLS/Port 465 for SSL)
$email_user = 'your_user';
$email_pass = 'your_pass';
</syntaxhighlight>

== 📑 Files Used ==

* <code>/spider/local_data/pending_reg.txt</code> — Automatically created
* <code>/spider/local_cmd/*.pl</code> — Command scripts
* <code>/spider/local/Local.pm</code> — Email & Telegram logic

== 🔧 Installation ==

# Copy the scripts to <code>/spider/local_cmd/</code>
# Edit <code>/spider/local/DXVars.pm</code> with your email and Telegram settings
# Install required Perl modules (see below)
# Restart the DXSpider node

== 📦 Required Perl Modules ==

Install with CPAN (from Linux shell):

<syntaxhighlight lang="bash">
cpan Net::SMTP
cpan Net::SMTP::SSL
cpan Net::MQTT::Simple
cpan JSON
</syntaxhighlight>

== ✏️ Template Customization ==

Each script includes variables where you can '''modify the bilingual message content'''. Look for blocks like:

<syntaxhighlight lang="perl">
my $msg_text_ok = <<"EMAIL";
...
EMAIL
</syntaxhighlight>

You can change these to fit your tone and language.

== 📧 Example Messages ==

=== Request Received ===
<pre>
Subject: Message received for EA3CV-3 sysop

En breve recibira una respuesta.
Saludos.

You will receive a response shortly.
Regards,

Kin EA3CV
</pre>

=== Confirmation Message ===
<pre>
Subject: Registration accepted EA0ABC-2 at EA3CV-3

Se ha aceptado su solicitud de registro

Usuario: EA0ABC-2
Password: 5B54gqGz

Use el comando `set/password` para cambiar la contraseña si lo desea.
Disfrute.

Your registration request has been approved.

User: EA0ABC-2
Password: 5B54gqGz

You can use the `set/password` command to change your password if you wish.
Enjoy.

Kin EA3CV
</pre>

=== Denial Message ===
<pre>
Subject: Access request denied for EA0ABC-2 on EA3CV-3

Lamentamos informarle que su solicitud de acceso para EA0ABC-2 ha sido denegada en EA3CV-3.

No cumple con los criterios requeridos.
Puede intentarlo más adelante si lo desea.

We regret to inform you that your access request for EA0ABC-2 has been denied on EA3CV-3.

It does not meet the required criteria.
You may try again later if you wish.

Kin EA3CV
</pre>

=== Telegram Notifications ===

* Incoming request:
<pre>
📡 Message from DXSpider command:
Call: EA0ABC-2
Subject: REGISTER
Email: name@domain.net
Sent by: EA3CV
IP: 1.2.3.4
</pre>

* Approval:
<pre>
✅ Registered EA0ABC-2 in EA3CV-3
</pre>

* Denial:
<pre>
❌ Registration denied for EA0ABC-2 on EA3CV-3
</pre>

== ✅ Commands Summary ==

{| class="wikitable"
! Command !! Description
|-
| <code>msg_sysop</code> || User sends registration request (and anothers)
|-
| <code>auth_register</code> || Sysop approves and registers the user
|-
| <code>deny_reg</code> || Sysop denies the request
|}

== 👤 Author ==
'''Kin EA3CV''' — [mailto:ea3cv@cronux.net ea3cv@cronux.net] April 2025

DXSpider Registration Support System

2025-04-11T17:04:00Z

EA3CV:

= DXSpider Registration Support System =

📡 '''DXSpider Registration Support System''' provides a user-friendly way for sysops to manage registration requests via '''email''' and/or '''Telegram''', with clear messages and configurable templates in '''Spanish and English'''.

== 📌 Purpose ==

This system adds simple tools to support '''registration and password management''' on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort.

== ⚙️ Features ==

* Users send requests via a simple command: <code>msg_sysop</code>
* Sysops receive Telegram alerts and emails
* Sysops can approve (<code>auth_register</code>) or reject (<code>deny_reg</code>) registrations
* Sends multilingual confirmation/denial messages to users
* Configurable templates for email content (Spanish/English)

== 💬 How It Works ==

1. '''User''' sends a message:
<pre>
msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request
</pre>

2. '''Sysop receives:'''
* 📧 Email with request details
* 📱 Telegram notification (optional)

3. '''Sysop approves:'''
<pre>
auth_register EA0ABC-2
</pre>

4. '''User receives confirmation email''', e.g.:
<pre>
Subject: Registration accepted EA0ABC-2 at EA3CV-3
User: EA0ABC-2
Password: 5B54gqGz
</pre>

5. '''Or sysop denies:'''
<pre>
deny_reg EA0ABC-2
</pre>

6. '''User receives denial notice''', e.g.:
<pre>
Subject: Access request denied for EA0ABC-2 on EA3CV-3
</pre>

== 📂 Scripts Included ==

All scripts go in <code>/spider/local_cmd/</code>

* [https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl msg_sysop.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl auth_register.pl]
* [https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl deny_register.pl]

Also required:

* [https://github.com/EA3CV/dxspider_info/blob/main/Local.pm Local.pm] → to <code>/spider/local/Local.pm</code>

== 🧩 Configuration: DXVars.pm ==

Append to <code>/spider/local/DXVars.pm</code>:

<syntaxhighlight lang="perl">
# Telegram config
$id = "123456789";
$token = "123456789:ABCDEF-TOKEN";

# Email SMTP config
$email_enable = 1;
$email_from = 'you@example.com';
$email_smtp = 'smtp.example.com';
$email_port = 587; # Port 587 for STARTTLS/Port 465 for SSL)
$email_user = 'your_user';
$email_pass = 'your_pass';
</syntaxhighlight>

== 📑 Files Used ==

* <code>/spider/local_data/pending_reg.txt</code> — Automatically created
* <code>/spider/local_cmd/*.pl</code> — Command scripts
* <code>/spider/local/Local.pm</code> — Email & Telegram logic

== 🔧 Installation ==

1. Copy the scripts to <code>/spider/local_cmd/</code>
2. Edit <code>/spider/local/DXVars.pm</code> with your email and Telegram settings
3. Install required Perl modules (see below)
4. Restart the DXSpider node

== 📦 Required Perl Modules ==

Install with CPAN (from Linux shell):

<syntaxhighlight lang="bash">
cpan Net::SMTP
cpan Net::SMTP::SSL
cpan Net::MQTT::Simple
cpan JSON
</syntaxhighlight>

== ✏️ Template Customization ==

Each script includes variables where you can '''modify the bilingual message content'''. Look for blocks like:

<syntaxhighlight lang="perl">
my $msg_text_ok = <<"EMAIL";
...
EMAIL
</syntaxhighlight>

You can change these to fit your tone and language.

== 📧 Example Messages ==

=== Request Received ===
<pre>
Subject: Message received for EA3CV-3 sysop

En breve recibira una respuesta.
Saludos.

You will receive a response shortly.
Regards,

Kin EA3CV
</pre>

=== Confirmation Message ===
<pre>
Subject: Registration accepted EA0ABC-2 at EA3CV-3

Se ha aceptado su solicitud de registro

Usuario: EA0ABC-2
Password: 5B54gqGz

Use el comando `set/password` para cambiar la contraseña si lo desea.
Disfrute.

Your registration request has been approved.

User: EA0ABC-2
Password: 5B54gqGz

You can use the `set/password` command to change your password if you wish.
Enjoy.

Kin EA3CV
</pre>

=== Denial Message ===
<pre>
Subject: Access request denied for EA0ABC-2 on EA3CV-3

Lamentamos informarle que su solicitud de acceso para EA0ABC-2 ha sido denegada en EA3CV-3.

No cumple con los criterios requeridos.
Puede intentarlo más adelante si lo desea.

We regret to inform you that your access request for EA0ABC-2 has been denied on EA3CV-3.

It does not meet the required criteria.
You may try again later if you wish.

Kin EA3CV
</pre>

=== Telegram Notifications ===

* Incoming request:
<pre>
📡 Message from DXSpider command:
Call: EA0ABC-2
Subject: REGISTER
Email: name@domain.net
Sent by: EA3CV
IP: 1.2.3.4
</pre>

* Approval:
<pre>
✅ Registered EA0ABC-2 in EA3CV-3
</pre>

* Denial:
<pre>
❌ Registration denied for EA0ABC-2 on EA3CV-3
</pre>

== ✅ Commands Summary ==

{| class="wikitable"
! Command !! Description
|-
| <code>msg_sysop</code> || User sends registration request
|-
| <code>auth_register</code> || Sysop approves and registers the user
|-
| <code>deny_reg</code> || Sysop denies the request
|}

== 👤 Author ==
'''Kin EA3CV''' — [mailto:ea3cv@cronux.net ea3cv@cronux.net] April 2025

DXSpider Registration Support System

2025-04-11T16:56:08Z

EA3CV:

= DXSpider Registration & Password Assistant System =
📌 '''Purpose''' This system provides a user-friendly assistant for managing user registrations and passwords in DXSpider. It includes:

- 📬 Sending bilingual emails (Spanish/English) to users. - 📲 Optional Telegram notifications to the sysop. - ⚙️ Three modular commands that can work independently or as a complete workflow:
- `msg_sysop`
- `auth_register`
- `deny_register`
All user-facing text (email bodies, etc.) is editable for customization.

== 🧰 Included Commands ==

=== msg_sysop.pl ===
- Sends a message from a user to the sysop via email and/or Telegram. - Optionally adds the user to a pending registration list if subject includes `REGISTER`.

=== auth_register.pl ===
- Authorizes a user in `pending_reg.txt`. - Registers the user in DXSpider. - Sends a bilingual welcome email with username/password. - Sends a Telegram notification to the sysop.

=== deny_register.pl ===
- Denies a user registration from `pending_reg.txt`. - Sends a bilingual rejection email to the user. - Sends a Telegram notification to the sysop.

== 📄 How to Use ==
=== From the DXSpider shell:
Send a registration request:
msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request

Authorize a registration:
auth_register EA0ABC-2

Deny a registration:
deny_register EA0ABC-2

== 📦 Requirements ==
=== DXVars.pm Located at: `/spider/local/DXVars.pm`

You must include at the bottom (before `1;`) the following configuration:

```perl

# Telegram config

$id = "123456789"; # Your Telegram chat ID $token = "123456789:ABCdEfGhIjKlmNo"; # Telegram bot token

# Email SMTP config

$email_enable = 1; $email_from = 'sysop@example.net'; $email_smtp = 'smtp.provider.net'; $email_port = 587; # 587 for STARTTLS or 465 for SSL $email_user = 'smtpuser@example.net'; $email_pass = 'smtppassword'; ```

=== Local.pm File: `/spider/local/Local.pm`

📥 Download: https://github.com/EA3CV/dxspider_info/blob/main/Local.pm

== 🔧 Installation

1. Download the scripts:

```text /spider/local_cmd/msg_sysop.pl /spider/local_cmd/auth_register.pl /spider/local_cmd/deny_register.pl ```

📥 Download them from:

- https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl - https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl - https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl

2. Make sure `/spider/local/Local.pm` is updated.

3. Restart DXSpider: ```bash ./cluster.pl restart ```

== 🧩 Required Perl Modules

Install the following modules using `cpan`:

```bash cpan JSON cpan Net::MQTT::Simple cpan Net::SMTP cpan Net::SMTP::SSL ```

== 📂 Files Used

- `/spider/local_cmd/msg_sysop.pl` - `/spider/local_cmd/auth_register.pl` - `/spider/local_cmd/deny_register.pl` - `/spider/local/Local.pm` - `/spider/local_data/pending_reg.txt` (created automatically)

== ✉️ Emails Sent to Users

=== Message confirmation: _Subject_: Message received for EA3CV-3 sysop

``` En breve recibira una respuesta. Saludos.

You will receive a response shortly. Regards,

Kin EA3CV ```

=== Welcome after auth_register: _Subject_: Aceptada su solicitud de registro / Registration accepted EA0ABC-2 at EA3CV-3

``` Se ha aceptado su solicitud de registro

Usuario: EA0ABC-2 Password: 5B54gqGz

Use el comando `set/password` para cambiar la contraseña si lo desea. Disfrute.

Your registration request has been approved.

User: EA0ABC-2 Password: 5B54gqGz

You can use the `set/password` command to change your password if you wish. Enjoy.

Kin EA3CV ```

=== Rejection after deny_register: _Subject_: Solicitud de acceso denegada / Access request denied for EA0ABC-2 on EA3CV-3

``` Lamentamos informarle que su solicitud de acceso para EA0ABC-2 ha sido denegada en EA3CV-3.

No cumple con los criterios requeridos. Puede intentarlo más adelante si lo desea.

We regret to inform you that your access request for EA0ABC-2 has been denied on EA3CV-3.

It does not meet the required criteria. You may try again later if you wish.

Kin EA3CV ```

== 📲 Telegram Messages (to sysop)

From msg_sysop:

``` 📡 Message from DXSpider command: Call: EA0ABC-2 Subject: REGISTER Email: name@domain.net Sent by: EA3CV IP: 1.2.3.4

Registration request ```

From auth_register:

``` ✅ Registered EA0ABC-2 in EA3CV-3 ```

From deny_register:

``` ❌ Registration denied for EA0ABC-2 on EA3CV-3 ```

== 📑 Command Outputs (user view)

From `msg_sysop`:

``` Message sent to sysop.
Call: EA0ABC-2
Subject: REGISTER
Email: name@domain.net
Message: Registration request ```

From `auth_register`:

``` ✔️ Registration completed for EA0ABC-2
Email: name@domain.net
IP: 1.2.3.4
Pass: 5B54gqGz
```

From `deny_register`:

``` ✔️ Registration denied for EA0ABC-2
Email: name@domain.net
IP: 1.2.3.4
```

== ✏️ Customizing Texts

Each script includes a section at the beginning where you can edit the bilingual email content. Modify these strings to suit your cluster style or tone.

== 👤 Author

📧 Kin EA3CV — [ea3cv@cronux.net](mailto:ea3cv@cronux.net) April 2025

DXSpider Registration Support System

2025-04-11T16:51:46Z

EA3CV:

= DXSpider Registration Support System =
📡 **DXSpider Registration Support System** provides a user-friendly way for sysops to manage registration requests via **email** and/or **Telegram**, with clear messages and configurable templates in **Spanish and English**.

== 📌 Purpose ==
This system adds simple tools to support **registration and password management** on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort.

== ⚙️ Features ==

* Users send requests via a simple command: `msg_sysop`
* Sysops receive Telegram alerts and emails
* Sysops can approve (`auth_register`) or reject (`deny_reg`) registrations
* Sends multilingual confirmation/denial messages to users
* Fully configurable templates for email content

== 💬 How It Works ==
1. **User** sends a message from telnet:
```
msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request
```
2. **Sysop receives:**
* 📧 Email with request details
* 📱 Telegram notification (optional)
3. **Sysop approves from console:**
```
auth_register EA0ABC-2
```
4. **User receives confirmation email**, e.g.:
```
Subject: Registration accepted EA0ABC-2 at EA3CV-3
User: EA0ABC-2
Password: 5B54gqGz
```
5. **Or sysop denies from console:**
```
deny_reg EA0ABC-2
```
6. **User receives denial notice**, e.g.:
```
Subject: Access request denied for EA0ABC-2 on EA3CV-3
```

== 📂 Scripts Included ==
All scripts go in `/spider/local_cmd/`

* [`msg_sysop.pl`](https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl)
* [`auth_register.pl`](https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl)
* [`deny_register.pl`](https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl)

Also required:

* [`Local.pm`](https://github.com/EA3CV/dxspider_info/blob/main/Local.pm) → to `/spider/local/Local.pm`

== 🧩 Configuration: DXVars.pm ==
Append to `/spider/local/DXVars.pm`:

```perl

# Telegram config

$id = "123456789"; $token = "123456789:ABCDEF-TOKEN";

# Email SMTP config

$email_enable = 1;

$email_from = 'you@example.com';

$email_smtp = 'smtp.example.com';

$email_port = 587; # Use 465 for SSL

$email_user = 'your_user';

$email_pass = 'your_pass'; ```

== 📑 Files Used ==

* `/spider/local_data/pending_reg.txt` — Automatically created
* `/spider/local_cmd/*.pl` — Command scripts
* `/spider/local/Local.pm` — Email & Telegram logic

== 🔧 Installation ==
1. Copy the scripts to `/spider/local_cmd/`

2. Edit `/spider/local/DXVars.pm` with your email and Telegram settings

3. Install required Perl modules (see below) 4. Restart the DXSpider node

== 📦 Required Perl Modules ==
Install with CPAN (or cpanm from Linux shell):

```cpan Net::SMTP Net::SMTP::SSL Net::MQTT::Simple ```

== ✏️ Template Customization ==
Each script includes variables where you can **modify the bilingual message content**. Look for blocks like:

```perl my $msg_text_ok = <<"EMAIL"; ... EMAIL ```

You can easily customize the tone and language to suit your needs.

== 📧 Example Messages ==

=== Request Message ===
``` msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request ```

=== Email to User (Request Received) ===
``` Subject: Message received for EA3CV-3 sysop

En breve recibira una respuesta. Saludos.

You will receive a response shortly. Regards,

Kin EA3CV ```

=== Email to User (Accepted) ===
``` Subject: Registration accepted EA0ABC-2 at EA3CV-3

Se ha aceptado su solicitud de registro

Usuario: EA0ABC-2 Password: 5B54gqGz

Use el comando `set/password` para cambiar la contraseña si lo desea.

Your registration request has been approved.

User: EA0ABC-2 Password: 5B54gqGz

You can use the `set/password` command to change your password if you wish. Enjoy.

Kin EA3CV ```

=== Email to User (Denied) ===
``` Subject: Access request denied for EA0ABC-2 on EA3CV-3

Lamentamos informarle que su solicitud de acceso para EA0ABC-2 ha sido denegada en EA3CV-3.

No cumple con los criterios requeridos. Puede intentarlo más adelante si lo desea.

We regret to inform you that your access request for EA0ABC-2 has been denied on EA3CV-3.

It does not meet the required criteria. You may try again later if you wish.

Kin EA3CV ```

=== Telegram ===

* Incoming request:

```
📡 Message from DXSpider command:
Call: EA0ABC-2
Subject: REGISTER
Email: name@domain.net
Sent by: EA3CV
IP: 1.2.3.4
```

* Approval:

```
✅ Registered EA0ABC-2 in EA3CV-3
```

* Denial:

```
❌ Registration denied for EA0ABC-2 on EA3CV-3
```

== ✅ Commands Summary ==
| Command | Description |

|------------------|------------------------------------|

| msg_sysop | User sends request |

| auth_register | Sysop approves registration |

| deny_reg | Sysop denies registration |

== 👤 Author ==
Kin EA3CV — [ea3cv@cronux.net](mailto:ea3cv@cronux.net) April 2025

DXSpider Registration Support System

2025-04-11T16:50:08Z

EA3CV: Created page with " = DXSpider Registration Support System = 📡 **DXSpider Registration Support System** provides a user-friendly way for sysops to manage registration requests via **email** and/or **Telegram**, with clear messages and configurable templates in **Spanish and English**. == 📌 Purpose == This system adds simple tools to support **registration and password management** on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal..."

= DXSpider Registration Support System =
📡 **DXSpider Registration Support System** provides a user-friendly way for sysops to manage registration requests via **email** and/or **Telegram**, with clear messages and configurable templates in **Spanish and English**.

== 📌 Purpose ==
This system adds simple tools to support **registration and password management** on a DXSpider node. It allows users to send a request, and sysops to authorize or deny it with minimal effort.

== ⚙️ Features ==

* Users send requests via a simple command: `msg_sysop`
* Sysops receive Telegram alerts and emails
* Sysops can approve (`auth_register`) or reject (`deny_reg`) registrations
* Sends multilingual confirmation/denial messages to users
* Fully configurable templates for email content

== 💬 How It Works ==
1. **User** sends a message from telnet:
```
msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request
```
2. **Sysop receives:**
* 📧 Email with request details
* 📱 Telegram notification (optional)
3. **Sysop approves from console:**
```
auth_register EA0ABC-2
```
4. **User receives confirmation email**, e.g.:
```
Subject: Registration accepted EA0ABC-2 at EA3CV-3
User: EA0ABC-2
Password: 5B54gqGz
```
5. **Or sysop denies from console:**
```
deny_reg EA0ABC-2
```
6. **User receives denial notice**, e.g.:
```
Subject: Access request denied for EA0ABC-2 on EA3CV-3
```

== 📂 Scripts Included ==
All scripts go in `/spider/local_cmd/`

* [`msg_sysop.pl`](https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl)
* [`auth_register.pl`](https://github.com/EA3CV/dxspider_info/blob/main/auth_register.pl)
* [`deny_register.pl`](https://github.com/EA3CV/dxspider_info/blob/main/deny_register.pl)

Also required:

* [`Local.pm`](https://github.com/EA3CV/dxspider_info/blob/main/Local.pm) → to `/spider/local/Local.pm`

== 🧩 Configuration: DXVars.pm ==
Append to `/spider/local/DXVars.pm`:

```perl

# Telegram config

$id = "123456789"; $token = "123456789:ABCDEF-TOKEN";

# Email SMTP config

$email_enable = 1;

$email_from = 'you@example.com';

$email_smtp = 'smtp.example.com';

$email_port = 587; # Use 465 for SSL

$email_user = 'your_user';

$email_pass = 'your_pass'; ```

== 📑 Files Used ==

* `/spider/local_data/pending_reg.txt` — Automatically created
* `/spider/local_cmd/*.pl` — Command scripts
* `/spider/local/Local.pm` — Email & Telegram logic

== 🔧 Installation ==
1. Copy the scripts to `/spider/local_cmd/`

2. Edit `/spider/local/DXVars.pm` with your email and Telegram settings

3. Install required Perl modules (see below) 4. Restart the DXSpider node

== 📦 Required Perl Modules ==
Install with CPAN (or cpanm from Linux shell):

```cpan Net::SMTP Net::SMTP::SSL Net::MQTT::Simple ```

== ✏️ Template Customization ==
Each script includes variables where you can **modify the bilingual message content**. Look for blocks like:

```perl my $msg_text_ok = <<"EMAIL"; ... EMAIL ```

You can easily customize the tone and language to suit your needs.

== 📧 Example Messages ==

=== Request Message ===
``` msg_sysop EA0ABC-2 REGISTER name@domain.net Registration request ```

=== Email to User (Request Received) ===
``` Subject: Message received for EA3CV-3 sysop

En breve recibira una respuesta. Saludos.

You will receive a response shortly. Regards,

Kin EA3CV ```

=== Email to User (Accepted) ===
``` Subject: Registration accepted EA0ABC-2 at EA3CV-3

Se ha aceptado su solicitud de registro

Usuario: EA0ABC-2 Password: 5B54gqGz

Use el comando `set/password` para cambiar la contraseña si lo desea.

Your registration request has been approved.

User: EA0ABC-2 Password: 5B54gqGz

You can use the `set/password` command to change your password if you wish. Enjoy.

Kin EA3CV ```

=== Email to User (Denied) ===
``` Subject: Access request denied for EA0ABC-2 on EA3CV-3

Lamentamos informarle que su solicitud de acceso para EA0ABC-2 ha sido denegada en EA3CV-3.

No cumple con los criterios requeridos. Puede intentarlo más adelante si lo desea.

We regret to inform you that your access request for EA0ABC-2 has been denied on EA3CV-3.

It does not meet the required criteria. You may try again later if you wish.

Kin EA3CV ```

=== Telegram ===

* Incoming request:

```
📡 Message from DXSpider command:
Call: EA0ABC-2
Subject: REGISTER
Email: name@domain.net
Sent by: EA3CV
IP: 1.2.3.4
```

* Approval:

```
✅ Registered EA0ABC-2 in EA3CV-3
```

* Denial:

```
❌ Registration denied for EA0ABC-2 on EA3CV-3
```

== ✅ Commands Summary ==
| Command | Description | |------------------|------------------------------------| | msg_sysop | User sends request | | auth_register | Sysop approves registration | | deny_reg | Sysop denies registration |

== 👤 Author ==
Kin EA3CV — [ea3cv@cronux.net](mailto:ea3cv@cronux.net) April 2025

DXSpider Kin's Helper Script Info

2025-04-09T16:56:24Z

EA3CV:

The following are resources to help with Kin's scripts.

* [https://wiki.dxcluster.org/wiki/Updating_Public_IP_and/or_Local_IPs_(set/update_ip) Updating Public IP and/or/Local IPs]
* [https://wiki.dxcluster.org/wiki/List_of_nodes_for_mobile_use List of nodes for mobile use (mnodes)]
* [https://wiki.dxcluster.org/wiki/List_of_users_for_mobile_use List of users for mobile use (musers)]
* Setting up the EA3CV contributions repository[https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository )]
* Node configuration for user access[https://wiki.dxcluster.org/wiki/Node_configuration_for_user_access )]
* Configure node with Dynamic IP[https://wiki.dxcluster.org/wiki/Configure_node_with_Dynamic_IP_(Mojo_branch) )]
* Configure Node with more than one local IP[https://wiki.dxcluster.org/wiki/Configure_Node_with_more_than_one_local_IP_(Mojo_branch) )]
* Create a secure connection between nodes[https://wiki.dxcluster.org/wiki/Create_a_secure_connection_between_nodes )]
* DXSpider MOJO Version Update Script[https://wiki.dxcluster.org/wiki/DXSpider_MOJO_Version_Update_Script )]
* Sending messages to the sysop via Telegram [https://wiki.dxcluster.org/wiki/Sending_messages_to_the_sysop_via_Telegram]
* Node Backup and Update with check_build [https://wiki.dxcluster.org/wiki/Node_Backup_and_Update_with_check_build]

Node Backup and Update with check build

2025-04-09T16:55:40Z

EA3CV: Created page with " = 🛠️ Node Backup and Update with check_build = == 📋 Description == The `check_build` command is a DXSpider utility script that checks for new builds (updates) in the MOJO branch. If a new build is available, it can: * Perform a full backup of the current node installation * Retain previous backup archives * Automatically update the node (Git hard reset + pull) This tool does not aim to replace the standard `git` update method, but is especially useful for sys..."

= 🛠️ Node Backup and Update with check_build =

== 📋 Description ==
The `check_build` command is a DXSpider utility script that checks for new builds (updates) in the MOJO branch. If a new build is available, it can:

* Perform a full backup of the current node installation
* Retain previous backup archives
* Automatically update the node (Git hard reset + pull)

This tool does not aim to replace the standard `git` update method, but is especially useful for sysops who are cautious about updates potentially breaking their nodes. In case of failure, a full backup ensures the service can be restored quickly.

The script can be run manually from the DXSpider shell or scheduled via `crontab`.

== ⚙️ Features ==

* Verifies if a newer build is available on the remote repository.
* If backup is enabled:
** Creates a full backup using `rsync`
** Compresses it as `spider.YYYYMMDD.HHMMSS.tar.gz`
** Retains up to a configurable number of backup files
* Performs a full Git reset and update
* Optionally notifies via Telegram if configured

== ▶️ Usage ==
From the DXSpider shell:<pre>
check_build <Y/N> <num_backups>
</pre>Where:

* `Y` = Enable backup before updating
* `N` = Update without backup
* `num_backups` = Number of backups to retain (default: 10)

== 🕒 Example crontab configuration ==
Run the command Monday to Friday at 04:00 with backup enabled, keeping 7 backups:<pre>
0 4 * * 1,2,3,4,5 run_cmd("check_build Y 7")
</pre>Update the script daily (thanks to G6NHU) with:<pre>
30 0 * * * spawn('cd /spider/local_cmd; wget -qN https://raw.githubusercontent.com/EA3CV/dxspider_info/main/check_build.pl -O /spider/local_cmd/check_build.pl')
32 0 * * * run_cmd('load/cmd')
</pre>

== 💾 Installation ==
Download the script from the official repository:

[https://github.com/EA3CV/dxspider_info/blob/main/check_build.pl View on GitHub - check_build.pl]

Save it as:<pre>
/spider/local_cmd/check_build.pl
</pre>

== 🔄 Restoring a backup ==
If something goes wrong during the update:

1. Locate the latest backup archive in `/home/sysop/spider.backup`

2. Decompress it:<pre>
cd /home/sysop
tar -xzvf spider.backup/spider.YYYYMMDD.HHMMSS.tar.gz
</pre>3. Replace the current `/spider` directory with the extracted backup

4. Restart DXSpider

== ⏪ Alternative: Using undo_newbuild.pl ==
If installed, the `undo_newbuild.pl` script allows you to quickly restore the most recent backup made by `check_build`.

Simply run:<pre>
set/undo_newbuild
</pre>This command will:

* Locate the latest backup archive in `/home/sysop/spider.backup`
* Decompress and restore it
* Restart the node automatically

=== 📥 Download ===
You can download the script from the repository:

[https://github.com/EA3CV/dxspider_info/blob/main/undo_newbuild.pl View on GitHub - undo_newbuild.pl]

Save it as:<pre>
/spider/local_cmd/undo_newbuild.pl
</pre>

== 📦 Dependencies ==
This script requires:

* Git
* rsync

To install `rsync` on Debian-based systems:<pre>
apt install rsync
</pre>

== 📲 Telegram integration (optional) ==
If the `telegram()` function is defined in `Local.pm` and Telegram bot variables (`$id`, `$token`) are set in `DXVars.pm`, the script will send notifications when:

* A backup starts
* A backup completes

For full setup instructions, see: [https://wiki.dxcluster.org/wiki/Sending_messages_to_the_sysop_via_Telegram Sending messages to the sysop via Telegram]

== 🧠 Notes ==

* Only supports the **MOJO branch** of DXSpider.
* Backup directory: `/home/sysop/spider.backup`
* Automatically excludes heavy folders: debug logs, spots, wwv, wcy, etc.
* Recommended for sysops who want to automate update and backup tasks with minimal risk.

== 👨‍💻 Author ==

* Kin EA3CV* — [mailto:ea3cv@cronux.net](mailto:ea3cv@cronux.net)

DXSpider Kin's Helper Script Info

2025-04-09T16:08:09Z

EA3CV:

Sending messages to the sysop via Telegram

2025-04-09T16:07:06Z

EA3CV:

= 📡 Sending messages to the sysop via Telegram =

== 📋 Description ==
The `msg_sysop` command allows users connected to a DXSpider node to send a direct message to the sysop via Telegram.

It is useful for:

* Requesting registration on the node
* Reporting issues or failures
* Making general enquiries

The message includes the following data:

* User callsign
* Subject (e.g. REGISTER, PROBLEM, INFO)
* Email address
* Message text
* Access IP

== ▶️ Command usage ==
From the DXSpider shell:<pre>
msg_sysop <CALL> <SUBJECT> <EMAIL> <MESSAGE>
</pre>

=== Examples ===
<pre>
set/msg_sysop XX0ABC REGISTER xx0abc@example.com Requesting registration
set/msg_sysop XX0ABC PROBLEM xx0abc@example.com My password is not working
set/msg_sysop XX0ABC-1 INFO xx0abc@example.com Greetings from DM42
</pre>The user will receive a confirmation, and the sysop will receive the complete message via Telegram.

== ⚙️ Required configuration ==
To use the `msg_sysop` command, minimal setup is needed for the Telegram bot.

=== 📁 File: /spider/local/Local.pm ===
Add the following to the end of the file, just before the final `1;`:<pre>
sub telegram
{
my $payload = shift;

my $url = "https://api.telegram.org/bot$main::token/sendMessage";
`curl -s -X POST $url -d chat_id=$main::id -d text="$payload\n" -d parse_mode="Markdown"`;
}
</pre>If `/spider/local/Local.pm` does not exist, you can copy it from the base installation:<pre>
cp /spider/perl/Local.pm /spider/local/
</pre>

=== 📁 File: /spider/local/DXVars.pm ===
Add your bot credentials at the end of the file, just before `1;`:<pre>
# Telegram Bot
$id = "123456789";
$token = "89734237899:KF90V20M90MCQJA9Q0'91C,CCC'0944";
</pre>Restart the node to apply the changes:<pre>
shutdown
</pre>

== 💬 Notify unregistered users ==
To let users know that they need to register and can use the `msg_sysop` command, you can override the default DXSpider error message.

Edit `/spider/startup` and add the following lines:<pre>
set/var $DXM::msgs{en}{e28} = 'Sorry, you need to be registered (Use the msg_sysop command to request registration.)'
set/var $DXM::msgs{es}{e28} = 'Lo sentimos, necesitas estar registrado (Usa el comando msg_sysop para solicitar registrarte)'
</pre>

== 📢 Display a message in the MOTD ==
To remind users upon login, edit the file `/spider/local_data/motd_nor`:<pre>
+-----------------------------------------------------------------------------+
| If you wish to have full access, please use the command 'msg_sysop' |
| to request registration on this node. |
+-----------------------------------------------------------------------------+
</pre>

== 📦 Script download ==
You can download the `msg_sysop.pl` script from the official repository:

[https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl View on GitHub - EA3CV/dxspider_info]

Save it as:<pre>
/spider/local_cmd/msg_sysop.pl
</pre>It may be helpful to look at [https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository]

== 🔐 How to get your Telegram ID and Token ==
To receive messages, you need to configure a Telegram bot:

# Open Telegram and search for <code>@BotFather</code>
# Start a new bot with: <code>/newbot</code> and follow the instructions
# BotFather will return a token like:
<pre>
1234567890:AAEjg0EjEMPLO_T0KEN4PRUEBA1234
</pre>

# Send any message to your bot via Telegram
# Then open this URL in your browser (replace with your actual token):
<pre>
https://api.telegram.org/bot<your_token>/getUpdates
</pre>You will see something like:<pre>
"chat":{"id":123456789,"first_name":"YourName",...}
</pre>That number is your **chat ID**. Use this ID and your token in `/spider/local/DXVars.pm`.

=== ⚠️ Important ===
This script **only works with Telegram bots**. It is not possible to send messages directly to personal accounts via the Telegram API.

== 🧠 Additional notes ==

* This command is designed as a lightweight and direct alternative to email.
* The sysop receives all relevant data, including the user’s IP and callsign.
* You may combine this with logging or other scripts for additional traceability.

== 🧑‍💻 Author ==

* Kin EA3CV* — [mailto:ea3cv@cronux.net](mailto:ea3cv@cronux.net)

Sending messages to the sysop via Telegram

2025-04-09T16:05:28Z

EA3CV:

= 📡 Sending messages to the sysop via Telegram =

== 📋 Description ==
The `msg_sysop` command allows users connected to a DXSpider node to send a direct message to the sysop via Telegram.

It is useful for:

* Requesting registration on the node
* Reporting issues or failures
* Making general enquiries

The message includes the following data:

* User callsign
* Subject (e.g. REGISTER, PROBLEM, INFO)
* Email address
* Message text
* Access IP

== ▶️ Command usage ==
From the DXSpider shell:<pre>
msg_sysop <CALL> <SUBJECT> <EMAIL> <MESSAGE>
</pre>

=== Examples ===
<pre>
set/msg_sysop XX0ABC REGISTER xx0abc@example.com Requesting registration
set/msg_sysop XX0ABC PROBLEM xx0abc@example.com My password is not working
set/msg_sysop XX0ABC-1 INFO xx0abc@example.com Greetings from DM42
</pre>The user will receive a confirmation, and the sysop will receive the complete message via Telegram.

== ⚙️ Required configuration ==
To use the `msg_sysop` command, minimal setup is needed for the Telegram bot.

=== 📁 File: /spider/local/Local.pm ===
Add the following to the end of the file, just before the final `1;`:<pre>
sub telegram
{
my $payload = shift;

my $url = "https://api.telegram.org/bot$main::token/sendMessage";
`curl -s -X POST $url -d chat_id=$main::id -d text="$payload\n" -d parse_mode="Markdown"`;
}
</pre>If `/spider/local/Local.pm` does not exist, you can copy it from the base installation:<pre>
cp /spider/perl/Local.pm /spider/local/
</pre>

=== 📁 File: /spider/local/DXVars.pm ===
Add your bot credentials at the end of the file, just before `1;`:<pre>
# Telegram Bot
$id = "123456789";
$token = "89734237899:KF90V20M90MCQJA9Q0'91C,CCC'0944";
</pre>Restart the node to apply the changes:<pre>
shutdown
</pre>

== 💬 Notify unregistered users ==
To let users know that they need to register and can use the `msg_sysop` command, you can override the default DXSpider error message.

Edit `/spider/startup` and add the following lines:<pre>
set/var $DXM::msgs{en}{e28} = 'Sorry, you need to be registered (Use the msg_sysop command to request registration.)'
set/var $DXM::msgs{es}{e28} = 'Lo sentimos, necesitas estar registrado (Usa el comando msg_sysop para solicitar registrarte)'
</pre>

== 📢 Display a message in the MOTD ==
To remind users upon login, edit the file `/spider/local_data/motd_nor`:<pre>
+-----------------------------------------------------------------------------+
| If you wish to have full access, please use the command 'msg_sysop' |
| to request registration on this node. |
+-----------------------------------------------------------------------------+
</pre>

== 📦 Script download ==
You can download the `msg_sysop.pl` script from the official repository:

[https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl View on GitHub - EA3CV/dxspider_info]

Save it as:<pre>
/spider/local_cmd/msg_sysop.pl
</pre>It may be helpful to look at <nowiki>[https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository]</nowiki>

== 🔐 How to get your Telegram ID and Token ==
To receive messages, you need to configure a Telegram bot:

# Open Telegram and search for <code>@BotFather</code>
# Start a new bot with: <code>/newbot</code> and follow the instructions
# BotFather will return a token like:
<pre>
1234567890:AAEjg0EjEMPLO_T0KEN4PRUEBA1234
</pre>

# Send any message to your bot via Telegram
# Then open this URL in your browser (replace with your actual token):
<pre>
https://api.telegram.org/bot<your_token>/getUpdates
</pre>You will see something like:<pre>
"chat":{"id":123456789,"first_name":"YourName",...}
</pre>That number is your **chat ID**. Use this ID and your token in `/spider/local/DXVars.pm`.

=== ⚠️ Important ===
This script **only works with Telegram bots**. It is not possible to send messages directly to personal accounts via the Telegram API.

== 🧠 Additional notes ==

* This command is designed as a lightweight and direct alternative to email.
* The sysop receives all relevant data, including the user’s IP and callsign.
* You may combine this with logging or other scripts for additional traceability.

== 🧑‍💻 Author ==

* Kin EA3CV* — [mailto:ea3cv@cronux.net](mailto:ea3cv@cronux.net)

DXSpider Kin's Helper Script Info

2025-04-09T15:59:21Z

EA3CV:

Sending messages to the sysop via Telegram

2025-04-09T15:57:13Z

EA3CV: Created page with " = 📡 Sending messages to the sysop via Telegram = == 📋 Description == The `msg_sysop` command allows users connected to a DXSpider node to send a direct message to the sysop via Telegram. It is useful for: * Requesting registration on the node * Reporting issues or failures * Making general enquiries The message includes the following data: * User callsign * Subject (e.g. REGISTER, PROBLEM, INFO) * Email address * Message text * Access IP == ▶️ Command us..."

= 📡 Sending messages to the sysop via Telegram =

== 📋 Description ==
The `msg_sysop` command allows users connected to a DXSpider node to send a direct message to the sysop via Telegram.

It is useful for:

* Requesting registration on the node
* Reporting issues or failures
* Making general enquiries

The message includes the following data:

* User callsign
* Subject (e.g. REGISTER, PROBLEM, INFO)
* Email address
* Message text
* Access IP

== ▶️ Command usage ==
From the DXSpider shell:<pre>
msg_sysop <CALL> <SUBJECT> <EMAIL> <MESSAGE>
</pre>

=== Examples ===
<pre>
set/msg_sysop XX0ABC REGISTER xx0abc@example.com Requesting registration
set/msg_sysop XX0ABC PROBLEM xx0abc@example.com My password is not working
set/msg_sysop XX0ABC-1 INFO xx0abc@example.com Greetings from DM42
</pre>The user will receive a confirmation, and the sysop will receive the complete message via Telegram.

== ⚙️ Required configuration ==
To use the `msg_sysop` command, minimal setup is needed for the Telegram bot.

=== 📁 File: /spider/local/Local.pm ===
Add the following to the end of the file, just before the final `1;`:<pre>
sub telegram
{
my $payload = shift;

my $url = "https://api.telegram.org/bot$main::token/sendMessage";
`curl -s -X POST $url -d chat_id=$main::id -d text="$payload\n" -d parse_mode="Markdown"`;
}
</pre>If `/spider/local/Local.pm` does not exist, you can copy it from the base installation:<pre>
cp /spider/perl/Local.pm /spider/local/
</pre>

=== 📁 File: /spider/local/DXVars.pm ===
Add your bot credentials at the end of the file, just before `1;`:<pre>
# Telegram Bot
$id = "123456789";
$token = "89734237899:KF90V20M90MCQJA9Q0'91C,CCC'0944";
</pre>Restart the node to apply the changes:<pre>
shutdown
</pre>

== 💬 Notify unregistered users ==
To let users know that they need to register and can use the `msg_sysop` command, you can override the default DXSpider error message.

Edit `/spider/startup` and add the following lines:<pre>
set/var $DXM::msgs{en}{e28} = 'Sorry, you need to be registered (Use the msg_sysop command to request registration.)'
set/var $DXM::msgs{es}{e28} = 'Lo sentimos, necesitas estar registrado (Usa el comando msg_sysop para solicitar registrarte)'
</pre>

== 📢 Display a message in the MOTD ==
To remind users upon login, edit the file `/spider/local_data/motd_nor`:<pre>
+-----------------------------------------------------------------------------+
| If you wish to have full access, please use the command 'msg_sysop' |
| to request registration on this node. |
+-----------------------------------------------------------------------------+
</pre>

== 📦 Script download ==
You can download the `msg_sysop.pl` script from the official repository:

[https://github.com/EA3CV/dxspider_info/blob/main/msg_sysop.pl View on GitHub - EA3CV/dxspider_info]

Save it as:<pre>
/spider/local_cmd/msg_sysop.pl
</pre><pre>

</pre>

== 🔐 How to get your Telegram ID and Token ==
To receive messages, you need to configure a Telegram bot:

# Open Telegram and search for <code>@BotFather</code>
# Start a new bot with: <code>/newbot</code> and follow the instructions
# BotFather will return a token like:
<pre>
1234567890:AAEjg0EjEMPLO_T0KEN4PRUEBA1234
</pre>

# Send any message to your bot via Telegram
# Then open this URL in your browser (replace with your actual token):
<pre>
https://api.telegram.org/bot<your_token>/getUpdates
</pre>You will see something like:<pre>
"chat":{"id":123456789,"first_name":"YourName",...}
</pre>That number is your **chat ID**. Use this ID and your token in `/spider/local/DXVars.pm`.

=== ⚠️ Important ===
This script **only works with Telegram bots**. It is not possible to send messages directly to personal accounts via the Telegram API.

== 🧠 Additional notes ==

* This command is designed as a lightweight and direct alternative to email.
* The sysop receives all relevant data, including the user’s IP and callsign.
* You may combine this with logging or other scripts for additional traceability.

== 🧑‍💻 Author ==

* Kin EA3CV* — [mailto:ea3cv@cronux.net](mailto:ea3cv@cronux.net)

DXSpider Kin's Helper Script Info

2025-04-09T07:32:11Z

EA3CV:

DXSpider MOJO Version Update Script

2025-04-09T07:31:04Z

EA3CV: Created page with " = 🛰️ DXSpider MOJO Version Update Script = == 📍 Purpose == This script allows DXSpider sysops to update their node installation to the latest available '''MOJO''' build (a modern development branch of DXSpider). The project is based on the excellent installation work by '''Yiannis Panagou (SV5FRI)''', and is intended for sysops who already have DXSpider installed and want to upgrade safely. == 📦 Repository == The script is hosted on GitHub: https://github..."

= 🛰️ DXSpider MOJO Version Update Script =

== 📍 Purpose ==
This script allows DXSpider sysops to update their node installation to the latest available '''MOJO''' build (a modern development branch of DXSpider).

The project is based on the excellent installation work by '''Yiannis Panagou (SV5FRI)''', and is intended for sysops who already have DXSpider installed and want to upgrade safely.

== 📦 Repository ==
The script is hosted on GitHub: https://github.com/EA3CV/dxspider_update

== ⚙️ What it does ==

* Automatically downloads the latest MOJO version.
* Creates a '''full backup''' of your current DXSpider installation before updating.
* Handles the update process in a controlled way.
* Provides guidance via interactive prompts.

== 📥 Download Instructions ==
Run the following commands as the '''root user''':<pre>
wget https://github.com/EA3CV/dxspider_update/archive/refs/heads/main.zip -O update_dxspider.zip
unzip update_dxspider.zip
cd dxspider_update-main
chmod a+x update_dxspider.sh
./update_dxspider.sh
</pre>You must provide the script with the full path to your current DXSpider installation (usually <code>/spider</code> or similar).

== 🖥️ Tested Operating Systems ==
This script has been tested on a wide range of Linux distributions, including:

* CentOS Linux 7 (Core)
* CentOS Linux 8 (Core)
* Debian GNU/Linux 9 (stretch)
* Debian GNU/Linux 10 (buster)
* Debian GNU/Linux 11 (bullseye)
* Debian GNU/Linux 12 (bookworm)
* Debian GNU/Linux bookworm/sid
* Fedora Linux 39 (Server Edition)
* Fedora Linux 39 (Workstation Edition)
* Linux Mint 21.1
* Linux Mint 21.3
* Raspbian GNU/Linux 9 (stretch)
* Raspbian GNU/Linux 10 (buster)
* Raspbian GNU/Linux 11 (bullseye)
* Raspbian GNU/Linux 12 (bookworm)
* Ubuntu 20.04.6 LTS
* Ubuntu 22.04 LTS
* Ubuntu 22.04.1 LTS
* Ubuntu 22.04.2 LTS
* Ubuntu 22.04.3 LTS
* Ubuntu 22.04.4 LTS
* Ubuntu 22.04.5 LTS
* Ubuntu 24.04.2 LTS
* Rocky Linux 8.5 (Green Obsidian)

== ⚠️ Notes ==

* This script is intended for '''updates only'''.
* For a full fresh installation of DXSpider, please refer to the project by '''SV5FRI''':

https://github.com/glaukos78/dxspider_installation_v2

== 📨 Join the DXSpider community ==
Sysops interested in tracking development, builds, and contributing can join the official DXSpider mailing list: [https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support DXSpider Support Mailing List]

DXSpider Kin's Helper Script Info

2025-04-09T07:17:17Z

EA3CV:

DXSpider Kin's Helper Script Info

2025-04-09T07:16:42Z

EA3CV:

DXSpider Kin's Helper Script Info

2025-04-09T07:07:12Z

EA3CV:

DXSpider Kin's Helper Script Info

2025-04-09T07:02:55Z

EA3CV:

Setting up the EA3CV contributions repository

2025-04-09T06:58:39Z

EA3CV: Created page with " = 📘 Installation and Maintenance Guide for the ''contrib/ea3cv'' Repository = == 📍 Purpose == This document provides step-by-step instructions for installing and keeping up to date the ''ea3cv'' repository under:<pre>/home/sysop/spider/contrib/ea3cv</pre>This repository is intended as a reference, backup, or development environment. It does '''not directly affect the DXSpider system''' unless its contents are copied into active directories such as <code>local_cmd..."

= 📘 Installation and Maintenance Guide for the ''contrib/ea3cv'' Repository =

== 📍 Purpose ==
This document provides step-by-step instructions for installing and keeping up to date the ''ea3cv'' repository under:<pre>/home/sysop/spider/contrib/ea3cv</pre>This repository is intended as a reference, backup, or development environment. It does '''not directly affect the DXSpider system''' unless its contents are copied into active directories such as <code>local_cmd/</code>.

== 🧩 1. Initial Installation ==

=== ▶️ Step 1: Change to the target directory ===
<pre>
cd /home/sysop/spider/contrib
</pre>

=== ▶️ Step 2: Clone the repository ===
<pre>
git clone https://github.com/EA3CV/dxspider_info.git ea3cv
</pre>This will create the directory:<pre>/home/sysop/spider/contrib/ea3cv/</pre>containing all the contents of the remote GitHub repository.

== 🔄 2. Updating the Repository ==

=== ▶️ Manual update ===
To fetch the latest changes from GitHub at any time:<pre>
cd /home/sysop/spider/contrib/ea3cv
git pull
</pre>This will update the local copy to the latest available version.

=== 🕒 Optional: Automatic update via <code>crontab</code> ===
To keep the repository automatically up to date, add a cron job:

# Edit the crontab:
<pre>nano local_cmd/crontab</pre>

# Add the following line to update daily at 04:00:
<pre>
0 4 * * * spawn("cd /home/sysop/spider/contrib/ea3cv; git pull")
</pre>This command will:

* Perform a <code>git pull</code> every day at 04:00.

'''Note''': Avoid making local modifications inside this repository if it is updated automatically via cron, to prevent merge conflicts.

== 🛠️ 3. Using the Cloned Repository ==
This repository may contain:

* Scripts under <code>set/</code>, <code>show/</code>, <code>unset/</code>
* Configuration examples
* Utility tools

You may copy files from this repository into production directories, such as:<pre>/home/sysop/spider/local_cmd/</pre>For example:<pre>
cp /home/sysop/spider/contrib/ea3cv/set/myscript.pl /home/sysop/spider/local_cmd/set/
</pre>

== ✅ Quick Summary ==
{| class="wikitable"
!Action
!Command
|-
|Clone the repository
|<code>git clone https://github.com/EA3CV/dxspider_info.git ea3cv</code>
|-
|Manual update
|<code>cd ea3cv && git pull</code>
|-
|Copy script to production
|<code>cp ea3cv/set/myscript.pl ../local_cmd/set/</code>
|-
|Enable auto-update (cron)
|See the '''crontab''' section above
|}

== 🧠 Notes ==

* This repository is ideal for maintaining clean, reusable command scripts and documentation.
* Custom scripts or local changes should be done outside this directory, typically in <code>local_cmd/</code>.

Updating Public IP and/or Local IPs (set/update ip)

2025-04-07T17:37:30Z

EA3CV:

== Purpose ==

Keeping your DXSpider node's IP addresses updated is '''not optional'''—it is '''essential''' to ensure correct behaviour of announcements, spots, and cluster communications. Without this, there is a risk that outbound spots or announcements may be discarded by other nodes.

This internal command allows your DXSpider node to:

* Automatically update its '''public IP address''' (IPv4 and IPv6) if it has changed (useful for dynamic IP setups).
* Add '''custom local IPs''' (LAN, Docker, VM, etc.) to <code>@main::localhost_names</code>, ensuring proper recognition of internal connections.

== Command ==

<code>set/update_ip <ip1> <ip2> ... <ipN></code>

== Usage ==

=== Basic ===

Run the command without arguments to update the public IPs (IPv4 and IPv6) and detect local IPs automatically:

<pre>
set/update_ip
</pre>

=== With local IPs ===

If your system uses a static local IP such as <code>192.168.1.100</code>, you should explicitly declare it:

<pre>
set/update_ip 192.168.1.100
</pre>

If you have more hosts (e.g., Docker containers, proxies, firewalls), list them all:

<pre>
set/update_ip 192.168.1.100 10.1.0.25
</pre>

This updates the <code>@main::localhost_names</code> variable to include those local IPs.

== Sample Output ==

If there are no changes:

<pre>
No public IPv4 change: 2.2.2.2
No public IPv6 change:
No local IPs change: 127.0.0.1 ::1 172.18.0.3 192.168.1.10
</pre>

If there is a change:

<pre>
Public IPv4 change: 2.2.2.2 → 1.1.1.1
Public IPv6 change:
Local IPs changes: 127.0.0.1 ::1 172.18.0.3 192.168.1.22
</pre>

== Crontab Integration ==

If your node uses a '''dynamic IP''', it is recommended to run this regularly via cron. Add the following to your crontab:

<pre>
00,10,20,30,40,50 * * * * run_cmd("set/update_ip 172.18.0.3 172.18.0.4 192.168.1.10")
</pre>

This checks for changes every 10 minutes. You may prefer a 5-minute interval depending on your setup.

== Installation ==

Save the script to the correct location:

<pre>
cd /spider/local_cmd
mkdir -p set
cd set
wget -c https://github.com/EA3CV/dxspider_info/blob/main/set/update_ip.pl

</pre>

Then, you can run it from DXSpider shell:

<pre>
set/update_ip 192.168.1.100 10.1.0.25
</pre>

Updating Public IP and/or Local IPs (set/update ip)

2025-04-07T16:36:59Z

EA3CV:

= Updating Public IP and/or Local IPs (set/update_ip) =

== Purpose ==
Keeping your DXSpider node's IP addresses updated is '''not optional'''—it is '''essential''' to ensure correct behaviour of announcements, spots, and cluster communications. Without this, there is a risk that outbound spots or announcements may be discarded by other nodes.

This internal command allows your DXSpider node to:

* Automatically update its '''public IP address''' (IPv4 and IPv6) if it has changed (useful for dynamic IP setups).
* Add '''custom local IPs''' (LAN, Docker, VM, etc.) to <code>@main::localhost_names</code>, ensuring proper recognition of internal connections.

== Command ==
<code>set/update_ip <ip1> <ip2> ... <ipN></code>

== Usage ==

=== Basic ===
Run the command without arguments to update the public IPs (IPv4 and IPv6) and detect local IPs automatically:<pre>
set/update_ip
</pre>

=== With local IPs ===
If your system uses a static local IP such as <code>192.168.1.100</code>, you should explicitly declare it:<pre>
set/update_ip 192.168.1.100
</pre>If you have more hosts (e.g., Docker containers, proxies, firewalls), list them all:<pre>
set/update_ip 192.168.1.100 10.1.0.25
</pre>This updates the <code>@main::localhost_names</code> variable to include those local IPs.

== Sample Output ==
If there are no changes:<pre>
No public IPv4 change: 2.2.2.2
No public IPv6 change:
No local IPs change: 127.0.0.1 ::1 172.18.0.3 192.168.1.10
</pre>If there is a change:<pre>
Public IPv4 change: 2.2.2.2 → 1.1.1.1
Public IPv6 change:
Local IPs changes: 127.0.0.1 ::1 172.18.0.3 192.168.1.22
</pre>

== Crontab Integration ==
If your node uses a '''dynamic IP''', it is recommended to run this regularly via cron. Add the following to your crontab:<pre>
00,10,20,30,40,50 * * * * run_cmd("set/update_ip 172.18.0.3 172.18.0.4 192.168.1.10")
</pre>This checks for changes every 10 minutes. You may prefer a 5-minute interval depending on your setup.

== Installation ==
Save the script to the correct location:<pre>
cd /spider/local_cmd
mkdir -p set
cd set
wget -c [https://github.com/EA3CV/dxspider_info/blob/main/set/update_ip.pl update_ip.pl on GitHub]

</pre>Then, you can run it from DXSpider shell:<pre>
set/update_ip 192.168.1.100 10.1.0.25
</pre>

Updating Public IP and/or Local IPs (set/update ip)

2025-04-07T16:33:24Z

EA3CV: Blanked the page

Updating Public IP and/or Local IPs (set/update ip)

2025-04-07T16:30:28Z

EA3CV: Created page with "= Updating Public IP and/or Local IPs (set/update_ip) = == Purpose == Keeping your DXSpider node's IP addresses updated is '''not optional'''—it is '''essential''' to ensure correct behaviour of announcements, spots, and cluster communications. Without this, there is a risk that outbound spots or announcements may be discarded by other nodes. This internal command allows your DXSpider node to: * Automatically update its '''public IP address''' (IPv4 and IPv6) if it..."

= Updating Public IP and/or Local IPs (set/update_ip) =

== Purpose ==

Keeping your DXSpider node's IP addresses updated is '''not optional'''—it is '''essential''' to ensure correct behaviour of announcements, spots, and cluster communications. Without this, there is a risk that outbound spots or announcements may be discarded by other nodes.

This internal command allows your DXSpider node to:

* Automatically update its '''public IP address''' (IPv4 and IPv6) if it has changed (useful for dynamic IP setups).
* Add '''custom local IPs''' (LAN, Docker, VM, etc.) to <code>@main::localhost_names</code>, ensuring proper recognition of internal connections.

== Command ==

<code>set/update_ip <ip1> <ip2> ... <ipN></code>

== Usage ==

=== Basic ===

Run the command without arguments to update the public IPs (IPv4 and IPv6) and detect local IPs automatically:

<pre>
set/update_ip
</pre>

=== With local IPs ===

If your system uses a static local IP such as <code>192.168.1.100</code>, you should explicitly declare it:

<pre>
set/update_ip 192.168.1.100
</pre>

If you have more hosts (e.g., Docker containers, proxies, firewalls), list them all:

<pre>
set/update_ip 192.168.1.100 10.1.0.25
</pre>

This updates the <code>@main::localhost_names</code> variable to include those local IPs.

== Sample Output ==

If there are no changes:

<pre>
No public IPv4 change: 2.2.2.2
No public IPv6 change:
No local IPs change: 127.0.0.1 ::1 172.18.0.3 192.168.1.10
</pre>

If there is a change:

<pre>
Public IPv4 change: 2.2.2.2 → 1.1.1.1
Public IPv6 change:
Local IPs changes: 127.0.0.1 ::1 172.18.0.3 192.168.1.22
</pre>

== Crontab Integration ==

If your node uses a '''dynamic IP''', it is recommended to run this regularly via cron. Add the following to your crontab:

<pre>
00,10,20,30,40,50 * * * * run_cmd("set/update_ip 172.18.0.3 172.18.0.4 192.168.1.10")
</pre>

This checks for changes every 10 minutes. You may prefer a 5-minute interval depending on your setup.

== Installation ==

Save the script to the correct location:

<pre>
cd /spider/local_cmd
mkdir -p set
cd set
wget -c [https://github.com/EA3CV/dxspider_info/blob/main/set/update_ip.pl update_ip.pl on GitHub]

</pre>

Then, you can run it from DXSpider shell:

<pre>
set/update_ip 192.168.1.100 10.1.0.25
</pre>

Configure Node with more than one local IP (Mojo branch)

2025-04-07T13:52:25Z

EA3CV: Update link

NOTE: You do NOT need to fiddle with this unless you specifically have more than just the normal definitions of localhost. So for 'normal' nodes with one external interface, YOU DO NOT NEED TO DO ANY OF THIS.

If you need to configure a node with more than one local IP address, you can do this in the Mojo branch. This allows other IP addresses to be treated in the same way as localhost.

These can be set in the '''/spider/scripts/startup''' file.

The variable '''@main::localhost_names''' is used to achieve this.

You must include ALL the normal localhost names + any other interface names that you might want to include:

set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.30', '172.16.0.20')

You can simplify this by using the qw() option, like this ...

set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.1.30 172.16.0.20)

but either will work. You can define as many IP addresses as you like and they can be IPV4 or 6.

To find the Local IPs you can use the following command at the command line:

hostname -I

You can also update the cluster immediately by adding the following line in the console:

set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.1.30 172.16.0.20)

To see what values the cluster has use the following in the console:

sh/var @main::localhost_names

There is a script called update_ip.pl (in contributions) that automatically updates this variable.

It can be downloaded at [https://raw.githubusercontent.com/EA3CV/dxspider_info/main/set/update_ip.pl]

Configure Node with more than one local IP (Mojo branch)

2025-04-07T06:23:39Z

EA3CV:

Restoring the user DB (Mojo branch)

2025-03-24T17:47:25Z

EA3CV:

From the command line as sysop user:

Stopped service
<pre>
sudo service dxspider stop
</pre>
Change to the directory that contains the user backup: user_json
<pre>
cd /spider/local_data
</pre>
Run regeneration of users.v3j
<pre>
perl user_json
</pre>
Start cluster service
<pre>
sudo service dxspider start
</pre>