[Dxspider-support] Bad IP

[Kin]

Hi Gregor,

I read you and I have the impression that you think that putting the real IP
is a caprice. I guess it's because of my bad English :(
Dirk has tried to endow the archaic AK1A protocol with some functionalities
that help sysops, and therefore everyone, to detect problems, to maintain
the network. This has allowed us to know that a certain node/user is or is
not the cause of a problem, and therefore allows us to act to solve it. When
data is missing, problems sometimes arise and hasty decisions are made.

When one reads the discussions here over time (I recommend it), one can be
amazed at what some humans are capable of doing out of boredom. 

There are web frontends like https://webcluster.ure.es/ ,
https://www.dxheat.com/dxc/ or https://www.dxfuncluster.com/ who are using
dxspider and had no problems attaching the user IP to the spots. I don't
remember any of them objecting to problems when I explained the reason for
adding the real address.
Even one of them I know works with HA and it works great.

Regards,

Kin EA3CV


-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de
Gregor Surmann via Dxspider-support
Enviado el: miércoles, 5 de febrero de 2025 19:41
Para: Dirk Koopman via Dxspider-support <dxspider-support at tobit.co.uk>
CC: Gregor Surmann <gs at funil.de>
Asunto: Re: [Dxspider-support] Bad IP

Dirk, with all due respect, I don't think I would need any "recalibration",
as I am successfully working in networking for 30 years now. However, I have
a fully equipped HF laboratory up to many GHz, so I could surely do it if
needed ;)

I have a valid reason here to use the xinetd, besided the listen socket, as
this node (after the old DB0SUE-7 failed) is used for registered and checked
users of a free website to allow them to spot, as I used to do on DB0SUE-7
for the last 12 years or so.

I will act immediately, if any bad spots will occure, and I don't think,
that this may be a problem. Many sites do that, like dxheat.com for example.

I mean, I could change the setup to be unnecessarily complicated, only to
show the "real" IP of the users (from webserver), for the solely purpose of
beeing there in the cluster messages, but this would be additional work,
which I would like to avoid.

There were no bad spots in the last 12 years, so please, please, with sugar
on top, have a little confidence that I know what I'm doing ;)

Over the last 30 years I have contributed quite a lot to the Internet for
free and at my own expense. This node is also a part of it. I respect
protocols, RFCs, etc. but sometimes one need to "bend" it slightly to
achieve a goal more easily.

best regards

73 de Gregor, DO5SSB



On 05.02.25 17:51, Dirk Koopman via Dxspider-support wrote:
> (x)inet(d) a secure system??
> 
> xinet (and all similar systems various) has been deprecated as a 
> (potential) security nightmare for at least the last 30 years (yes I 
> am that old, and more).
> 
> The only reason continued to include the client program is for dealing 
> with things like raw ax25 connections.
> 
> Please recalibrate this sysop.
> 
> 73 Dirk


_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support