On Fri, 2015-07-17 at 11:53 +0200, Martin Pauly wrote: > > just a status update on this, and sorry for the delay. > Many sorts of "playing around", i.e. renaming the tun interface > seem to fix the problem permanently. E.g. renaming the adapter > forth and back will leave you with a permanently working system. > So I now believe this is not only about the adapter names > but rather about some subtle change in some other part of > the environment, perhaps not even the registry. > So to reproduce the error, you need a fresh install almost every time > you try something. This is no big deal with a VM image, of course, > but cornering the error might require more than dumping a registry branch > "before" and "after". I hope that in a couple of weeks from now I am able > to report something more detailed as I should have a little more time then. Any progress on this? I'm pondering a minor release of OpenConnect with a few fixes that have accumulated, and wouldn't mind rolling in a fix for this if we can find one. It would also be useful to know if it affects OpenVPN. Partly because we can then make it Someone Else's Problem :) -- dwmw2 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5691 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20150805/7579a443/attachment.bin>
