[Dxspider-support] Blocking a bad node (rather than bad spotter)

[Howard Leadmon]

I allow anyone to join and read, but I require registration to post spots.
Sure I know that means only a handful of people probably use the node to
post, but I agree it keeps things more on the up and up.   Really how hard
is it to drop a message saying this is XYZZY and I would like to use your
node to post spots, it at least shows your sincere hopefully.

 

 

---

Howard Leadmon - WB3FFV

 

 

From: dxspider-support-bounces at dxcluster.org
[mailto:dxspider-support-bounces at dxcluster.org] On Behalf Of Dave Trainor
Sent: Friday, December 05, 2014 12:40 PM
To: The DXSpider Support list
Subject: Re: [Dxspider-support] Blocking a bad node (rather than bad
spotter)

 

I would venture to say that in this day/age and given the state of the
internet, we all should be using usernames and passwords, or this type of
thing will continue. I think that's a sad statement to have to make, but
necessary.  We had a club debate on the KY4KY cluster about just this
subject and came to the conclusion that without forcing registrations we
would just be opening ourselves up to exactly what went on yesterday. None
of us liked it but saw no other option to prevent random garbage.

 

73 - Dave N8ZFM

Sysop of KY4KY-3 Cluster

KY DX Association

 

 

From: Michael Carper <mike at wa9pie.net>
Reply-To: The DXSpider Support list <dxspider-support at dxcluster.org>
Date: Friday, December 5, 2014 at 12:22 PM
To: The DXSpider Support list <dxspider-support at dxcluster.org>
Subject: Re: [Dxspider-support] Blocking a bad node (rather than bad
spotter)

 

I found it.  Thanks. 

 

I suppose there's absolutely no way to prevent this without EVERYONE going
to registrations (usernames AND passwords).

 

Mike, wa9pie

 

On Fri, Dec 5, 2014 at 4:38 AM, Mike McCarthy, W1NR <lists at w1nr.net> wrote:

Actually, blocking a node is rather drastic. Contacting the sysop and
locking out the offending callsigns is a better solution. Unless it is
generating lots of anonymous garbage.

set/badspot w2re

will block spots and announce messages by w2re

set/lockout w2re

will prevent that call from connecting to your node

Mike, W1NR


On 12/05/2014 05:22 AM, Mike McCarthy, W1NR wrote:
>
> set/badnode ja2yyf-9
>
> Mike, W1NR
>
> On 12/04/2014 06:38 PM, Michael G. Carper wrote:
>> Is there anything we can do to shut off spots from JA2YYF-9?  (I've
>> blocked spotters before. but not nodes.)
>>
>>
>>
>> Here's what I'm seeing with the latest (which is similar to the pirating
>> of WW2DX earlier today).
>>
>>
>>
>> It seems to be coming in from the same JA2YYF-9 node that we saw with
>> other calls a while back.
>>
>>
>>
>> <-  sh/route w2re
>>
>> W2RE on JA2YYF-9 via VE7CC-1(5),W1NR(6)
>>
>> WA9PIE-2>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at dxcluster.org
>> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>

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

 


-- 
This message was scanned by ESVA and is believed to be clean. 
Click here to report this message as spam.
<http://h0stname/cgi-bin/learn-msg.cgi?id=B55EC27FD8.83791> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20141205/a54d04e3/attachment-0001.html>