[Dxspider-support] FAO Dirk - Someone's not happy

[Keith Maton]

To do my bit, I’ve just enabled registration on my node.  I don’t have many users, I don’t think I’ve ever had more than ten connected at any one time but I’ll keep an eye out and manually register the ones I recognise as I see them online.

73 Keith G6NHU


> On 26 Feb 2023, at 22:00, Rene Olsen via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> Hi.
> 
> I totally aggree that we need to get al these old nodes weeded out, as they are just causing 
> problems for the network.
> 
> I am also of the opinion that upgrading to the MOJO branch, and enabling registration, with or 
> without password, should be a requirement to be part of the network.
> 
> It seems to me like DJ4PK are linked to DD5XX-10, HB9DRV-9 and/or DD5XX-10, 
> WA9PIE-2, depending on how to interpret the stat/route_node command.
> 
> As a minimum DJ4PK-2 should be set as isolated until it gets updated and registration 
> enabled. I believe that just enabling registration alone, will weed out most of the spots we are 
> seing.
> 
> Let me just say, that if password for users will become a must, or we must use encrypted 
> links and what not between nodes, then OZ5BBS-7 that has been running for 25+ years will 
> no longer be around. But I guess the plan is to have less clusters.
> 
> I aggree that we have a problem, but it can be solved with way less drastic measures. Like 
> we already have done.
> 
> The way ahead will be to get everyone on the MOJO branch and enable registration, so that 
> no one will be able to do hit and run spotting.
> 
> Unfortunately we have some big nodes with lots of links still running old versions, and not 
> having registration turned on. And until that gets fixed the problem will persist.
> 
> If they do not want to upgrade and enable registration, I guess the only option is to set them 
> as isolated.
> 
> Vy 73 de René / OZ1LQH
> 
> On 26 Feb 2023 at 15:14, Stephen Carroll via Dxspider-support wrote:
> 
>> What we do know is node DJ4PK-2 is still using V1.55 build 0.67 !!!
>> 
>> On Sun, Feb 26, 2023, 3:05 PM Keith Maton via Dxspider-support <
>> dxspider-support at tobit.co.uk> wrote:
>> 
>>> 14000.0^*G1TLH*^1677444780^the cluster network is broken^*G1TLH*
>>> ^61^61^DJ4PK-2^27^14^27^14^^^163.172.11.79
>>> 
>>> 14000.0^*G1TLH*^1677445020^do i really need to prove it?^*G1TLH*
>>> ^61^61^DJ4PK-2^27^14^27^14^^^84.73.221.190
>>> 
>>> 14000.0^*G1TLH*^1677445140^the network will be taken down^*G1TLH*
>>> ^61^61^DJ4PK-2^27^14^27^14^^^163.172.11.79
>>> 
>>> 14000.0^*G1TLH*^1677445200^get ready to rumble^*G1TLH*
>>> ^61^61^DJ4PK-2^27^14^27^14^^^163.172.11.79
>>> 
>>> 
>>> Not sure how to interpret this or what to block?
>>> 
>>> 
>>> 
>>> 
>>> On 26 Feb 2023, at 21:00, Keith Maton via Dxspider-support <
>>> dxspider-support at tobit.co.uk> wrote:
>>> 
>>> 14000.0 G1TLH       26-Feb-2023 2059Z the network will be taken down
>>>                            <G1TLH>
>>> 14000.0 G1TLH       26-Feb-2023 2057Z do i really need to prove it?
>>>                             <G1TLH>
>>> 14000.0 G1TLH       26-Feb-2023 2053Z the cluster network is broken
>>>                             <G1TLH>
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 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