[Dxspider-support] Spot with False Origin Nodes

[Luigi Carlotto IK5ZUK]

Hi Dirk,

first of all, thank you for your great and hard work with DxSpider!

Regarding your proposal, I'm agree to implement this kind of detection 
to filter out the forged spots.
For the first 3-6 hours or until routing table is not fully gained, that 
mechanism of forged spot detection could be disabled and to be 
subsequently enabled when the Spider's routing table is fully populated.

73 Luigi IK5ZUK


Il 29/01/2025 18:28, Dirk Koopman via Dxspider-support ha scritto:
> The real problem is that the spotter and/or ip address in a PC11 / 
> PC61 is forged. This is relatively easy to detect as are spots with a 
> forged origin node IFF we deploy the nuclear option:
>
> Check the callsign, node and ip address with the values in the routing 
> table.
>
> The problem with this is that if a node is restarted it will take up 
> 3-6 hours to gain a full routing table AND it is likely that AR 
> Cluster originated spots could not be validated.
>
> This last issue would mean that there could well be a loud wailing and 
> gnashing of teeth by the more erm... dedicated DXer who would demand 
> ALL spots from EVERYWHERE even though the ~1% of spots that are AR-C 
> only generated could be swamped by all the forgeries.
>
> Now nodes normally run for months at a time. So this *could* be done.
>
> But should it?
>
> 73 Dirk G1TLH
>
>
>
> On 29/01/2025 13:11, Kin via Dxspider-support wrote:
>> Hi,
>>
>> Since the 27th, I have started seeing spots appearing from my EA3CV-3 
>> node.
>>
>> It is impossible for these spots to have originated from my node, as 
>> it is
>> password-protected.
>> I fear that other nodes may be experiencing the same issue.
>> This started after we raised concerns about a node that couldn't 
>> identify
>> its connection and used a time string in the comment field-remember? 
>> Well,
>> now that node is no longer visible, and the spots no longer contain that
>> string, yet multiple spots are still being sent.
>>
>> 1737969291^(chan) <- I PI4CC 
>> PC61^18104.0^II5WWA^27-Jan-2025^0914Z^FT4 award
>> Worldwide^IK5FKE^EA3CV-3^54.7.76.202^H30^~
>> 1737985919^(chan) <- I PI4CC PC61^21031.0^8E3R^27-Jan-2025^1351Z^CW 
>> WWA25
>> ham.cm/wwa^YB1CDA^EA3CV-3^24.89.103.72^H30^~
>> 1738058541^(chan) <- I PI4CC PC61^21074.0^8E3R^28-Jan-2025^1002Z^2025 
>> WWA
>> ft8^YB3CUG^EA3CV-3^159.16.127.210^H30^~
>> 1738061474^(chan) <- I PI4CC PC61^14034.0^II4WWA^28-Jan-2025^1051Z^cw 
>> thanks
>> wwa^I4GAD^EA3CV-3^185.120.124.165^H30^~
>> 1738135942^(chan) <- I PI4CC PC61^7162.0^II2WWA^29-Jan-2025^0732Z^
>> ^IK2YCW^EA3CV-3^131.4.148.117^H30^~
>> 1738154649^(chan) <- I PI4CC PC61^28023.0^II3WWA^29-Jan-2025^1244Z^tu
>> wwa^IV3ZXQ^EA3CV-3^218.41.168.166^H30^~
>>
>> I am going to block EVERYTHING related to the event these spots carry,
>> including the DX stations.
>>
>> Kin EA3CV
>>
>>
>>
>>
>> _______________________________________________
>> 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