[Dxspider-support] Again
Terry Hunt
terry at thenuttyhunt.house
Sat Mar 22 16:24:29 GMT 2025
I agree Jose,
I recently went through the exercise with K4HNT-2 to authenticate partner Nodes. I had one partner that never replied to me, after several emails and a week of no response I isolated the node, after two weeks I dropped that partner. I successfully negotiated passwords to all my other partners within a week, and all but one of those are on a two way authentication.
If we as sysops will communicate with our partners and agree on what we each expect from each other, then we can hold each other accountable to that agreement. I may have some partners that are active and we agree to stay within n-2 (accepted standard in most software support) on releases I may have an agreement with another that they are n-3. But I think if we individually set some standards and held ourselves accountable, and begin isolating and dropping our partners that won’t hold up what the two of us agreed to int order to become partners, we should drop them and move on. This would have an effect of forcing the network to self police. Eventually it may mean the older releases isolate themselves into their own cluster network and they may survive at a small scale but most likely they will either upgrade and rejoin the main network or they will lose users because the spots will be limited.
Just my thoughts. I do not have any agreements with my node partners on releases etc, I will say all but one partner is current and the other is I think only one release back.
I just put in a lot of work to move my node into a 24x7 datacenter with the hopes of it becoming a nice stable node. It has RBN support and I don’t mind Hamclock users or any other connection that is operating nicely within the network. My personal operating would be so much different or non existent without the benefit of the clusters. I use them every day.
My opinion
Terry K4HNT
> On Mar 22, 2025, at 11:04 AM, CX2SA - Jose Ma Gonzalez via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>
> Hello All
> Every SysOp should seek relevant information from their partners.
> Basically, do two things:
> 1) Exchange messages via email.
> 2) Use logins and passwords between nodes.
> Check radio activity, DX, contests, web sites, consult available global databases, verify that the callsign hasn't expired, etc.
> In other words, check for convincing information about that callsign.
> It's not easy, but there must be many unmonitored zombie nodes.
> And if the available information isn't clear and concise, delete them.
> Have a nice weekend.
> 73, Jose
>
>
>
> De: Dxspider-support [mailto:dxspider-support-bounces at tobit.co.uk] En nombre de HB9DHG Fulvio via Dxspider-support
> Enviado el: sábado, 22 de marzo de 2025 11:17
> Para: The DXSpider Support list
> CC: HB9DHG Fulvio
> Asunto: Re: [Dxspider-support] Again
>
> Thanks, Keith. That makes sense to me.
>
> It is very sad to see these situations, and I hope we can soon have a clearer network.
>
> Have a great weekend.
>
> HB9DHG Fulvio
>
>
> On Sat, Mar 22, 2025 at 3:11 PM Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>> wrote:
>> Yes, that was my actual spot, done like that to be distinctive so I could see if it was repeated. Whoever is doing this is taking genuine spots and repeating them but with a different frequency/callsign, etc. I’ve not got full debugging enabled so I can’t see the full details.
>>
>> dx 28081 J35X SFH tnx for new slot
>>
>>
>> 73 Keith
>> On 22 Mar 2025 at 14:04 +0000, HB9DHG Fulvio via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>, wrote:
>>
>> Hello Keith,
>>
>> Out of curiosity, did you manually insert the comment "SFH tnx for new slot"? I'm very confused and concerned about why all the comments are the same.
>>
>> Best, HB9DHG Fulvio
>>
>>
>> On Sat, Mar 22, 2025 at 2:31 PM Keith, G6NHU via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>> wrote:
>>> Genuine spots are being replicated on false frequencies.
>>>
>>> I just worked J35X on 10m FT8 and spotted it, there were around 15 instant repeats of the same spot but on different frequencies. The bottom one is my actual spot.
>>>
>>> 73 Keith
>>>
>>> 28339.1 J35X 22-Mar-2025 1327Z SFH tnx for new slot <GI7NKK>
>>> 1855.2 J35X 22-Mar-2025 1327Z SFH tnx for new slot <JR8AMF>
>>> 1865.9 J35X 22-Mar-2025 1327Z SFH tnx for new slot <ON4ZD>
>>> 21045.6 J35X 22-Mar-2025 1327Z SFH tnx for new slot <SP2RTA>
>>> 3658.7 J35X 22-Mar-2025 1327Z SFH tnx for new slot <IK0IHA>
>>> 7053.0 J35X 22-Mar-2025 1327Z SFH tnx for new slot <WA2ILB>
>>> 21111.4 J35X 22-Mar-2025 1327Z SFH tnx for new slot <IK0LYL>
>>> 1818.3 J35X 22-Mar-2025 1327Z SFH tnx for new slot <F4JYF>
>>> 7175.3 J35X 22-Mar-2025 1327Z SFH tnx for new slot <R6FS>
>>> 21044.0 J35X 22-Mar-2025 1327Z SFH tnx for new slot <F4ALP>
>>> 14173.6 J35X 22-Mar-2025 1327Z SFH tnx for new slot <IU5RCJ>
>>> 14308.7 J35X 22-Mar-2025 1327Z SFH tnx for new slot <PU2OXB>
>>> 14201.8 J35X 22-Mar-2025 1327Z SFH tnx for new slot <EA4M>
>>> 7274.3 J35X 22-Mar-2025 1327Z SFH tnx for new slot <G4PEN>
>>> 1877.2 J35X 22-Mar-2025 1327Z SFH tnx for new slot <WA1BXY>
>>> 28081.0 J35X 22-Mar-2025 1327Z SFH tnx for new slot <G6NHU>
>>> On 22 Mar 2025 at 12:30 +0000, Jan via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>, wrote:
>>>
>>> Its is flooding again
>>>
>>> 73
>>> Jan
>>> PA4JJ
>>>
>>>
>>> --
>>> ____________________________________________________
>>> my dxspider clusters running on a raspberry pi:
>>> pa4jj-2 77.174.195.163 port 7300
>>> pa4jj-3 77.174.195.163 port 7388
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk <mailto: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 <mailto: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 <mailto: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 <mailto: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/20250322/1377cc4a/attachment-0001.htm>
More information about the Dxspider-support
mailing list