<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Thanks Kin. But - my point was that I didn't understand what I'd done wrong.</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">73</div><div dir="auto"><br></div><div dir="auto">Andy, G4PIQ </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:12px;color:#575757" dir="auto">Sent from my Galaxy</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Kin <ea3cv@cronux.net> </div><div>Date: 22/03/2025 21:28 (GMT+00:00) </div><div>To: g4piq@btinternet.com, 'The DXSpider Support list' <dxspider-support@tobit.co.uk> </div><div>Subject: RE: [Dxspider-support] List of users/nodes with incorrect IP addresses </div><div><br></div></div>Hi Andy,<br><br>I have no intention of blacklisting anyone for not having the correct<br>configuration. It was simply a way to get the attention of sysops to try to<br>get them to configure their node correctly.<br>I assume/hope that with the next code changes, Dirk will fix this problem.<br><br>By the way, my email is related to a previous one Dirk posted, which reads<br>as follows:<br><br>One of the things that is going to important for the next release is for<br>sysops running (test?) instances behind masquerading firewalls (eg my<br>development node GB7TLH) is to have these three statements (suitably<br>modified) in your startup script:<br><br>set/var $main::localhost_alias_ipv4 '82.68.205.1'<br>set/var $main::localhost_alias_ipv6 '2a02:8010:9019::6'<br>set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.19.20)<br><br>These are the ip addresses that will be used on PC92 sentences (amongst<br>others) when the node is not physically connected directly to the internet. <br><br>With this release PC92 K records will have an ip address and a version<br>string tacked on the end:<br><br> <br>PC92^GB7TLH^58020.01^K^5GB7TLH:5457:593^4^1^82.68.205.1^test/f9b61990[r]^H99<br>^<br><br>Dirk G1TLH<br><br>73 de Kin EA3CV<br><br>_____________________________________________<br>De: g4piq@btinternet.com <g4piq@btinternet.com> <br>Enviado el: sábado, 22 de marzo de 2025 22:14<br>Para: 'The DXSpider Support list' <dxspider-support@tobit.co.uk><br>CC: 'Kin' <ea3cv@cronux.net><br>Asunto: RE: [Dxspider-support] List of users/nodes with incorrect IP<br>addresses<br><br><br>Sorry Kin - I haven't clue why G4PIQ/GB7DXM shows up on your list. I'm just<br>the sysop user on my local GB7DXM node on the local LAN. 192.168.1.254. I've<br>done no special coding and am running 1.57 build 564. Please be clear on<br>what I've done wrong to get on the naughty step. You've no reason to start<br>dropping my spots.<br><br>73<br><br>Andy, G4PIQ<br><br><br><br>_____________________________________________<br>From: Dxspider-support <dxspider-support-bounces@tobit.co.uk<br><mailto:dxspider-support-bounces@tobit.co.uk> > On Behalf Of Kin via<br>Dxspider-support<br>Sent: 22 March 2025 21:02<br>To: 'The DXSpider Support list' <dxspider-support@tobit.co.uk<br><mailto:dxspider-support@tobit.co.uk> ><br>Cc: Kin <ea3cv@cronux.net <mailto:ea3cv@cronux.net> ><br>Subject: [Dxspider-support] List of users/nodes with incorrect IP addresses<br><br><br>Hi,<br><br>List of users/nodes that are being identified by an intranet IP address:<br><br>IPv4: RFC 1918<br> 10.0.0.0/8 (10.0.0.0 - 10.255.255.255)<br> 172.16.0.0/12 (172.16.0.0 - 172.31.255.255)<br> 192.168.0.0/16 (192.168.0.0 - 192.168.255.255)<br><br>IPv4: RFC 3927<br> 169.254.0.0/16 (169.254.0.0 - 169.254.255.255)<br><br>IPv6: RFC 4193<br> fc00::/8<br> fd00::/8<br><br>IPv6: RFC 4291<br> fe80::/10<br> ff00::/8<br> ::/128<br> ::1/128<br><br>Please note that all users of these addresses will soon have their<br>spots/anns removed.<br>This list is only of what has been seen today.<br><br>User IP Address Node<br>------- ------------- ------- <br>CX1MS 10.0.0.4 M0KGX-3<br>CX4RL 10.0.0.4 M0KGX-3<br>EA5HNF 10.0.0.4 M0KGX-3<br>EA5RKB 10.0.0.4 M0KGX-3<br>EA7JPT 10.0.0.4 M0KGX-3<br>EA7KWC 10.0.0.4 M0KGX-3<br>EC7ZT 10.0.0.4 M0KGX-3<br>G0VAX 192.168.1.254 GB7VAX<br>G1DIF 192.168.1.116 G7VJA-2<br>G4PIQ 192.168.1.254 GB7DXM<br>G6NHU 192.168.1.8 G6NHU-2<br>G7RAU 192.168.0.2 GB7RAU<br>G7VJA 192.168.1.64 GB7HTL<br>G7VJA 192.168.1.140 GB7HTL<br>IT7GGK 10.0.0.4 M0KGX-3<br>IT9BGB 10.0.0.4 M0KGX-3<br>IZ0EHV 10.0.0.4 M0KGX-3<br>IZ0IJC 10.0.0.4 M0KGX-3<br>IZ0ORT 192.168.1.84 IZ0ORT-6<br>IZ2LUS 10.0.0.4 M0KGX-3<br>IZ5FSA 192.168.1.6 IZ5FSA-6<br>K2LS-22 192.168.1.254 K2LS<br>KD3ABP 10.0.0.4 M0KGX-3<br>LZ2EN 10.0.0.4 M0KGX-3<br>M7CVK 10.0.0.4 M0KGX-3<br>N1PPP 10.0.2.2 EA6VQ-1<br>PD1WC 10.0.0.4 M0KGX-3<br>Q1QQQ 192.168.4.197 IZ2LSC-55<br>RN8C 10.0.0.4 M0KGX-3<br>RN8C 10.0.0.4 K1TTT<br>UA4CC-5 192.168.11.253 UA4CC<br>UA4NDX 10.0.0.4 M0KGX-3<br>UA4YE 10.0.0.4 M0KGX-3<br>VE3EY-3 192.168.10.30 VE3EY-7<br>WP4JD 10.0.0.4 M0KGX-3<br>YE4IJ 10.0.0.4 M0KGX-3<br><br>Nodes that do not propagate the user's real IP will end up on blacklists.<br>It's a matter of time.<br><br>Kin EA3CV<br> << File: Untitled attachment 00006.txt >> <br></body></html>