开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

FW: [CC-User] Bogus DX Spot Attacks on Clusters


 

FYI:

From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io
Sent: Tuesday, April 01, 2025 10:25 AM
To: [email protected]
Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters

What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer.

Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped.

My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through.

Lee VE7CC


 

This is not the first time it happened.

I informed Dave, but no action was needed in DXLab.

Eddy ON5JK

Op 1/04/2025 om 18:47 schreef Dave AA6YQ:

FYI:

From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io
Sent: Tuesday, April 01, 2025 10:25 AM
To: [email protected]
Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters

What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer.
Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped.
My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through.
Lee VE7CC





 

I had noticed "something " going on. For the first time in many months, I turned SKIMMER on, on my spot sources.

It took a few hours, but I found all my spot sources indicators were yellow, and when I opened config, Prune, Compact, Clear and (I think) Recompute were all flashing. Spot Collector was locked up and I had to use Task Manager to kill it.

Spot Database Entries was somewhere around 30K-40K entries.

There is/wasn't error log.

Turning Skimmer off and limiting the database size to 7K entries seems to have fixed whatever it was.

Just another data point, I guess.

7 3
Earl / KD5XB

Sent from Proton Mail Android

-------- Original Message --------
On 4/1/25 10:47 AM, Dave AA6YQ <aa6yq@...> wrote:

FYI:

From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io
Sent: Tuesday, April 01, 2025 10:25 AM
To: [email protected]
Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters

What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer.

Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped.

My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through.

Lee VE7CC









 

+ AA6YQ comments below

I had noticed "something " going on. For the first time in many months, I turned SKIMMER on, on my spot sources.

It took a few hours, but I found all my spot sources indicators were yellow, and when I opened config, Prune, Compact, Clear and (I think) Recompute were all flashing. Spot Collector was locked up and I had to use Task Manager to kill it.

+ Spot Source status displayed as "yellow" means "disconnected, trying to reconnect".

Spot Database Entries was somewhere around 30K-40K entries.

+ That'd a big Spot Database during a popular contest with your own Skimmer running.

There is/wasn't error log.

+ I suggest checking the Windows Error Log:



73,

Dave, AA6YQ

\


 

On Tuesday, April 1st, 2025 at 4:50 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below
<SNIP>
Spot Database Entries was somewhere around 30K-40K entries.

+ That'd a big Spot Database during a popular contest with your own Skimmer running.
Yes, I agree. I just didn't think of the contest, I was just trying to contact a particular DX area, using every spot source / input I could get.

There is/wasn't error log.

+ I suggest checking the Windows Error Log:

Well, I (just now) took a look at it, and it has enough entries that I am not sure I want to pursue it further! <G>

Thanks, Dave. Watch for next email.

7 3
Earl


Sent with Proton Mail secure email.


 

+ AA6YQ comments below
Well, I (just now) took a look at it, and it has enough entries that I am not sure I want to pursue it further! <G>
+ You can reduce your "search" to the time the behavior occurred, and the 5-10 minutes before that.?

? ? ? ? ?Dave