[Dxspider-support] Are spots being lost on the Network?

[Keith Maton]

Some time ago, there were posts here encouraging SysOps to block nodes running out of date versions to ‘encourage’ them to update.

I don’t recall I ever did this but I’ve just been through my lockout list (sh/lockout all) and the first six nodes were listed.  I’ve unlocked them (unset/lockout [callsign]).

There are 320 callsigns in my sh/lockout all list which seems a lot to me

Is this the blocking you refer to, Kin?

73 Keith

> On 7 Aug 2024, at 08:54, Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> Hi,
> 
> Today I received a query from a user complaining that the spots with his
> callsign were not appearing on several nodes.
> After analysing the logs and testing from different nodes, the conclusion
> was that there are nodes (and with many users) that are blocked by other
> nodes. This has the effect of appearing or not in parts of the network.
> As the user is not on any blocking list and there are no blockages to this
> node on the nodes I manage, the conclusion is that this is affecting many
> users.
> 
> For this reason, I take this opportunity to pass on a list of nodes with a
> significant volume of spots sent to the network and which are out of date:
> 
> 9A0DXC     5455 115
> DB0SUE-7   5455 136
> DD5XX-10   5455 196
> EA6VQ-2    5455 38
> F5LEN-7    5455 166
> N0VD-7     5455 181
> OK0DXI     5455 0.52
> PY3NZ-8    5455 115
> SM6YOU-7   5455 82
> SR4DXC     5455 198 
> 
> DB0LJ-6    5457 499
> EA4FIT-2   5457 451
> I8ZSE-1    5457 496
> RW3XA-8    5457 497
> 
> Upgrading might help some of the blocked nodes to get out of the list, this
> is just an opinion, because there are other factors that might be
> influencing these blockages.
> 
> 73 de EA3CV
> 
> 
> <winmail.dat>_______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support