[Dxspider-support] Bad IP
Dirk Koopman
djk at tobit.co.uk
Wed Feb 5 14:19:52 GMT 2025
Nope.
The node knows the incoming IP address of all connections. But if the
gateway is using reverse NAT then this sort of thing could occur.
These variables in main:: may help or be the cause of the issue.
our @localhost_names = qw(127.0.0.1 ::1); # all ip addresses that will
need to be aliased below (ipv4 or ipv6)
our $localhost_alias_ipv4; # these are the IPV4 & 6 aliases for
localhost connected clients
our $localhost_alias_ipv6; # for things (PC92, PC61 etc) that
expose IP addresses. These *may*
# be set by Msg.pm stuff if they are
left undefined but, if you need
# certainty then set/var them in the
startup file.
There is code which could use the way HA communicates that might help.
Kin knows more about this than I do.
Dirk
On 05/02/2025 13:23, Mike McCarthy, W1NR via Dxspider-support wrote:
> If client is listening on 82.149.227.228 then every connection will
> get that IP and every spot will show that IP as the connection IP.
>
> On 2/5/2025 8:18 AM, ea3cv at cronux.net wrote:
>> No, we are not talking about the user's IP, we are talking about the
>> node's IP.
>> If you look at the traces it is crystal clear.
>>
>> Kin
>>
>>
>
>
More information about the Dxspider-support
mailing list