[arm-allstar] Node not connecting if internet is flakey

[Doug Crompton]

Chris,

 There is a lot more to this than just comparing wired and wireless. If a
connection is flaky then the best thing to do is improve the connection or
not use it. There also are many factors here. If you are not using hamvoip
registration and DNS the problem could be it is not registering properly.
The Allstar registration is currently using a 10 minute timeout window due
to there lousy sever performance. This would be a much bigger factor on a
wireless cell network where IP addresses could change wildly.

If you use hamvoip DNS, which you would be with the lastest image, and you
have a hamvoip registration things should work much better in that regard
BUT only to other nodes doing the same thing. Once we get our registration
code out for all this will be substantially better.


*73 Doug*

*WA3DSP*

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

On Mon, Oct 15, 2018 at 10:06 PM "chris novara via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I’ve got a node running latest update
>
> Connected to cellular modem that has weak signal at times and can lose
> connection and reconnect.
>
> Is it a fact that wired (eth) connections will recover better then
> wireless?
>
> I’m using auto reconnect that always works great at boot.
>
> When watching the CLI, it’s shows correct IP for my hub, but then says
> slow reply.
>
> If I shut the node down for 15 mins and then restart, it will connect
> every time until internet becomes flakey and then this all repeats.
>
> Ideas ?
>
> Thank you,
>
> Chris Novara, AB7BS
> Eugene Oregon
>
>
> _______________________________________________
>
> 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