[Dxspider-support] List of users/nodes with incorrect IP addresses

Sat Mar 22 22:10:58 GMT 2025

Thank you Keith and Kin - that should work. I clearly can't keep up with every posting here.73Andy, G4PIQ Sent from my Galaxy
-------- Original message --------From: "Keith, G6NHU via Dxspider-support" <dxspider-support at tobit.co.uk> Date: 22/03/2025  22:04  (GMT+00:00) To: The DXSpider Support list <dxspider-support at tobit.co.uk> Cc: "Keith, G6NHU" <g6nhu at me.com>, g4piq <g4piq at btinternet.com> Subject: Re: [Dxspider-support] List of users/nodes with incorrect IP addresses 

Andy, I stand to be corrected but I think Kin wrote a script which does this called update_ip.pl.  You just call it from crontab every five minutes or so and it updates the variables to the external IP address.All the info is here: https://github.com/EA3CV/dxspider_info73 Keith.

On 22 Mar 2025 at 21:54 +0000, g4piq via Dxspider-support <dxspider-support at tobit.co.uk>, wrote:

Genuinely without trying to be negative - the challenge with a script updating the startup script IP for a dynamic IP address is when the public IP address changes but the node doesn't restart. This will be quite frequent. Some routers reboot after a fixed period (2 weeks not uncommon) and users with DSL connections in particular may reboot after noise (e.g. RFI) on the line. My router is certainly rebooted more frequently than the cluster host.

73

Andy, G4PIQ 

Sent from my Galaxy

-------- Original message --------
From: Rene Olsen via Dxspider-support <dxspider-support at tobit.co.uk>
Date: 22/03/2025 21:32 (GMT+00:00)
To: dxspider-support at tobit.co.uk
Cc: Rene Olsen <rene at rcolsen.dk>, g4piq at btinternet.com
Subject: Re: [Dxspider-support] List of users/nodes with incorrect IP addresses

Hi andy.

Dirk wrote this in a previous post.

-----

One of the things that is going to important for the next release is for
sysops running (test?) instances behind masquerading firewalls (eg my
development node GB7TLH)  is to have these three statements (suitably
modified) in your startup script:

set/var $main::localhost_alias_ipv4 '82.68.205.1'
set/var $main::localhost_alias_ipv6 '2a02:8010:9019::6'
set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.19.20)

These are the ip addresses that will be used on PC92 sentences (amongst
others) when the node is not physically connected directly to the
internet.

-----

So, guess that is what you (and other behind NAT) should do.

Not really sure what one is supposed to put there, if one has a dynamic IP. Guess one will
have to run a script that updates the startup script or whatever.

Vy 73 de Rene / OZ1LQH

On 22 Mar 2025 at 21:13, g4piq--- via Dxspider-support wrote:

> Sorry Kin - I haven't clue why G4PIQ/GB7DXM shows up on your list. I'm just
> the sysop user on my local GB7DXM node on the local LAN. 192.168.1.254. I've
> done no special coding and am running 1.57 build 564. Please be clear on
> what I've done wrong to get on the naughty step. You've no reason to start
> dropping my spots.
>
> 73
>
> Andy, G4PIQ
>
>
>
> _____________________________________________
> From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> On Behalf Of
> Kin via Dxspider-support
> Sent: 22 March 2025 21:02
> To: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
> Cc: Kin <ea3cv at cronux.net>
> Subject: [Dxspider-support] List of users/nodes with incorrect IP addresses
>
>
> Hi,
>
> List of users/nodes that are being identified by an intranet IP address:
>
> IPv4: RFC 1918
> 10.0.0.0/8 (10.0.0.0 - 10.255.255.255)
> 172.16.0.0/12 (172.16.0.0 - 172.31.255.255)
> 192.168.0.0/16 (192.168.0.0 - 192.168.255.255)
>
> IPv4: RFC 3927
> 169.254.0.0/16 (169.254.0.0 - 169.254.255.255)
>
> IPv6: RFC 4193
> fc00::/8
> fd00::/8
>
> IPv6: RFC 4291
> fe80::/10
> ff00::/8
> ::/128
> ::1/128
>
> Please note that all users of these addresses will soon have their
> spots/anns removed.
> This list is only of what has been seen today.
>
> User IP Address Node
> ------- ------------- -------
> CX1MS 10.0.0.4 M0KGX-3
> CX4RL 10.0.0.4 M0KGX-3
> EA5HNF 10.0.0.4 M0KGX-3
> EA5RKB 10.0.0.4 M0KGX-3
> EA7JPT 10.0.0.4 M0KGX-3
> EA7KWC 10.0.0.4 M0KGX-3
> EC7ZT 10.0.0.4 M0KGX-3
> G0VAX 192.168.1.254 GB7VAX
> G1DIF 192.168.1.116 G7VJA-2
> G4PIQ 192.168.1.254 GB7DXM
> G6NHU 192.168.1.8 G6NHU-2
> G7RAU 192.168.0.2 GB7RAU
> G7VJA 192.168.1.64 GB7HTL
> G7VJA 192.168.1.140 GB7HTL
> IT7GGK 10.0.0.4 M0KGX-3
> IT9BGB 10.0.0.4 M0KGX-3
> IZ0EHV 10.0.0.4 M0KGX-3
> IZ0IJC 10.0.0.4 M0KGX-3
> IZ0ORT 192.168.1.84 IZ0ORT-6
> IZ2LUS 10.0.0.4 M0KGX-3
> IZ5FSA 192.168.1.6 IZ5FSA-6
> K2LS-22 192.168.1.254 K2LS
> KD3ABP 10.0.0.4 M0KGX-3
> LZ2EN 10.0.0.4 M0KGX-3
> M7CVK 10.0.0.4 M0KGX-3
> N1PPP 10.0.2.2 EA6VQ-1
> PD1WC 10.0.0.4 M0KGX-3
> Q1QQQ 192.168.4.197 IZ2LSC-55
> RN8C 10.0.0.4 M0KGX-3
> RN8C 10.0.0.4 K1TTT
> UA4CC-5 192.168.11.253 UA4CC
> UA4NDX 10.0.0.4 M0KGX-3
> UA4YE 10.0.0.4 M0KGX-3
> VE3EY-3 192.168.10.30 VE3EY-7
> WP4JD 10.0.0.4 M0KGX-3
> YE4IJ 10.0.0.4 M0KGX-3
>
> Nodes that do not propagate the user's real IP will end up on blacklists.
> It's a matter of time.
>
> Kin EA3CV
>  << File: Untitled attachment 00006.txt >>
>

_______________________________________________
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/c83811b4/attachment-0001.htm>