[Dxspider-support] Weekend data
djk
djk at tobit.co.uk
Wed Apr 2 09:35:30 BST 2025
On 02/04/2025 09:22, Keith, G6NHU via Dxspider-support wrote:
> I wrote a whole wall of text but I’ve deleted it as there are just two
> steps.
>
> Set dxspider to reject all spots without IP addresses (can this
> currently be done?)
>
Yes, but probably needs a little bit of work from me to make easier to
do. I'm not certain it will help because it does cut off a sizeable
chunk of US spots. And then there are all those pesky unupdated nodes.
> Disconnect all links to the highly vulnerable and out of date AR
> Cluster nodes.
>
There are very few connections and those are all up to date nodes.
> 73 Keith.
>
>
>
>
> On 1 Apr 2025 at 18:56 +0100, Michael Carper, Ph.D. via
> Dxspider-support <dxspider-support at tobit.co.uk>, wrote:
>
> Good point, Keith.
> What are the steps for doing that?
> Has anyone made any gains on identifying the offender(s)?
> Mike, WA9PIE
> On Tue, Apr 1, 2025 at 12:46 PM Keith, G6NHU via Dxspider-support
> <dxspider-support at tobit.co.uk
> <https://mailto:dxspider-support@tobit.co.uk>> wrote:
>
> I read that thread a few minutes ago and Lee is making
> interesting comments, some I agree with but I think that some
> others are simply wrong. For those who want to read it, it’s
> here:
> https://groups.io/g/CC-User/topic/bogus_dx_spot_attacks_on/112020247
> However, he raises a very important point, one which Dirk has
> also touched on (and that I’ve mentioned a couple of times)
> regarding AR Clusters.
> "Other types of software such as AR Cluster simply pass
> everything they get. Since AR Cluster doesn't give IP
> addresses with their spots it makes it difficult to determine
> whether these spots are bogus or not. A simple solution that
> is used by some sysops it to drop all AR Cluster originated
> spots!"
> And:
> "I am now blocking all spots without IP addresses. This
> includes all spots from AR Clusters etc."
> It’s been proven and demonstrated that AR Cluster nodes are a
> weak spot on the network and as the creator is SK, no further
> development will happen. For the good of the network, we need
> to be removing links to AR Cluster nodes.
> Hopefully Jim will be updating his dxcluster telnet list very
> soon which will give an idea of how many AR Cluster nodes are
> still active but the sooner these are all isolated or the
> owner changes them to something else, either CC Cluster or
> DXSpider, the better for everyone.
> 73 Keith.
> On 1 Apr 2025 at 18:19 +0100, Michael Carper, Ph.D. via
> Dxspider-support <dxspider-support at tobit.co.uk
> <https://mailto:dxspider-support@tobit.co.uk>>, wrote:
>
> On a related note, did anyone see this?
> Mike, WA9PIE
> ===========
> From: CC-User at groups.io
> <https://mailto:CC-User@groups.io> [mailto:CC-User at groups.io
> <https://mailto:CC-User@groups.io>] On Behalf Of Lee
> Sawkins via groups.io <http://groups.io/>Sent: Tuesday,
> April 01, 2025 10:25 AMTo: CC-User at groups.io
> <https://mailto:CC-User@groups.io>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
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> <https://mailto:Dxspider-support@tobit.co.uk>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> <https://mailto:Dxspider-support@tobit.co.uk>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> On Tue, Apr 1, 2025 at 8:45 AM Kin via Dxspider-support
> <dxspider-support at tobit.co.uk> wrote:
>
> Absolutely brilliant 🤣🤣🤣
>
> Kin EA3CV
>
> *De:* Dxspider-support <dxspider-support-bounces at tobit.co.uk> *En
> nombre de* Danilo Brelih via Dxspider-support
> *Enviado el:* lunes, 31 de marzo de 2025 22:47
> *Para:* Keith, G6NHU via Dxspider-support
> <dxspider-support at tobit.co.uk>
> *CC:* Danilo Brelih <s50u at s50e.si>
> *Asunto:* Re: [Dxspider-support] Weekend data
>
> …
>
> This is Linux land.
> In silent nights you can hear the Windows machines rebooting.
> https://s50clx.infrax.si
>
> GL Dan
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250402/a726384a/attachment-0001.htm>
More information about the Dxspider-support
mailing list