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")?
Note that the technet forum talks about ipv6 *route*, not "set address", and
this is not part of your patch...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
