[Dxspider-support] set local sysop as node by mistake

[Dirk Koopman]

On 08/12/16 21:56, Erwin Fiten via Dxspider-support wrote:
> Hi All,
>
> In some way a added the local sysop user as a NODE :
> 'ON8AR NODE AK1A  8-Dec-2016 2154Z Erwin      999.00 ::1'
>
> Due to this, i'm not able to add any other nodes, or to disable myself 
> as anode , and enter the system as a normal sysop.
>
>

There is a possible fix in git/cvs for this problem. It seems to be 
caused by misconfiguration at one or more link partners. You can tell 
who they likely by running something like this:

(/spider/perl/) watchdbg '\^<your myalias call>\^'

You need to investigate (in particular) any PC19 sentences with your 
$myalias callsign. The sysops of the sending node should be informed and 
if this isn't possible then they should be locked out.

This sort of thing is probably suspicious (anything with a 
PC19/PC21/PC51 in it:

   350.dat:1481760001^<- I VA3MW-7 PC19^1^VE3CGR^0^5455^H25^
   350.dat:1481760001^<- I VE6DXC PC19^1^VE3CGR^0^5455^H25^
   350.dat:1481760008^<- I PA8F-6 PC51^VE3CGR^PA8F-6^1^

Grepping through your debug files with something like:

grep -Pi '\^<your myalias call>\^' 35*.dat | less

will pick up historical ones.

Should you happen to be one of the above nodes, please check your 
connect script name as you are (likely) leaving the SSID off the end - 
which is causing this.

In general, if you find yourself sending PC16/17/19/21 to a known 
dxspider node then please a) make sure that you have done a set/spider 
<node call> and b) called your connect script by the (correct) full node 
callsign name. Sending these sentences (unless you have isolated the 
node) is a configuration error.

I shall be limiting (even more) the use of these archaic sentences in 
the coming weeks.

Dirk G1TLH