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

[g4piq]

Thanks Kin. But - my point was that I didn't understand what I'd done wrong.If I've understood tge request correctly, I don't believe that's it's practical for many users to insert their public IP addresses in the startup config. Like many (most?) sysops, my node runs on a network with dynamic public IP address allocation and NAT to an RFC1918 range, changing each time the router reboots. I won't put the host in a DMZ because of the extra security exploits that enables. So, it's not practical to put a static IP entry in the startup config. It would be better for the code to dynamically establish the public IP itself and use that.73Andy, G4PIQ Sent from my Galaxy
-------- Original message --------From: Kin <ea3cv at cronux.net> Date: 22/03/2025  21:28  (GMT+00:00) To: g4piq at btinternet.com, 'The DXSpider Support list' <dxspider-support at tobit.co.uk> Subject: RE: [Dxspider-support] List of users/nodes with incorrect IP addresses Hi Andy,I have no intention of blacklisting anyone for not having the correctconfiguration. It was simply a way to get the attention of sysops to try toget them to configure their node correctly.I assume/hope that with the next code changes, Dirk will fix this problem.By the way, my email is related to a previous one Dirk posted, which readsas follows:One of the things that is going to important for the next release is forsysops running (test?) instances behind masquerading firewalls (eg mydevelopment node GB7TLH)  is to have these three statements (suitablymodified) 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 (amongstothers) when the node is not physically connected directly to the internet. With this release PC92 K records will have an ip address and a versionstring tacked on the end: PC92^GB7TLH^58020.01^K^5GB7TLH:5457:593^4^1^82.68.205.1^test/f9b61990[r]^H99^Dirk G1TLH73 de Kin EA3CV_____________________________________________De: g4piq at btinternet.com <g4piq at btinternet.com> Enviado el: sábado, 22 de marzo de 2025 22:14Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>CC: 'Kin' <ea3cv at cronux.net>Asunto: RE: [Dxspider-support] List of users/nodes with incorrect IPaddressesSorry Kin - I haven't clue why G4PIQ/GB7DXM shows up on your list. I'm justthe sysop user on my local GB7DXM node on the local LAN. 192.168.1.254. I'vedone no special coding and am running 1.57 build 564. Please be clear onwhat I've done wrong to get on the naughty step. You've no reason to startdropping my spots.73Andy, G4PIQ_____________________________________________From: Dxspider-support <dxspider-support-bounces at tobit.co.uk<mailto:dxspider-support-bounces at tobit.co.uk> > On Behalf Of Kin viaDxspider-supportSent: 22 March 2025 21:02To: 'The DXSpider Support list' <dxspider-support at tobit.co.uk<mailto:dxspider-support at tobit.co.uk> >Cc: Kin <ea3cv at cronux.net <mailto:ea3cv at cronux.net> >Subject: [Dxspider-support] List of users/nodes with incorrect IP addressesHi,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::/8IPv6: RFC 4291	fe80::/10	ff00::/8	::/128	::1/128Please note that all users of these addresses will soon have theirspots/anns removed.This list is only of what has been seen today.User		IP Address		Node-------	-------------	-------	CX1MS		10.0.0.4		M0KGX-3CX4RL		10.0.0.4		M0KGX-3EA5HNF	10.0.0.4		M0KGX-3EA5RKB	10.0.0.4		M0KGX-3EA7JPT	10.0.0.4		M0KGX-3EA7KWC	10.0.0.4		M0KGX-3EC7ZT		10.0.0.4		M0KGX-3G0VAX		192.168.1.254	GB7VAXG1DIF		192.168.1.116	G7VJA-2G4PIQ		192.168.1.254	GB7DXMG6NHU		192.168.1.8	G6NHU-2G7RAU		192.168.0.2	GB7RAUG7VJA		192.168.1.64	GB7HTLG7VJA		192.168.1.140	GB7HTLIT7GGK	10.0.0.4		M0KGX-3IT9BGB	10.0.0.4		M0KGX-3IZ0EHV	10.0.0.4		M0KGX-3IZ0IJC	10.0.0.4		M0KGX-3IZ0ORT	192.168.1.84	IZ0ORT-6IZ2LUS	10.0.0.4		M0KGX-3IZ5FSA	192.168.1.6	IZ5FSA-6K2LS-22	192.168.1.254	K2LSKD3ABP	10.0.0.4		M0KGX-3LZ2EN		10.0.0.4		M0KGX-3M7CVK		10.0.0.4		M0KGX-3N1PPP		10.0.2.2		EA6VQ-1PD1WC		10.0.0.4		M0KGX-3Q1QQQ		192.168.4.197	IZ2LSC-55RN8C		10.0.0.4		M0KGX-3RN8C		10.0.0.4		K1TTTUA4CC-5	192.168.11.253	UA4CCUA4NDX	10.0.0.4		M0KGX-3UA4YE		10.0.0.4		M0KGX-3VE3EY-3	192.168.10.30	VE3EY-7WP4JD		10.0.0.4		M0KGX-3YE4IJ		10.0.0.4		M0KGX-3Nodes 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 >> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250322/c02d76d0/attachment-0001.htm>