[Dxspider-support] DXSpider mojo branch build 482

[Kin]

To find out if DHCP has changed any LAN IP, you would have to have an external process (perhaps in cron) that would check, for example:

hostname -I

and on a change, cast a set/var @main::localhost_names ('127.0.0.1', '::1', 'x.x.x.x', 'z.z.z.z')

 

Kin

 

 

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Kjell Jarl via Dxspider-support
Enviado el: domingo, 22 de enero de 2023 16:53
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Kjell Jarl <kjell.jarl at bahnhof.se>
Asunto: Re: [Dxspider-support] DXSpider mojo branch build 482

 

Thanks Dirk,

If I understand correctly, my external address will be used as the spotter address when on local ip numbers.

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?

73

Kjell

 

On 2023-01-22 15:15, Dirk Koopman via Dxspider-support wrote:

On 22/01/2023 11:37, Kjell Jarl via Dxspider-support wrote:

Hi

How are spots issued from my local network (192...) on the local interface treated? Will it  be dropped now or in the future?


Ah, you'll be one of my customers for the snippets below

TLDR:

Stick these lines in your startup script file
set/var $main::localhost_alias_ipv4 '<external IPV4 address of node>'
set/var $main::localhost_alias_ipv6 '<external IPV6 address of node>'  # if any
set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.30')   # or whatever your internal net address(es) are

Kin EA3CV, for instance, has many more internal network addresses, over and above the localhost addresses. There is no theoretical limit. 
  
73 de Dirk G1TLH



73

Kjell, SM7GVF

On 2023-01-20 15:41, Dirk Koopman via Dxspider-support wrote:



20Jan23=======================================================================
1. Add the variable @main::localhost_names to allow other IP addresses to
   be treated in the same way as localhost in item 1 on 19Jan23 below. NOTE
   you must include ALL the normal localhost names + any other interface
   names that you might want to include:

      set/var @main::localhost_names qw(127.0.0.1 ::1 192.168.1.30)

   using the qw() construction is easier than:

      set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.30')

   but either will work. You can define as many IP addresses as you like and
   they can be IPV4 or 6. 
   
   You do NOT need to fiddle with this unless you specifically have more
   than just the normal definitions of localhost. So for 'normal' nodes with
   one external interface, you DO NOT NEED TO DO ANY OF THIS. 
2. Added CTY-3304 prefix data
19Jan23=======================================================================
1. Introduce aliasing for localhost in DX Spots and outgoing PC92 A records
   on login. There are two variables which can be set with the alias to use:
      $main::localhost_alias_ipv4
      $main::localhost_alias_ipv6 
   These can be set in the /spider/scripts/startup, but this is only 
   necessary if the node has more than one interface, or virtual hosts. If 
   there is ONLY ONE ipv4 and/or ipv6 IP address on the node machine then 
   these variables will be automatically populated on first use. But the SAFE
   thing to do is to set them in the startup file.  

   THIS FEATURE IS EXPERIMENTAL... 






_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto: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/20230122/9b2b1800/attachment-0001.htm>