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

[IZ2LSC]

AFAIK the lockout list is used to stop users/nodes to connect (login) to
the cluster. This doesn't mean that you cannot receive a spot originated by
that user/node.
The list is populated with several entries by default, see here:
https://mailman.tobit.co.uk/pipermail/dxspider-support/2022-March/015932.html

73
Andrea
iz2lsc


-->


Il giorno mer 7 ago 2024 alle ore 11:45 Kin via Dxspider-support <
dxspider-support at tobit.co.uk> ha scritto:

> Keith, the list you have obtained represents not only nodes, but also
> (mostly) users.
> It is a consequence (I think) of the commands: set/lock, set/badnode and
> set/baduser.
>
> The causes are diverse. They range from a sysop who wants to block junk
> spot traffic, to those who don't want to receive advertisements from
> certain nodes, to those who consider that certain nodes represent a problem
> for the network.
>
> Sometimes a node is blocked and we forget to unblock it afterwards. I'm
> very meticulous about this, the ones I've blocked for junk traffic and that
> I haven't been able to get a response from the sysops, when normality has
> been restored, I've unblocked them.
>
> The list you have obtained is merely informative, so it only indicates
> that a certain callsign is blocked on one or more nodes in the network, but
> it is not automatically used to block them on the nodes that receive this
> information.
> I have neighbouring nodes that are on the list and from which I still
> receive spots.
>
> There is another type of blocking that is "invisible" to the rest of the
> sysops. This is when filtering rules are applied to the routes of our
> adjacent nodes.
> Since we don't have a traceroute-style command, we can't be sure where all
> or part of the traffic is cut off.
>
> But back to the topic that originated this thread, I still think it is
> essential that we sysops look after our Network. That we make an effort to
> keep it in good shape, which does not mean that the nodes run without
> maintenance. What my node puts on the Network affects the whole Network.
>
> Kin
>
>
>
>
> Translated with DeepL.com (free version)
>
> -----Mensaje original-----
> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
> Keith Maton via Dxspider-support
> Enviado el: miércoles, 7 de agosto de 2024 10:28
> Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
> CC: Keith Maton <g6nhu at me.com>
> Asunto: Re: [Dxspider-support] Are spots being lost on the Network?
>
> 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
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240807/66e35bbe/attachment.htm>