[Dxspider-support] Summary of Spoofed Spots CQ WW CW

[JOSEPH REED]

Apparently I’m not worthy either, or by proactively blocking 217.61.58.0/24 at the firewall prior to the contest I had 0+0 as well.

Thanks for the reminder to upgrade prior to the contest, I updated and applied the latest country files prior to the contest.  My amp blew up a week before (LDMOS) and I had a bad cold so didn’t operate but the node was ready for those who could,

I liked your table of PC92 nodes.  Indeed there is a lot of outdated software out there.  And so simple to update :)

Nice bit of work to get 363 out and publishing the IP of the ham acting badly.  I’m sure it took some wind out of the sails of the bot operator.

Again, thanks for a super nifty bit of software. 

Joe N9JR

> On Nov 29, 2021, at 7:21 AM, Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> That's a 1000 less than last time.  But build 363 managed to stop:
> 
> WA9PIE-2 78 + 46 = 124
> GB7DJK   0 + 0 = 0
> GB7BAA   0 + 0 = 0
> 
> He does a 'sh/cl' every time. Perhaps he's looking for nodes with a certain number of connected users/nodes? Maybe I am not considered worthy. I could be a bit miffed by this. But I expect I'll get over it. GB7BAA is registration only.
> 
> You can look at your reasonably up to date  'mojo' nodes with these two commands to count how many times your node was used with these two commands:
> 
> grepdbg -2 progress CMD: DX 217.61.58.23 | wc -l
> grepdbg -1 progress CMD: DX 217.61.58.23 | wc -l
> 
> 73 Dirk G1TLH
>