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

[Keith, G6NHU]

Oh wait…. That’s a user/node combo?

Yes, G6NHU is logged on to the console at G6NHU-2 which is on 192.168.1.8.   I’m always connected via SSH to the node console and I submit spots by hand, there’s no way around this as far as I know.

73 Keith.

On 22 Mar 2025 at 21:28 +0000, Keith, G6NHU <g6nhu at me.com>, wrote:
> You can cross G6NHU (no SSID) off the list, that was me firing up the old AR-Cluster node for about 20 minutes earlier today for some testing.  It will never return.  192.168.1.8 is the internal address of G6NHU-2 which has been behind a static IP for donkeys years.
>
> G6NHU 192.168.1.8 G6NHU-2
> On 22 Mar 2025 at 21:01 +0000, Kin via Dxspider-support <dxspider-support at tobit.co.uk>, wrote:
> > 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
> >
> >
> > _______________________________________________
> > 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/5a4a076a/attachment.htm>