On Thu, 2014-10-02 at 00:13 +0800, Niels Peen wrote: > > The more lost packets from the server the more likely a timeout could > > occur. The current value for DTLS is 12 seconds and given that the wait > > time doubles per lost packet it would take 4 lost packets for this error > > to pop up. I had the impression though that openconnect will retry > > connecting using DTLS isn't that the case? > > OpenConnect on Windows gives up after this error, which is indeed > different from how it behaves on Android. > The OpenConnect-GUI is left in a stuck state. I have to close the GUI and > restart it to try again. Indeed... It seems it handled the failure of dtls_connect() inappropriately. It should be fixed now though. regards, Nikos
