On Fri, Jul 3, 2015 at 10:32 AM, David Woodhouse <dwmw2 at infradead.org> wrote: >> So looks like it's really all about the adapter name chosen by some Windows magic. >> In my Opinion, setting the name explicitly to something clear like "TUN/TAP openvpn/openconnect" >> would help anyway. You could tell adapters apart much easier then. > I haven't looked at precisely how Nikos has incorporated the OpenVPN > signed driver into his OpenConnect installer. It might be possible to > change things so that it gets a more appropriate name. Hi, I haven't followed the issue and it is unclear to me what the issue is. About packaging, I simply ship and run the tun/tap driver installer as it is in openvpn. If the issue affects both openvpn and openconnect it may make sense to report it to them so that the issue is fixed upstream. regards, Nikos
