<html><body><div dir="auto">MartÃn,</div><div dir="auto"><br></div><div dir="auto" style="color: rgb(0, 0, 0);">I'm out of the house now, so check out these links to see if they help.<br>If you don't understand, let's talk.</div><div dir="auto" style="color: rgb(0, 0, 0);"><br></div><div dir="auto" style="color: rgb(0, 0, 0);"><a href="https://wiki.dxcluster.org/wiki/Updating_Public_IP_and/or_Local_IPs_(set/update_ip" rel="noreferrer noopener">https://wiki.dxcluster.org/wiki/Updating_Public_IP_and/or_Local_IPs_(set/update_ip</a></div><div id="ms-outlook-mobile-body-separator-line" dir="auto"><br><div dir="auto" style="color: rgb(0, 0, 0);"><a href="https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository" rel="noreferrer noopener">https://wiki.dxcluster.org/wiki/Setting_up_the_EA3CV_contributions_repository</a></div><div dir="auto"><br></div><div dir="auto">Kin EA3CV</div><div dir="auto"><br></div><div dir="auto"><br></div></div><div id="ms-outlook-mobile-signature" dir="auto">Enviado desde <a href="https://aka.ms/AAb9ysg">Outlook para Android</a></div><div dir="auto" id="mail-editor-reference-message-container"><br><hr style="display: inline-block; width: 98%;"><div id="divRplyFwdMsg" style="font-size: 11pt;" dir="auto"><b>De:</b> Martin Davies G0HDB <marting0hdb@gmail.com><br><b>Enviado:</b> jueves, abril 10, 2025 4:44:30 p. m.<br><b>Para:</b> The DXSpider Support list <dxspider-support@tobit.co.uk><br><b>CC:</b> Kin <ea3cv@cronux.net><br><b>Asunto:</b> Re: [Dxspider-support] BadIPs on PC92<br></div><br>On 9 Apr 2025 at 20:09, Kin via Dxspider-support wrote:<br><br>> Hi all,<br>><br>> List of nodes that do not send their public IP address (today).<br>><br>> This could be due to a misconfiguration or a bug in the build.<br>> If you have it configured correctly, indicate it in the List, it may be a<br>> defect.<br>><br>> Nodes that identify themselves as 172.0.0.1<br>><br>> GB7DXC-5 614<br>.<br>.<br>.<br><br>> Nodes that send all or some users with 127.0.0.1 10.* 192.*<br>> 172.16.*/172.31.*<br>.<br>.<br>.<br>> GB7DXC-5<br>.<br>.<br>.<br>> Let's build a better network.<br><br>Hello Kin (and group), I am now getting thoroughly confused by the recent flood of messages<br>about bad IPs in PC92s and other related topics...!<br><br>A couple of weeks ago I followed previous guidance and included the following in the startup<br>file for the GB7DXC-5 node:<br><br>set/var $main::localhost_alias_ipv4 = '90.155.35.170'<br>set/var @main::localhost_names qw( 127.0.0.1 ::1 192.168.1.90)<br><br>The address 90.155.35.170 is my public one, and 192.168.1.90 is the address of the<br>Raspberry Pi-based GB7DXC-5 node on my LAN. Both addresses are static.<br><br>I also downloaded version 1.2 dated 20250322 of Kin's update_ip.pl and put it into<br>/spider/local_cmd, as per the instructions at that time.<br><br>I subsequently added the following to my crontab, to run update_ip.pl once a day at 0445,<br>even though neither the WAN nor the LAN IP address should ever change:<br><br>45 04 * * * run_cmd("update_ip")<br><br>I now find that the GB7DXC-5 node is apparently misconfigured and is identifying itself as<br>having address 127.0.0.1 and is also forwarding user information with LAN IP addresses<br>(127.0.0.1 etc).<br><br>My question is what do I now need to do on the GB7DXC-5 node to correct whatever<br>misconfigurations exist; I would be grateful for a step-by-step explanation in as simple<br>language as possible, please - I am not a Linux expert...!<br><br>To confuse me even more I've recently noted that there is a reference to putting Kin's latest<br>version of update_ip.pl into the local_cmd/set directory, which doesn't exist on my system.<br>I've also seen references to local_cmd/show, which also doesn't exist on my system. Can<br>someone please explain how to create these directories (mkdir?) and also provide a list of<br>what they should contain, in addition to the latest update_ip.pl file.<br><br>Thank you in advance,<br><br>73,<br>--<br>Martin Davies G0HDB, GB7DXC-5 sysop<br>marting0hdb@gmail.com<br><br><br>--<br>This email has been checked for viruses by Avast antivirus software.<br>www.avast.com<br><br></div></body></html>