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

[Mike McCarthy, W1NR]

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
>