<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="">Craig,<div class=""><br class=""></div><div class="">I get the same (with for-v3.3):</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">W (2940) ssh: Couldn't initialize wolfSSL debugging, error -174: Unknown error code</div></blockquote><div class=""><div><br class=""></div><div>I guess it is just a warning. Probably some debugging config setting.</div><div><br class=""></div><div>But wifi, web and others work ok for me. Only problems I have with for-v3.3 branch are (a) the web dashboard modem status, and (b) the TLS certificate verification against <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a>. I am working on both.</div><div><br class=""></div><div>Regards, Mark.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 12 Mar 2021, at 9:46 AM, Craig Leres <<a href="mailto:leres@xse.com" class="">leres@xse.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 3/10/21 11:23 PM, Stephen Casner wrote:<br class=""><blockquote type="cite" class="">Michael and anyone else who's game:<br class="">I now have an updated mongoose-wolfssl branch ready to be tested. The<br class="">reason for the 90-second lockup mentioned in the previous post is a<br class="">whole lot of math for a prime-number validation that's part of the<br class="">Diffie-Hellman step. It was actually 87 seconds for Mark's server and<br class="">28 seconds for Michael's due to differences in certificates. That<br class="">prime-number validation is required for FIPS compliance, which WolfSSL<br class="">supports, but we don't need it. I spent quite a while digging into<br class="">this to find where the process was getting stuck. Finally I got help<br class="">from WolfSSL support suggesting a configuration option that avoids<br class="">this extra check.<br class="">So now I have an implementation using mongoose with wolfssl that<br class="">connects successfully to both servers with a 3-4 second delay. (I<br class="">don't recall what the delay was for the MBEDTLS-based implementation.)<br class="">I think the memory usage looks OK. I still have not taken any steps<br class="">to reduce any resources used by the MBEDTLS code as accessed for other<br class="">purposes.<br class="">Included in the debugging was another version update on the Wolf code<br class="">to wolfssh 1.4.6 and wolfssl 4.7.0.<br class=""></blockquote><br class="">I tried building/booting this on my dev module( 3.2.016-66-g93e0cf3e); but for some time now the for-v3.3 branch has been broken for me. When the module first boots the web gui works long enough for me to login and then it times out. From that point on I can't get the web gui or ssh to respond. It will return pings. The serial console is fine (and that's how I switch back to build based on master).<br class=""><br class="">I just did a fresh reboot and captured the serial console output and noticed this:<br class=""><br class=""> W (4484) ssh: Couldn't initialize wolfSSL debugging, error -174: Unknown error code<br class=""><br class="">I think it happened around the time I lost wifi connectivity.<br class=""><br class="">My sdkconfig is close to support/sdkconfig.default.hw31, I have CONFIG_SPIRAM_CACHE_WORKAROUND turned off along with a lot of vehicles.<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Craig<br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></body></html>