[Dxspider-support] lock call

[Dirk Koopman]

This has a founding feature of DXSpider from its inception. 
Unfortunately, this also got disabled a longish time ago. This remained 
so until an update a couple of years ago. In order to set the situation 
back to the original intent - and with the agreement and encouragement 
of some of the more active management of the network - I have tried (as 
carefully as I can) to lock out all "learned" (but not specifically 
authorised) nodes coming through the PC92 network connections 
description system. This was one of the more visible changes  made in 
the last major update.

set/spider <node call> will both mark a node as a DXSpider (compatible) 
node AND will unlock it, thus allowing it to connect to your node directly.

73 Dirk G1TLH

On 24/11/2024 08:54, Kin via Dxspider-support wrote:
> Hi Jean,
>
> I seem to remember Dirk commenting that by default node callsigns would be in a locked state, until the sysop authorised that it could connect to its node.
> The list that appears are almost all nodes or were.
>
> Kin EA3CV
>
>
> EA3CV-2 dxcluster.cronux.net 7300
> http://clustermap.cronux.net/map.html
>
>
> -----Mensaje original-----
> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Jean VE2PKT via Dxspider-support
> Enviado el: sábado, 23 de noviembre de 2024 21:43
> Para: The DXSpider Support list <dxspider-support at dxcluster.org>
> CC: Jean VE2PKT <ve2pkt at gmail.com>
> Asunto: [Dxspider-support] lock call
>
> Hello all,
>
>
>       I just did a sh/lockout all and there 2 pages of lock call, where that come from?
>
>