[Dxspider-support] The results are in for today (so far)

[Kin]

For those of you who are eager to try it out, you can do the following:
 
./grepdbg '\s+<-\s+I\s+EA3CV-3\s+PC61' | wc -l
./grepdbg 'bad spot ' | awk '{ $1=substr($1,1,9); $2=""; line=$0; if (!seen[line]++) print line }' | wc -l
 
In my case 63.59%
 
Kin EA3CV
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Dirk Koopman via Dxspider-support
Enviado el: miércoles, 12 de febrero de 2025 16:34
Para: Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk>
CC: Dirk Koopman <djk at tobit.co.uk>
Asunto: Re: [Dxspider-support] The results are in for today (so far)
 
On 12/02/2025 15:20, Dirk Koopman via Dxspider-support wrote:

Or to put it another way, most of the traffic sent today is very likely fake.

Houston, we have a problem...

73 Dirk G1TLH

PS If you have had senderverify set > 0 for all of today, you can repeat the example above by changing 'GB7DJK' to a similar node feeding yours from which you are likely to get all/most of your spots.

I'm sorry to say that you will have to wait until the next release to do this test yourselves. You can set $DXProt::sendverify > 0, and it will do the job, but the debug data will be too noisy to get similar numbers. I am on my "test" branch which puts this check in the correct place, so that you get just the one error message per spot instead of one for *every* PC61. 

Sorry pardon

Dirk 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250212/652db922/attachment-0001.htm>