On Thu, 2015-10-22 at 15:51 +0200, Gert Doering wrote: > Hi, > > On Thu, Oct 22, 2015 at 04:47:56PM +0300, Olli Männistö wrote: > > Many VPN providers like us experience these issues and have to give users > > workarounds to fix it. Here are couple of examples: > > https://community.f-secure.com/t5/F-Secure/After-a-Windows-10-upgrade/ta-p/72732 > > https://forum.hidemyass.com/index.php/topic/18331-connection-problem/ > > https://vpn.ccrypto.org/page/install-windows > > > > There is also workaround on Microsoft Technet forum > > ( > > https://social.technet.microsoft.com/Forums/windowsserver/en-US/bb73aa66-34c3-49c2-8a2d-def03ee03902/element-not-found-error-when-trying-to-define-static-ipv6-route?forum=ipv6) > > to use index instead of adapter name. If it's reliable that we always get > > the index figured out it doesn't need to have fallback to use adapter name. > > In our testing it seems to work well with index and fix the described issue. > > So what is the underlying issue here? Non-ASCII characters in the > device name ("this *should* have been fixed a few releases ago")?
No, and not spaces (despite the vpn.ccrypto.org link above suggesting that it is). The issue is not known. Seriously, "because Windows". Renaming the interface, and then renaming it back to precisely what it was before, and doing registry dumps and checking that things really *are* just the same as they were before, is sufficient to fix it. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
