[arm-allstar] Confusion

[Doug Crompton]

Roger,

 You are running into the same problem that others have only yours is more
visible. astnode gets its information from the Allstar server which as has
been pointed out gives bogus information on a regular basis. The only total
answer at this point is to use both Hamvoip registration and DNS lookup for
your nodes. This will ensure that Hamvoip to Hamvoip connections work
quickly and 100%. Connections outside of the Hamvoip network may or may not
work depending on the mood of the Allstar server. This is NOT a Hamvoip
issue and it effects everyone on Allstar not just Hamvoip users but Hamvoip
users have the advantage of avoiding the problem when connecting to other
Hamvoip nodes.

In your case using a dyndns to resolve the IP address rather than astnodes
might be a better choice.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Fri, Aug 2, 2019 at 10:28 AM "Roger Coudé via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

>  I have two virtual nodes located in a same computer.
> 40020 and 40347
> Both are succesfully registered.
> That computer also has a VPN server
> Other machines in the network need the openvpn remote to be set to that
> server
> I was using 40347.asnode.org as remote address.
> Today 40347.asnode.org does not return a proper ip address, but
> 40020.asnode.org does.
> What is wrong with asnode.org
> Is there a more reliable method access I could use for my vpn without
> having to suscribe to a dynamic dns service?
> 73
> Roger
> VE2DBE
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>