[Dxspider-support] Skimmer spots

Dirk Koopman djk at tobit.co.uk
Sat Oct 12 20:44:04 BST 2013


On 12/10/13 18:50, Michael G. Carper wrote:
> Understood, Dirk.  And I agree completely.
>
> I thought the node could be setup for "inbound only".  That was my thinking.
>
>
> I still don't have it working.  I created a connect script as follows
> (script name wb5vzl):
> timeout 15
> connect telnet telnet.reversebeacon.net 7000
> 'callsign: ' 'WA9PIE-2'
>
> I did "set/node wb5vzl" at the console prompt.
> I did "connect wb5vzl" at the console prompt.
>
> But I'm CentOS here... so I'm not using Wintelnetx.  But I suppose I can
> "set/isolate wb5vzl" regardless.
>
> Ideally, it would be great to be able to turn the skimmer spots on/off
> somehow (maybe by issuing a "disconnect wb5vzl" at some point later.
>
> I can't "see" the connection after I issue the connect command... but I
> don't see the spots.  So I can't tell what's preventing the spots from
> coming.

That's because, as it says on the issue screen "This is not a DX Cluster 
Node". And anyway, in order to receive cluster protocol, the other end 
has to acknowledge you as a node. Just doing it at your end will not work.

And, should you get him to allow you to connect as a node (and I don't 
think you will), you should also do a 'unset/wantpc9x wb5vzl' as well as 
a 'set/isolate wb5vzl'.

Before you ask: I do not and will not (as a matter of very long standing 
policy) write code to do what I think in AR Cluster terms is called a 
"passive node". Other now long gone node software also allowed this. A 
"passive node" is one that tries to make sense of a standard user style 
connection. This is fraught with error and has caused (and occassionally 
still does) no end of problems as a result.

Dirk




More information about the Dxspider-support mailing list