[Dxspider-support] Skimmer spots

[Michael G. Carper]

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.

Mike, WA9PIE



-----Original Message-----
From: dxspider-support-bounces at dxcluster.org
[mailto:dxspider-support-bounces at dxcluster.org] On Behalf Of Dirk Koopman
Sent: Saturday, October 12, 2013 11:14 AM
To: The DXSpider Support list
Subject: Re: [Dxspider-support] Skimmer spots

On 12/10/13 07:02, Aurelio - PC5A wrote:
> Hello Mike,
>
> What worked for me was using wintelnetx 
> <http://www.k1ttt.net/software.html#wintelnetx>to collect the skimmer 
> spots at telnet.reversebeacon.net:7000 Also I configured wintelnetx to 
> act as server. Finally connect your spider to wintelnetx and make sure 
> that connections does not forward the skimmer sposts beyond your 
> dxspider node.
>
> 73
> -- Aurelio
> ps. this assumes you are running all under windows.
> pps. I looked quickly in the installation and admin manual of dxspider 
> but could not find info about setting up a "user-like" node connection.
> If that is possible simply define the link to
> telnet.reversebeacon.net:7000 as a user link.
>

Could I just *emphasise* that any skimmer spots you receive should remain on
your node. A good way to achieve this is to do a 'set/isolate <node
callsign>' on the connection to the wintelnetx.

I know that the skimmer people (used to?) use DXSpider as the node software,
but I don't think they allow normal node connections. If they now do, it is
important that you do a 'unset/wantpc9x <node callsign>' 
together with the 'set/isolate ...' above. The isolation code only works
correctly on legacy protocol nodes as the reasons for it don't apply on PC9x
handling nodes such as DXSpider and CC.

Sysops on the general spot network will get *VERY* upset if skimmer spots
appeared outside of the skimmer network. This is simply because they
(weren't) deduplicated and the sheer volume of them, and their
non-discriminating relentlessness overwhelm the normal spot traffic.

Do not take from the above that I am, in any way, against the skimmer
traffic, I'm not. But they keep their network separate for a reason and we
should respect that. They don't want our traffic (and 4000 user/400 node
lists) either.

Dirk G1TLH

_______________________________________________
Dxspider-support mailing list
Dxspider-support at dxcluster.org
http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support