[Workaround] No Graph/Statistics (Hyper-V Virtual Switch)

Got a problem with Viscosity or need help? Ask here!

tridy

User avatar
Posts: 22
Joined: Sun Dec 23, 2012 3:56 am

Post by tridy » Thu Oct 03, 2013 6:34 am
The tabs with graph and statistics are not displaying any information after Hyper-V install (needed for Windows Phone emulator). I guess that is the virtual switch that could not be located.

Image
Code: Select all
Oct 02 10:06:55: State changed to Connecting
Oct 02 10:06:55: Viscosity 1.4.6 (1212)
Oct 02 10:06:55: Running on Microsoft Windows 8 Enterprise
Oct 02 10:06:55: Bringing up interface...
Oct 02 10:06:55: Checking reachability status of connection...
Oct 02 10:06:56: Connection is reachable. Starting connection attempt.
Oct 02 10:06:56: OpenVPN 2.3.2 Windows-MSVC [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Jun 18 2013
Oct 2 10:06:57: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Oct 2 10:06:57: UDPv4 link local: [undef]
Oct 2 10:06:57: UDPv4 link remote: [AF_INET][HIDDEN]:[HIDDEN]
Oct 2 10:07:02: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Oct 2 10:07:02: [HIDDEN] Peer Connection Initiated with [AF_INET][HIDDEN]
Oct 2 10:07:04: WARNING: potential conflict between --remote address [HIDDEN] and --ifconfig address pair [HIDDEN] -- this is a warning only that is triggered when local/remote addresses exist within the same /24 subnet as --ifconfig endpoints. (silence this warning with --ifconfig-nowarn)
Oct 2 10:07:04: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Oct 2 10:07:04: open_tun, tt->ipv6=0
Oct 2 10:07:04: TAP-WIN32 device [HIDDEN] opened: \\.\Global\{[HIDDEN]}.tap
Oct 2 10:07:04: Set TAP-Windows TUN subnet mode network/local/netmask = [HIDDEN] [SUCCEEDED]
Oct 2 10:07:04: Notified TAP-Windows driver to set a DHCP IP/netmask of [HIDDEN] on interface {[HIDDEN]} [DHCP-serv: [HIDDEN], lease-time: 31536000]Oct 2 10:07:09: ROUTE: route addition failed using CreateIpForwardEntry: The object already exists.   [status=5010 if_index=26]
Oct 2 10:07:09: env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Oct 2 10:07:09: Initialization Sequence Completed
Oct 02 10:07:09: [i]Unable to locate adapter used for this connection.[/i]
Oct 02 10:07:09: State changed to Connected
Last edited by tridy on Fri Oct 04, 2013 4:26 pm, edited 1 time in total.

Eric

User avatar
Posts: 1023
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Thu Oct 03, 2013 11:00 am
Hi tridy,

Integrating the Viscosity adapter into a Virtual Switch I'm afraid is something I've never seen done before, I'm actually slightly surprised your VPN tunnel is working at all as the Virtual Switch will try to hide it from applications in favour of the switch itself.

I'm not sure there is a lot we can do here, though we will certainly have a poke to see if there is anything we can do. To give you an idea what is happening, Viscosity is trying to get a traffic statistics report from the adapter, which is basically showing no traffic as the traffic is being diverted to the Virtual Switch that is encapsulating the Viscosity Adapter instead.

All I can suggest in the short term is removing the Viscosity adapter from the switch. If you wish for your Hyper-V to use your VPN for internet access, you should be able to create an internal network in Hyper-V with NAT, which should draw it's internet from your computers default route which should be the VPN Connection when it is connected.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

tridy

User avatar
Posts: 22
Joined: Sun Dec 23, 2012 3:56 am

Post by tridy » Fri Oct 04, 2013 8:21 am
Removing an adapter from the switch is not as straightforward as I thought.

Image

I cannot uncheck Hyper-V Extensible Virtual Switch, and as long as it is checked in, I cannot check in TCP/IPv4.

So, the process will probably require removal of the switch and not just disabling. I am afraid it might alter Hyper-V and I will have problems running emulator. To be on the safe side, I would rather have no statistics and know for sure that the adapters will work with Hyper-V/Emulator.

Thanks

regards

tridy

User avatar
Posts: 22
Joined: Sun Dec 23, 2012 3:56 am

Post by tridy » Fri Oct 04, 2013 4:25 pm
Ok, Hyper-V Manager has Virtual Switch Manager where a virtual switch can be added or deleted. I removed Viscosity Virtual Switch and it did uncheck Hyper-V Extensible Virtual Switch and checked in TCP/IPv4. So, now the Viscosity adapter is back to the original (prior to Hyper-V installation) state I have got the statistics and graph working.

Eric

User avatar
Posts: 1023
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Oct 08, 2013 2:20 pm
Hi Tridy,

Great to hear you got it going, the virtual switch manager in Hyper-V could stand to be a bit easier to navigate :).

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
5 posts Page 1 of 1