<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Do you have a DNS server set on the module?<div class=""><br class=""></div><div class="">I think we should probably use 8.8.8.8 and 8.8.4.4 by default.</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/43" class="">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/43</a></div></blockquote><div class=""><div><br class=""></div><div>Regards, Mark.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 19 Apr 2018, at 12:46 AM, Greg D. <<a href="mailto:gregd2350@gmail.com" class="">gregd2350@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=us-ascii" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Michael Balzer wrote:<br class="">
<blockquote type="cite" cite="mid:d3cfa849-032a-dc74-5ed4-398a3cd915ef@expeedo.de" class="">
<pre wrap="" class="">Am 16.04.2018 um 22:16 schrieb Michael Balzer:
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">I have seen the queue overflow problem once on the current build, so it isn't solved. But it wasn't related to any action, it happened while
the module was idle.
To clarify, it's no problem if it resolves after some seconds, that may be due to a temporary mongoose lock / overload. If we can trigger that
reliably by some action, that would help to track this down.
</pre>
</blockquote>
<pre wrap="" class="">Short update: I could trigger it again now multiple times on the OTA page. It seems to be happening due to the update check running over the
modem line, it does not happen with modem disabled. I need to check in Wifi client mode.
Regards,
Michael
</pre>
</blockquote>
<br class="">
Hi Michael,<br class="">
<br class="">
Interesting... I was going to write back and say that the 3.003 to
3.004 update went very smoothly, with no queue overflows being
reported, and that all was well. I don't recall if the modem was
connected at the time, however.<br class="">
<br class="">
A side note for anyone having trouble connecting to AP mode with
their cell phone... I've always had a lot of trouble with timeouts
and such, and finally tracked it down to a similar issue as above.
If the phone has both an LTE and AP connection, the http request to
192.168.4.1 often goes out over the LTE path, and is therefore
doomed. Disabling LTE "fixes" that, but of course, also disables
your phone.(or at least the data part). I haven't found a good way
to beat some (routing) sense into the phone otherwise.<br class="">
<br class="">
This was with my new Google Pixel2, so it's not a matter of an old
buggy device. (Ok, so it's a new buggy device...)<br class="">
<br class="">
Also, the first time you connect to the AP, the phone <i class="">blocks</i>
all communications with it until you answer the annoying
notification (usually hidden in the background) that says "Hey, we
can't get to the Internet with that AP. Are you sure you want to
stay connected to it?", or words to that effect. Me thinks they
have taken this always connected Internet meme a bit too far.<br class="">
<br class="">
Greg<br class="">
<br class="">
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>