[Dxspider-support] Hop counts

Fri Dec 30 23:37:41 GMT 2022

Whoever is setting hop counts to such low values should desist 
IMMEDIATELY. Frankly the hop count is now redundant, given all the other 
de-duplication measures that nodes have. But, as a backstop, the default 
value should be set to at least 30. But better yet, just leave it at the 
default.

As for the best thing to do: personally, I'd just re-hop them up to some 
minimum. Having said that, I am not seeing the disparity of hop count 
that you are at VA1AAA-1. The "worst" I have seen is some nodes setting 
the initial hop count to 30 (as recommended above)[if you must do it at 
all]. But I have a job running to trap any that pass GB7DJK's way.

I have been concerned about PC11s "winning" the spot "record slot" over 
a PC61 arriving later. I keep meaning to do something about this but I 
keep getting distracted and forget. I feel an ephemeral "per spot queue" 
coming on.

Dirk G1TLH

On 30/12/2022 20:48, Lee Sawkins via Dxspider-support wrote:
> Examples of Hop problem at VA6AAA-1 node
>
> This is really annoying.  Spots were being missed by some nodes because of this.
>
> Since AR Clusters can't process PC61 spots and CC Clusters only down hop by 1, some of the following could only happen at Spider nodes.
> What I have done in self defense is to forward multiple spots.  This means that both spots you see below will be forwarded.  One right after another.  CC Clusters can accept and forward these.  I keep forwarding duplicate spots until the hops count gets above 10.  I may have to increase this.
>
>        GB7DJK ->  4 PC61^14031.0^Z36T^30-Dec-2022^1846Z^Frustrated OM ^Z30T-10^F5LEN-3^51.68.11.211^H5^~
>       VE7CC-1 ->  5 PC11^14031.0^Z36T^30-Dec-2022^1846Z^Frustrated OM^Z30T-10^F5LEN-3^H97^~
>
>          AE5E ->  3 PC61^14023.1^AJ1AJ^30-Dec-2022^1859Z^YOTA CW TNX ES HNY!^NB1N^W1NR^24.91.112.56^H2^~
>       VE7CC-1 ->  5 PC61^14023.1^AJ1AJ^30-Dec-2022^1859Z^YOTA CW TNX ES HNY!^NB1N^W1NR^24.91.112.56^H26^~
>
>        GB7DJK ->  4 PC61^14021.4^E7CW^30-Dec-2022^1908Z^YOTA CW TNX ES HNY!^NB1N^W1NR^24.91.112.56^H2
>          AE5E ->  3 PC11^14021.4^E7CW^30-Dec-2022^1908Z^YOTA CW TNX ES HNY!^NB1N^W1NR^H97
>
>          AE5E ->  3 PC61^7272.0^W2T^30-Dec-2022^1949Z^ ^KK4ADQ^W1NR^76.106.89.109^H2^~
>       VE7CC-1 ->  5 PC11^7272.0^W2T^30-Dec-2022^1949Z^ ^KK4ADQ^W1NR^H97^~
>
>       VE7CC-1 ->  5 PC61^7020.6^CT9ABN^30-Dec-2022^2028Z^ ^NB1N^W1NR^24.91.112.56^H2^~
>          AE5E ->  3 PC11^7020.6^CT9ABN^30-Dec-2022^2028Z^ ^NB1N^W1NR^H97^~
>
> Lee VE7CC
>
> ----- Original Message -----
> From: "The DXSpider Support list" <dxspider-support at tobit.co.uk>
> To: "The DXSpider Support list" <dxspider-support at tobit.co.uk>
> Cc: "Dirk Koopman" <djk at tobit.co.uk>
> Sent: Friday, December 30, 2022 8:23:18 PM
> Subject: Re: [Dxspider-support] Hop counts
>
> I should add that it is technically possible for DXSpider nodes to rehop
> PCxx sentences, particularly in the downward direction.
>
> On 30/12/2022 20:20, Dirk Koopman via Dxspider-support wrote:
>> Some nodes deliberately limit hop counts to some low number like 10 or
>> 15. A pity then, that spots that travel through nodes (IIRC AR-C)
>> where they are "rehopped" back to 98 (or so). I did some research on
>> this several years ago and that was the conclusion I came to at the
>> time. But things may have changed since then.
>>
>> 73 Dirk G1TLH
>>
>> On 30/12/2022 18:41, Lee Sawkins via Dxspider-support wrote:
>>> Can someone explain to me why my cluster receives some dx spots with
>>> a hop count of say H3 or lower from one of my node links and almost
>>> immediately receives another identical spot almost immediately from
>>> another node partner with a hop count of H97.  This first one is sent
>>> out to my node connections with a hop count of H2 or less, which
>>> means it should soon be hopped out and not further forwarded.  Why is
>>> some intermediate node doing this.  Is it an attempt to sabotage the
>>> distribution of some spots?
>>>
>>> Hop numbers from a couple of specific nodes are particularly low.
>>> These include W1NR, F5LEN-3 and EA6VQ-2.
>>>
>>> 73 Lee VE7CC
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support