<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I answer myself;</p>
<p>sh/log sm7gvf-1 shows the external IP number in a PC92A message.</p>
<p>The trouble is to be aware if it changes, when a new DHCP address
is given.</p>
<p>73</p>
<p>Kjell</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2023-01-22 16:52, Kjell Jarl via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:626acada-30f9-fa69-091d-0e622d2da1f4@bahnhof.se">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Thanks Dirk,</p>
<p>If I understand correctly, my external address will be used as
the spotter address when on local ip numbers.</p>
<p>Both interfaces are DHCP but changes rareley, is there a way to
tell if it has been broken or I got it right in the first place?</p>
<p>73</p>
<p>Kjell</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2023-01-22 15:15, Dirk Koopman via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:02ed5cbb-4575-5db3-d66b-ab361d04b37e@tobit.co.uk">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">On 22/01/2023 11:37, Kjell Jarl via
Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b524473c-713c-0b7a-6f82-94dddac09420@bahnhof.se">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p>Hi</p>
<p>How are spots issued from my local network (192...) on the
local interface treated? Will it be dropped now or in the
future?<br>
</p>
</blockquote>
<br>
Ah, you'll be one of my customers for the snippets below<br>
<br>
TLDR:<br>
<br>
Stick these lines in your startup script file<br>
<font face="monospace">set/var <font size="4">$main::localhost_alias_ipv4
'<external IPV4 address of node>'<br>
</font>set/var </font><font size="4"><font face="monospace">$main::localhost_alias_ipv6
'<external IPV6 address of node>' </font></font><font
size="4">#</font><font size="4"><font face="monospace"> if any<br>
</font></font><font size="4"><font face="monospace">set/var
@main::localhost_names ('127.0.0.1', '::1',
'192.168.1.30') </font></font><font size="4"># or
whatever your internal net address(es) are</font><font
size="4"><font face="monospace"><br>
</font></font><font size="4"><br>
Kin EA3CV, for instance, has many more internal network
addresses, over and above the localhost addresses</font><font
size="4">. There is no theoretical limit. </font><font
size="4"><font face="monospace"><br>
<br>
</font></font><font size="4">73 de Dirk G1TLH<br>
</font>
<blockquote type="cite"
cite="mid:b524473c-713c-0b7a-6f82-94dddac09420@bahnhof.se">
<p> </p>
<p>73</p>
<p>Kjell, SM7GVF<br>
</p>
<div class="moz-cite-prefix">On 2023-01-20 15:41, Dirk Koopman
via Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:69a1fcea-8516-8dbe-1bd7-703dded01086@tobit.co.uk">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<font size="4"><br>
<br>
<font face="monospace">20Jan23=======================================================================<br>
1. Add the variable @main::localhost_names to allow
other IP addresses to<br>
be treated in the same way as localhost in item 1 on
19Jan23 below. NOTE<br>
you must include ALL the normal localhost names + any
other interface<br>
names that you might want to include:<br>
<br>
set/var @main::localhost_names qw(127.0.0.1 ::1
192.168.1.30)<br>
<br>
using the qw() construction is easier than:<br>
<br>
set/var @main::localhost_names ('127.0.0.1',
'::1', '192.168.1.30')<br>
<br>
but either will work. You can define as many IP
addresses as you like and<br>
they can be IPV4 or 6. <br>
<br>
You do NOT need to fiddle with this unless you
specifically have more<br>
than just the normal definitions of localhost. So for
'normal' nodes with<br>
one external interface, you DO NOT NEED TO DO ANY OF
THIS. <br>
2. Added CTY-3304 prefix data<br>
19Jan23=======================================================================<br>
1. Introduce aliasing for localhost in DX Spots and
outgoing PC92 A records<br>
on login. There are two variables which can be set
with the alias to use:<br>
$main::localhost_alias_ipv4<br>
$main::localhost_alias_ipv6 <br>
These can be set in the /spider/scripts/startup, but
this is only <br>
necessary if the node has more than one interface, or
virtual hosts. If <br>
there is ONLY ONE ipv4 and/or ipv6 IP address on the
node machine then <br>
these variables will be automatically populated on
first use. But the SAFE<br>
thing to do is to set them in the startup file. <br>
<br>
THIS FEATURE IS EXPERIMENTAL... </font></font><br>
</blockquote>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:Dxspider-support@tobit.co.uk" moz-do-not-send="true">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
</body>
</html>