[Dxspider-support] Trying To Understand This

[Christopher Schlegel]

Trying to get information to figure that out. If all the connected nodes
accurately show the users IP then it shouldn't matter as long as the
routing table has the appropriate information. If the routing table can
only handle one IP record per user based on the set home node, It could be
problematic if the user's software doesn't take that into account or they
do not have their home node set appropriately. Or it could be problematic
if some of the nodes report an IP and others do not. Just throwing out
hypotheticals until details can be pinned down.

Chris, WI3W

On Mon, Mar 31, 2025 at 8:10 PM Rudy Bakalov <r_bakalov at yahoo.com> wrote:

> I will have to test it as I don’t see an obvious setting in CC User that
> designates the spotting cluster.
>
> That said, tell me more why would it matter? Let’s say I am connected to 5
> nodes. Regardless of which one I use to spot, all 5 will report I am
> connected to them.
>
> Rudy N2WQ
>
> Sent using a tiny keyboard.  Please excuse brevity, typos, or
> inappropriate autocorrect.
>
>
> On Mar 31, 2025, at 6:56 PM, Christopher Schlegel <sutehk.cs at gmail.com>
> wrote:
>
> 
> Rudy,
>
> When these users connect to multiple nodes, which node is chosen when
> spots are sent?
>
> Chris, WI3W
>
> On Mon, Mar 31, 2025 at 6:16 PM Rudy Bakalov <r_bakalov at yahoo.com> wrote:
>
>> So here is a real life scenario:
>>
>> Folks like using CC User, not to be confused with CC Cluster, to connect
>> to multiple clusters. Same with DX Labs Suite. So how are multiple logins
>> into different clusters handled by these new flood prevention mechanisms?
>> Does the algorithm keep track of all nodes into which the user is connected?
>>
>> Rudy N2WQ
>>
>> Sent using a tiny keyboard.  Please excuse brevity, typos, or
>> inappropriate autocorrect.
>>
>>
>> On Mar 31, 2025, at 6:04 PM, Christopher Schlegel via Dxspider-support <
>> dxspider-support at tobit.co.uk> wrote:
>>
>> 
>> Anthony,
>>
>> This log entry translated...
>>
>> Senderverify has identified the spot of G1GFW by LU6YR from node EA4RCH-5
>> as a invalid spot because LU6YR is not connected to node EA4RCH-5 and
>> therefore can't be valid. The 'WARNING' means that the spot has been passed
>> on with a warning and not dropped. The spot came into your node via
>> KB2FAF-12.
>>
>> Chris, WI3W
>>
>> On Mon, Mar 31, 2025 at 5:54 PM Anthony (N2KI) via Dxspider-support <
>> dxspider-support at tobit.co.uk> wrote:
>>
>>> What exactly does this mean?  I saw it in the watchdbg.
>>>
>>> 21:51:10 (*) PCPROT: Bad Spot G1GFW on 21074.0 by
>>> LU6YR(186.134.127.173)@EA4RCH-5 User LU6YR not on node EA4RCH-5WARNING via
>>> KB2FAF-12 27 hops
>>>
>>>
>>>
>>>
>>> *Regards,Anthony *
>>> *   N2KI*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20250331/245567cd/attachment.htm>