[Dxspider-support] Another flooding of forged spots

Mon Feb 10 13:18:46 GMT 2025

Chris,

That is what a v2 network implies, an evolution of the protocol.

Kin

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Lists via Dxspider-support
Enviado el: lunes, 10 de febrero de 2025 12:06
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Lists <lists at g1fef.co.uk>
Asunto: Re: [Dxspider-support] Another flooding of forged spots

Or a v2 protocol that does include origin identification (and path data) of a spot, along with ssh support for node interconnects, and…

Chris - G1FEF

On 10 Feb 2025, at 09:56, Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:

You can't trace the originating node without having access to all the nodes.
The only thing that is really effective is for the nodes to be trustworthy, and this can only be achieved with authentication of all node members and users.
Which brings us to a v2 network that can co-exist with the current one, I think.

Kin

Enviado desde Outlook para Android <https://aka.ms/AAb9ysg> 

  _____  

De: IZ2LSC <iz2lsc.andrea at gmail.com>
Enviado: lunes, febrero 10, 2025 9:48:59 a. m.
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: s50u at s50e.si <s50u at s50e.si>; Kin <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] Another flooding of forged spots

I think we all agree that these spots were deliberately forged by someone that has nothing more interesting to do.

Now, how can we track the entry point? I mean, the first legitimate node that received these spots and forwarded to the rest of the network?
Can we add an option in the PC61 (or PC11) to "record route" the path that every spot is doing?
I.e. every node append to the pc61 message his call and ip?

Andrea

-->

On Mon, Feb 10, 2025 at 8:55 AM Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> > wrote:
I think it's safe to say that this is not a software glitch, it's an attempt to manipulate the spots to make it difficult to know which is the ‘good/real’ spot.

Kin

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk <mailto:dxspider-support-bounces at tobit.co.uk> > En nombre de Danilo Brelih via Dxspider-support
Enviado el: lunes, 10 de febrero de 2025 8:47
Para: Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
CC: Danilo Brelih <s50u at s50e.si <mailto:s50u at s50e.si> >
Asunto: Re: [Dxspider-support] Another flooding of forged spots

Kin via Dxspider-support je 10.2.2025 ob 8:16 napisal:
Here you can see the patterns perfectly:

1739128184^(chan) <- I VE7CC-1 PC61^7038.2^OZ6P^09-Feb-2025^1909Z^RTTY^S51J-2^S50CLX^95.159.226.41^H48^~
1739128186^(chan) <- I VE7CC-1 PC61^14250.2^OZ6P^09-Feb-2025^1909Z^UP UP UP!^S51J-2^F6BVP-3^95.159.41.226^H59^~
1739128186^(chan) <- I VE7CC-1 PC61^7034.8^OZ6P^09-Feb-2025^1909Z^award^S51J-2^PB4PT-8^95.159.226.41^H20^~
1739128186^(chan) <- I VE7CC-1 PC61^28220.7^OZ6P^09-Feb-2025^1909Z^55^S51J-2^EA4RCH-5^95.41.159.226^H81^~
1739128186^(chan) <- I VE7CC-1 PC61^7116.9^OZ6P^09-Feb-2025^1909Z^UP^S51J-2^CX2SA-8^95.226.159.41^H18^~
1739128186^(chan) <- I VE7CC-1 PC61^21447.4^OZ6P^09-Feb-2025^1909Z^UP^S51J-2^SM4ONW-7^95.159.41.226^H67^~

The last pattern illustrates that what happens has no correlation with the usability of N1MM+ contest software.

I can confirm as the spotter below is my "client" and he was connected to my cluster all weekend long with some spots sent. I am checking my logs and what I notice is that although it has changed some connections between LOCAL ISP access via adsl/mobile but never connect outside the ORIGIN cluster of spots sent. He's SSID used was always the same for all sent spots only his IP has changed two, three times. So only the first spot is correct and all the others are the work of the dirty script of forged spots we know from previous years or a bug somewhere in one of the cluster programs on the network?
1739128184^(chan) <- I VE7CC-1 PC61^7038.2^OZ6P^09-Feb-2025^1909Z^RTTY^S51J-2^S50CLX^95.159.226.41^H48^~
CU Dan
-- 
S50CLX DX Cluster <https://s50clx.infrax.si/> 
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto: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/20250210/a7b7f862/attachment-0001.htm>