[Dxspider-support] Bad IP

[Mike McCarthy, W1NR]

Kin, you are missing the point here. He is not using the direct listener 
in cluster.pl. He is using xinetd and spawning a /spider/src/client on 
each connection. Depending on how it is set up, the connecting user will 
get localhost (127.0.0.1) or the node IP. The users own ip will be hidden.

xinetd is old school and not used much anymore, but in some ways it can 
be configured for better security for connections.

On 2/5/2025 8:33 AM, ea3cv at cronux.net wrote:
> It is not where the client is listening, it is the IP that the node 
> obtains when the session is established, which will be associated with 
> the spots generated by the user, that IP will be his, not the node's.
> But there are nodes that either do not send it (PC11) or put the node's 
> IP, localhost, ... in that field.
> Lately we have had an avalanche of spots with callsigns attached to IPs 
> that were not theirs in the spots.
> In the routing messages referring to the nodes, it must coincide with 
> the node's IP.
> 
> Kin
> 
-- 
73 de Mike, W1NR

THAT was the equation. EXISTENCE!... SURVIVAL... must cancel out... 
programming!

- Ruk -