[Dxspider-support] Fwd: Max Spot per Minute (how to avoid flooding)

[IZ2LSC]

I know there is the following knob, but if the originating node is not up
to date (or is not a spider), then the flood is sent into the network.

   Added cmd entry rate limiting. If a user sends X commmands in Y secs then
   they are disconnected without notice. The defaults are X
   ($DXCommandmode::maxcmdcount) = 16 and Y ($DXCommandmode::cmdinterval) =
9.


Andrea, IZ2LSC

-->


On Tue, Jan 21, 2025 at 10:07 PM <ea3cv at cronux.net> wrote:

> The only thing I can think of is to treat spotter+time as a duplicate
> variant within a 1s window.
> I don't know if Dirk has something implemented.
> I'll look tomorrow, I'm curious.
>
> Kin
>
>
> Enviado desde Outlook para Android <https://aka.ms/AAb9ysg>
>
> ------------------------------
> *De:* Dxspider-support <dxspider-support-bounces at tobit.co.uk> en nombre
> de IZ2LSC via Dxspider-support <dxspider-support at tobit.co.uk>
> *Enviado:* martes, enero 21, 2025 9:30:48 p. m.
> *Para:* The DXSpider Support list <dxspider-support at tobit.co.uk>
> *CC:* IZ2LSC <iz2lsc.andrea at gmail.com>
> *Asunto:* [Dxspider-support] Fwd: Max Spot per Minute (how to avoid
> flooding)
>
> Hi sysops!
> I was reviewing my cluster stats when I noticed this spike in spot per
> minute (see attached image).
>
> [image: immagine.png]
>
>
> Looking at the logs I can see a flood of 55 spots coming in the same
> second from the same user, an extract below:
>
>
> 7074.4^DH2YBG^1737474360^FT8^KC9LFD^32^226^DB0ERF-5^28^14^8^4^^^204.93.149.214
>
> 7074.4^GM6URC^1737474360^FT8^KC9LFD^65^226^DB0ERF-5^27^14^8^4^^^204.93.149.214
>
> 7074.4^N5TLH^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^7^4^8^4^^^204.93.149.214
>
> 7074.4^LA8ENA^1737474360^FT8^KC9LFD^123^226^DB0ERF-5^18^14^8^4^^^204.93.149.214
>
> 7074.4^P40AA^1737474360^FT8^KC9LFD^326^226^DB0ERF-5^11^9^8^4^^^204.93.149.214
>
> 7074.4^F5SJF^1737474360^FT8^KC9LFD^42^226^DB0ERF-5^27^14^8^4^^^204.93.149.214
>
> 7074.4^VK2WN^1737474360^FT8^KC9LFD^198^226^DB0ERF-5^59^30^8^4^^^204.93.149.214
> 7074.4^N1UL^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^8^5^8^4^^^204.93.149.214
>
> 7074.4^KA9SOG^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^8^4^8^4^^^204.93.149.214
>
> 7074.4^VK3YW^1737474360^FT8^KC9LFD^198^226^DB0ERF-5^59^30^8^4^^^204.93.149.214
>
> 7074.4^N9IBM^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^8^4^8^4^^^204.93.149.214
>
> 7074.4^W5ORC^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^8^5^8^4^^^204.93.149.214
>
> 7074.4^KP2BH^1737474360^FT8^KC9LFD^119^226^DB0ERF-5^11^8^8^4^^^204.93.149.214
> 3573.4^K8CW^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^8^4^8^4^^^204.93.149.214
>
> 3573.4^P40AA^1737474360^FT8^KC9LFD^326^226^DB0ERF-5^11^9^8^4^^^204.93.149.214
>
> 3573.4^K1TAP^1737474360^FT8^KC9LFD^226^226^DB0ERF-5^8^5^8^4^^^204.93.149.214
>
>
> Is there a way to activate a sort of flooding protection?
>
>
> Thanks and 73
>
>
> Andrea, IZ2LSC
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250121/87a5c3f9/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: immagine.png
Type: image/png
Size: 33364 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250121/87a5c3f9/attachment-0001.png>