[Dxspider-support] Again
Christopher Schlegel
sutehk.cs at gmail.com
Sat Mar 22 17:59:38 GMT 2025
Entries at WI3W-2...
DX de G6NHU: 7074.0 G6NHU testing
1734Z
22Mar2025 at 17:34:38 (chan) <- I N7OD
PC11^7074.0^G6NHU^22-Mar-2025^1734Z^testing^G6NHU-73^G6NHU^H98^~
Chris WI3W
On Sat, Mar 22, 2025 at 1:50 PM Ken Sharman via Dxspider-support <
dxspider-support at tobit.co.uk> wrote:
> Hi Keuth
> Your testing spot came through to GB7HTL
>
> Ken G7VJA
> GB7HTL
>
> On 22 Mar 2025 17:45, "Keith, G6NHU via Dxspider-support" <
> dxspider-support at tobit.co.uk> wrote:
>
> I don’t delete stuff very often and I just found the installation of
> ar-cluster from when I used it, nearly ten years ago. It included an
> install file and my saved directory from program files from when I last ran
> it.
>
> So I fired up a Windows box, installed it, copied my install directory
> over and ran it.
>
> Straight away, it created two connections into other nodes and started
> showing spots. I removed the connections and enabled an ‘ARC6’ connection
> that I had setup previously, all that time ago.
>
> I logged onto this node I’d restored and tried to submit a spot. Lo and
> behold, it was accepted and it appeared on my dxspider a couple of seconds
> later. Bear in mind that I’ve not run this cluster for nearly ten years
> and originally I didn’t ask anyone to partner with me, I just set it up.
>
> 7074.0 G6NHU 22-Mar-2025 1734Z testing <G6NHU>
>
> Also:
>
> sh/dx origin g6nhu
> 7074.0 G6NHU 22-Mar-2025 1734Z testing <G6NHU>
>
> I only have very basic logging enabled so I can’t check my debug log to
> see this spot but perhaps someone else can have a look and see how it was
> formed.
>
> AR cluster crashes every few minutes and I’ve now shut the PC down anyway
> but surely this demonstrates why we should be doing what Rene says below
> (and what I’ve said previously). We need to start disconnecting nodes
> that are wide open like this.
>
> 73 Keith.
> On 22 Mar 2025 at 15:40 +0000, Rene Olsen via Dxspider-support <
> dxspider-support at tobit.co.uk>, wrote:
>
> Hi.
>
> I know that we want to try and be backwards compatible, and every node
> should be able to be
> part of the network.
>
> But at some point we will simply have to to make some minimum requirements
> for nodes to be
> part of the network.
>
> Node software like you mention, where anyone can just connect as a node
> partner, and start
> to send data, should simply be banned from the network.
>
> Nodes where any user can just login and start sending spots, should also
> not be part of the
> network. I am aware that some softwares may have rate settings on users,
> so thet can't just
> spot like crazy.
>
> I have no personal preference towards any node software, but in my opinion
> we can't keep
> accepting the lowest possible security level, just to be backwards
> compatible with 10+ year
> old software, that may even no longer be maintained.
>
> We can try to do all kinds of tricks, and I am sure Dirk is doing his best
> to combat this. But
> there has to be other solutions, than spending time trying to battle
> things, that only exsists
> because of old software and poorly maintained nodes.
>
> Just my thougts...
>
> Vy 73 de Rene / OZ1LQH
>
>
> On 22 Mar 2025 at 13:59, Keith, G6NHU via Dxspider-sup wrote:
>
> Rene,
>
> This is complete and utter speculation and I may be well off the mark.
>
> When I set up my first dxcluster, I used some windows software that´s now
> been out of development for years. I never asked anyone if I could node
> partner with them (because I didn´t know one was supposed to), I just set
> up some links to other nodes using the same software and it worked.
>
> According to dxcluster.info, there are still over 120 of these older
> clusters still out there - Could these spots be coming in via one of them?
>
> 73 Keith.
>
> On 22 Mar 2025 at 13:43 +0000, Rene Olsen via Dxspider-support <
> dxspider-support at tobit.co.uk>, wrote:
>
> Hi.
>
> Someone must know who is doing this and be covering for them.
>
> Maybe I am wrong, but to make those false spots, they must be running a
> cluster and have a
> link to a node somewhere in the network.
>
> Somehow they must have an entry point into the network, where they can
> then spread their
> falsified PC61 frames.
>
> Vy 73 de Rene / OZ1LQH
>
>
> On 22 Mar 2025 at 13:31, Keith, G6NHU via Dxspider-sup 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>, 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
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250322/147252b0/attachment.htm>
More information about the Dxspider-support
mailing list