[Dxspider-support] DXSpider multiple calls with same IP.
Dirk Koopman
djk at tobit.co.uk
Wed Mar 15 10:55:53 GMT 2023
This is called 'sniping'. It has been disabled for some time.
The process works like this:
* (normal) user logs in
* user send(s) spot, announces etc
* they are queued up for a period (default: 60 seconds)
* after that period, any queued up stuff is sent onwards
* thereafter normal operation is restored. All spots etc are sent
immediately
$self->{isslugged} = 0 if $self->{priv} || $user->registered ||
($user->homenode && $user->homenode eq $main::mycall);
This means that if the user has privilege (> 0) (this means you Alain),
is registered or has done a set/homenode ON4KST, then this restriction
goes away.
This "feature" was added in November 2021.
Dirk
On 15/03/2023 07:48, STIEVENART Alain via Dxspider-support wrote:
> Hi Kin,
>
> Added a 10 seconds delay between the login and the dx spot... still
> not forwarded... pffff. Strange that my own dx spots work immediately
> and perfectly, the others not.
>
> 73s Alain ON4KST.
>
> On 14-03-23 17:23, Kin wrote:
>> Alain,
>>
>> I think what is happening to you is that the user connects and
>> immediately tries to send a spot. This operation is used by cluster
>> abusers, so until some time has passed they will not be allowed to
>> send a spot. I don't remember the time, but it's not long.
>>
>> Kin EA3CV
>>
>>
>> -----Mensaje original-----
>> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre
>> de STIEVENART Alain via Dxspider-support
>> Enviado el: martes, 14 de marzo de 2023 16:33
>> Para: Dxspider-support at tobit.co.uk
>> CC: STIEVENART Alain <on4kst at skynet.be>
>> Asunto: [Dxspider-support] DXSpider multiple calls with same IP.
>>
>> Hi,
>>
>> I am running the ON4KST-2 DXSpider for several years. Sinds the last
>> upgrade to V1.57 build 516 dx spots done with my ON4KST callsign
>> (sysop) work BUT dx spots done from other callsigns using the same IP
>> address are not forwarded. What is the cause? Is it an IP address
>> limitation?
>> How to solve it?
>>
>> Example (ON4KST-2 running on 141.94.171.16):
>>
>> 1678789414^(connect) connect 247: BA4SI
>> 1678789414^(state) BA4SI channel func state 0 -> prompt
>> 1678789414^(*) BA4SI connected from 141.94.171.16 cols 80
>> 1678789414^(progress) CMD: 'show/cluster ' by BA4SI ip: 141.94.171.16
>> 0mS
>> 1678789414^(*) spotter BA4SI/BA4SI
>> 1678789414^(progress) CMD: 'DX 50313 5w1sa CQ -8' by BA4SI ip:
>> 141.94.171.16 1mS --> NOT FORWARDED.
>> 1678789435^(*) BA4SI disconnected
>>
>> 73s Alain ON4KST.
>>
>>
>> --
>> Cet e-mail a été vérifié par le logiciel antivirus d'Avast.
>> www.avast.com
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>
More information about the Dxspider-support
mailing list