[Dxspider-support] Here we are again (huge flooding)

Mon Feb 17 13:21:15 GMT 2025

Rudy et al

Please can we stop going around in circles.

These spots are clearly fake. Situations like this (and other measures 
that arise from these examples) will be dealt with before the next contest.

You'll have to excuse the small smile I had when you said multiop 
because, I would suggest that (for example):

1739695059^(progress) SPOT: HH3DX on 3635.7 @ 0837Z by 
LX8NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@CS5ARLC-1 '59 Here' route:
1739695059^(progress) SPOT: HH3DX on 3678.0 @ 0837Z by 
LX2NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@KM3T-10 '59 Here' route:
1739695060^(progress) SPOT: HH3DX on 3599.2 @ 0837Z by 
LX1NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@IK6XMI-12 'SES' route:
1739695061^(progress) SPOT: HH3DX on 3514.1 @ 0837Z by 
LX4NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@F5MZN-3 'tnx 73s.' route:
1739695061^(progress) SPOT: HH3DX on 3622.6 @ 0837Z by 
LX6NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@SQ3MZM-3 '' route:
1739695061^(progress) SPOT: HH3DX on 3688.4 @ 0837Z by 
LX1NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@F5UGQ-2 '' route:
1739695061^(progress) SPOT: HH3DX on 3671.5 @ 0837Z by 
LX3NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@WD1L '' route:

Is stunningly good operating, even by multiop standards, to have this 
number of spots being "worked", on one band, within three seconds in a 
CW contest. Especially with all the cross talk that running what must be 
several radios pushing out a (cough) large signal on the same band, in 
the same square mile of territory. The RX frontends must be exceptional 
- all the DXers will want them ;-)

But I want to pick up on this statement of Rudy's: "and have spotter IPs 
different from the cluster they are using". This was, at one time, a 
requirement for all connections to have the IP address, from which they 
are sending spots, to be accurate. Which means that we EXPECT spots to 
come from IP addresses that the spotter is using to connect to a node 
(whether web based, direct or otherwise) to be different from ,and 
external to, the node IP address(es). Further we expect nodes to at 
least try to tell the network - especially during times of high load - 
who is connected to which node. Clearly, in this case, that did not happen.

Erm... BTW, these spots from different operators, and on all bands, all 
seem to be using exactly the same IPV6 'local' address.

73 Dirk G1TLH

On 17/02/2025 12:36, Rudy Bakalov via Dxspider-support wrote:
> All I am suggesting is that understanding the life of logger generated 
> spots, be it self spotted or during S&P, is important to designing 
> effective protection. Such spots may have high rates, spot stations on 
> different frequencies at the same time, and have spotter IPs different 
> from the cluster they are using. And that the pattern of a multi op 
> spotter is likely quite different than the pattern of a casual single op.
>
> Rudy N2WQ
>
> Sent using a tiny keyboard.  Please excuse brevity, typos, or 
> inappropriate autocorrect.
>
>
>> On Feb 17, 2025, at 7:25 AM, Keith, G6NHU via Dxspider-support 
>> <dxspider-support at tobit.co.uk> wrote:
>>
>> 
>> Rudy.
>>
>> Explain this.
>>
>> Seriously, using the logic you’ve been applying in your last few 
>> posts, explain this.
>>
>> HH3DX spotted on 53 different frequencies by variations of the same 
>> callsign in the exact same second, all allegedly through different 
>> nodes.  There are literally hundreds of different instances of this 
>> with different DX callsigns that were dumped on the network over the 
>> weekend.
>>
>> If sysops can’t even accept that we’ve been hit and try and fob 
>> everything off as genuine, we have no chance.
>>
>> 73 Keith.
>>
>>
>>
>> 1739695055^(progress) SPOT: HH3DX on 28430.0 @ 0837Z by 
>> LX1NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@DH1TW-2 '' route:
>> 1739695058^(progress) SPOT: HH3DX on 7058.4 @ 0837Z by 
>> LX5NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@K1AX-11 '55' route:
>> 1739695059^(progress) SPOT: HH3DX on 7118.3 @ 0837Z by 
>> LX3NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@VE2REA 'good signal' 
>> route:
>> 1739695059^(progress) SPOT: HH3DX on 3635.7 @ 0837Z by 
>> LX8NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@CS5ARLC-1 '59 Here' route:
>> 1739695059^(progress) SPOT: HH3DX on 3678.0 @ 0837Z by 
>> LX2NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@KM3T-10 '59 Here' route:
>> 1739695059^(progress) SPOT: HH3DX on 7128.1 @ 0837Z by 
>> LX8NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@IT9OBK-6 '55' route:
>> 1739695059^(progress) SPOT: HH3DX on 21072.2 @ 0837Z by 
>> LX2NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@VE7CC-1 'sorry' route:
>> 1739695060^(progress) SPOT: HH3DX on 21180.6 @ 0837Z by 
>> LX7NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@SV1KP-9 '' route:
>> 1739695060^(progress) SPOT: HH3DX on 3599.2 @ 0837Z by 
>> LX1NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@IK6XMI-12 'SES' route:
>> 1739695060^(progress) SPOT: HH3DX on 21235.9 @ 0837Z by 
>> LX8NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@IV3BVK-5 'strng here' 
>> route:
>> 1739695061^(progress) SPOT: HH3DX on 3514.1 @ 0837Z by 
>> LX4NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@F5MZN-3 'tnx 73s.' route:
>> 1739695061^(progress) SPOT: HH3DX on 14084.7 @ 0837Z by 
>> LX8NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@GB7RAU '' route:
>> 1739695061^(progress) SPOT: HH3DX on 3622.6 @ 0837Z by 
>> LX6NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@SQ3MZM-3 '' route:
>> 1739695061^(progress) SPOT: HH3DX on 28264.1 @ 0837Z by 
>> LX8NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@KD4WLE-3 'tnx QSO' route:
>> 1739695061^(progress) SPOT: HH3DX on 3688.4 @ 0837Z by 
>> LX1NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@F5UGQ-2 '' route:
>> 1739695061^(progress) SPOT: HH3DX on 14177.6 @ 0837Z by 
>> LX0NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@EA3KZ-5 'pilup!!!' route:
>> 1739695061^(progress) SPOT: HH3DX on 7036.7 @ 0837Z by 
>> LX5NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@VE3TOK-1 'award' route:
>> 1739695061^(progress) SPOT: HH3DX on 14066.9 @ 0837Z by 
>> LX5NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@EA1RCF-5 'tnx qso' route:
>> 1739695061^(progress) SPOT: HH3DX on 3671.5 @ 0837Z by 
>> LX3NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@WD1L '' route:
>> 1739695061^(progress) SPOT: HH3DX on 14144.8 @ 0837Z by 
>> LX6NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@IR5V 'pilup!!!' route:
>> 1739695061^(progress) SPOT: HH3DX on 7097.6 @ 0837Z by 
>> LX4NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@KC9AOP-1 '' route:
>> 1739695061^(progress) SPOT: HH3DX on 14012.6 @ 0837Z by 
>> LX4NX(2001:7e8:f631:a801:3cd2:8551:9b32:5db7)@DJ4PK-2 'TKS 5/9' route:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250217/da07164f/attachment.htm>