[Dxspider-support] Epoch time stamp / multi times login

[Dirk Koopman]

The locked out ones are easy, because you ban them based on the "locked 
out" or just the "RA4HL" string.

You could try sending RT1M a message  with "SP RT1M", I tried that the 
other day for the first time in more years than I care to admit and I 
got a reply!

Clearly they don't understand what to put into their crontab files, e.g:

00,10,20,30,40,50 * * * * start_connect('gb7djk') unless connected('gb7djk')

Dirk

On 08/05/2020 13:14, Peter via Dxspider-support wrote:
> Hi sysops!
>
> There are a lot of misconfigured PCs that make a connection to the 
> DX-clsuter network
> A common problem is  they start 2 clients thats connect  with the same 
> callsign and where auto reconnect is active
>
> 1588550278^connect 300: login:
> 1588550278^connect 300: timeout set to 60
> 1588550279^connect 300: RT1M
> 1588550279^DXCommand
> 1588550279^RT1M bumped off by 78.37.108.198, disconnected
> 1588550279^DXCommand
> 1588550279^RT1M disconnected
> 1588550279^DXCommand
> 1588550279^RT1M connected from 78.37.108.198
>
> An other problem is a fast reconnect.
> You can set lockout the call  you want, but its keeps reconnecting al 
> the time.
>
> 1588832564^connect 126: %FF%FB%%FF%FD%03%FF%FB"%FF%FD%05RA4HL
> 1588832564^DXCommand
> 1588832564^RA4HL on 5.164.179.244 is locked out, disconnected
> 1588832564^connect 127: login:
> 1588832564^connect 127: timeout set to 60
> 1588832564^connect 127: RA4HL
> 1588832564^DXCommand
> 1588832564^RA4HL on 5.164.179.244 is locked out, disconnected
> 1588832564^connect 128: login:
> 1588832564^connect 128: timeout set to 60
> 1588832564^connect 128: %FF%FB%%FF%FD%03%FF%FB"%FF%FD%05RA4HL
> 1588832564^DXCommand
> 1588832564^RA4HL on 5.164.179.244 is locked out, disconnected
> 1588832565^connect 129: login:
> 1588832565^connect 129: timeout set to 60
> 1588832565^connect 129: RA4HL
> 1588832565^DXCommand
> 1588832565^RA4HL on 5.164.179.244 is locked out, disconnected
> 1588832565^connect 130: login:
> 1588832565^connect 130: timeout set to 60
> 1588832565^connect 130: %FF%FB%%FF%FD%03%FF%FB"%FF%FD%05RA4HL
> 1588832565^DXCommand
> 1588832565^RA4HL on 5.164.179.244 is locked out, disconnected
> 1588832565^connect 131: login:
> 1588832565^connect 131: timeout set to 60
> 1588832565^connect 131: RA4HL
> 1588832565^DXCommand
> 1588832565^RA4HL on 5.164.179.244 is locked out, disconnected
>
> I add his IP to the firewall, but every day he got an other IP adres :-(
>
> Via fail2ban you can make some rules and block those as**l automagic.
> But fail2ban those work with the unix epoch time string.
>
> 3 questions:
> How do you deal with those problems?
> Has anyone makes fail2ban working with a epoch time stamp
> It the debug file configurable to change the time stamp so fal2ban can 
> read the log file?
>
> Peter
> PC2a
> Sysop PI4CC
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support