[Dxspider-support] badnode filtering

Dirk Koopman G1TLH gb7tlh at dxcluster.org
Sat Nov 14 11:53:18 GMT 2009


Mike McCarthy, W1NR wrote:
> I am trying to stop the flood of garbage originating on DXSummit (OH8X)
> by setting the node in the badnode database. However, the spots from
> OH8X-11 and other SSID variants still go through. Is there something
> wrong with the badnode filtering?
> 
> Am I correct in assuming the following originates on OH8X, relayed by
> VE1DXI?
> 
> <- I VE1DXI PC11^1823.2^W7ASS^12-Nov-2009^0005Z^U ARE SUCH A LOSER
> !!^LO5ER^OH8X-11^H98^~
> 

Ah, I see the problem... It's not the code in the node that is at fault, 
it is the command set/badnode! This is now fixed in cvs/git. No restart 
required.

You may also find that a 'rej/spot node_default call_dxcc 666 or by_dxcc 
666' useful. This should remove all spots by countries that it doesn't 
recognise - HOWEVER - this may remove some actual DX (usually of the 
commemorative callsign type).

Dirk



More information about the Dxspider-support mailing list