Dont mix Viscosity and openvpn client

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

Gilles

Posts: 3
Joined: Sat Aug 20, 2011 2:15 am

Post by Gilles » Sat Aug 20, 2011 2:21 am
Hi
Just for information (but it could be nice to solve) : I installed in my W7 both Viscosity and openvpn client.
Viscosity does not connect as long as TAP-Win32 Adapter V9 (which is the Tap Driver used by open vpn) is installed
This driver is partly considered by Viscosity instead of the Viscosity Virtual Adapter V9.1
After having deactivated the TAP-Win32 Adapter, Viscosity works like a charm

Gilles

Eric

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

Post by Eric » Mon Aug 22, 2011 7:25 pm
Hi Gilles,

What version of Viscosity and OpenVPN are you using? I have several of OpenVPNs TAP-Win32 adapters as well as our Viscosity Virtual Adapters installed and enabled concurrently, as do many of our users, and we have never faced nor heard of this issue occurring before.

Also, are you allowing Viscosity to manage the adapters or have you ticked the box not too? Could you please check a valid dev-node is displayed in the Advanced tab when you edit your connection as well?

Cheers,

Eric
Eric Thorpe
Viscosity Developer

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

Gilles

Posts: 3
Joined: Sat Aug 20, 2011 2:15 am

Post by Gilles » Fri Aug 26, 2011 12:59 am
Hi Eric
Sorry for the delay.. I'm not really in trouble since I deactivated the openvpn Tap .. Anyhow , here are your answers :
- I am using the lastest OpenVPN TAP adaptor : the driver says : TAP-Win32 Provider V9 version 9.0.0.8 dates 04/19/2010 from Open VPN Technologies Inc.
-I am also using Viscosity latest release , again the driver says Viscosity Virtual Adapter V9.1 from Sparklabs version 9.0.0.8 dated 04/19/2010 from Sparklabs

- May be not needless to say, I imported the openVPN data from my original Open VPN client into Viscosity at install time.

In advanced tab, the "dont create a network adapter "is unckecked

Anyhow its does'nt burden me... i just experienced disabled viscosity service so I had to restart it.. may be my windows fault :oops:
Gilles

Eric

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

Post by Eric » Fri Aug 26, 2011 2:38 pm
Thanks for the reply Gilles,

We will have a look into it regardless to triple check there isn't something we've missed that may be causing an issue. We disable Viscosity's adapters when they're not in use for the very reason of preventing any issues with OpenVPN's official release, we've just never encountered it happening the other way around.

Cheers,

Eric
Eric Thorpe
Viscosity Developer

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

Gilles

Posts: 3
Joined: Sat Aug 20, 2011 2:15 am

Post by Gilles » Sat Sep 03, 2011 4:49 am
Thanks for your reply Eric.
I have some more things about :
1) I may believe my first pb appeared because the TAP adaptor of openVPN client was not disabled.
I have several VPN servers : there is one adaptor per destination (probably related to the {dev node..} which is appended in the detailed configuration when the adaptor is being created)
When I connect/disconnect, the adaptors return to disable which seems to be the status when no VPN is active
So may be the openVPN TAP was not disabled when i launched for the first time a VPN with Viscosity and it confused about the adaptor..
Since I dont know the detailed behavior, I can't go deeper.... lets say it is probably due to something like I describe above.

2)Now A second point, not related to the previous but which makes me worry about my customer :
I had a crash of viscosity (was doing crazy telnet characters.... since I was showing viscosit to a customer, i did'nt have time to detail what led to this crash)
I tried to restart, was asked for administrator rights to create an adaptor but it failed
Restarting the computer just told me the viscosity service could'nt be contacted (again I could'nt check if the service was running but I think it was not)
so i deleted the adaptors and restarted the computer..the service went on and i could continue, the adaptor has been created

My current thinking about that is :
If Viscosity crashs, something in the adaptor remains even If I restart the computer... This prevents the viscosity service to start

All I want to do is to find a procedure for the customer if it happens.. so currently, if he finds the service has gone, i'll ask to delete the adaptors and restart the computer (he does not know how to start a service)

If It can help; here are the windows logs
First is the net run time error
second is the subsequent application error (quite obvious)
last is the service start failure (service control manager)
Hope it helps
Gilles
Code: Select all
Application: Viscosity.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ObjectDisposedException
Stack:
   at DLRCachedCode.networkChangedThread$325(System.Runtime.CompilerServices.Closure, IronPython.Runtime.PythonFunction, System.Object)
   at IronPython.Runtime.PythonFunction+FunctionCaller`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Call1(System.Runtime.CompilerServices.CallSite, IronPython.Runtime.CodeContext, System.Object, System.__Canon)
   at DynamicClass.CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, System.Object)
   at System.Dynamic.UpdateDelegates.UpdateAndExecute1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Runtime.CompilerServices.CallSite, System.__Canon)
   at DynamicClass._Scripting_(System.Object[])
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()
second :
Code: Select all
Nom de l’application défaillante Viscosity.exe, version : 1.3.2.1082, horodatage : 0x4e37d4c2
Nom du module défaillant : KERNELBASE.dll, version : 6.1.7601.17651, horodatage : 0x4e2111c0
Code d’exception : 0xe0434352
Décalage d’erreur : 0x0000d36f
ID du processus défaillant : 0x1950
Heure de début de l’application défaillante : 0x01cc67b7f0b43dcf
Chemin d’accès de l’application défaillante : C:\Program Files\Viscosity\Viscosity.exe
Chemin d’accès du module défaillant: C:\Windows\system32\KERNELBASE.dll
ID de rapport : 4bcfe1df-d585-11e0-be1a-00238be0c059
last (no reply after start of viscosity service)
Code: Select all
Le service Viscosity Service n’a pas pu démarrer en raison de l’erreur : 
Le service n’a pas répondu assez vite à la demande de lancement ou de contrôle.

Eric

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

Post by Eric » Tue Sep 06, 2011 6:28 pm
Hi GIlles,

Just to let you know we are looking into all of this. If the service does crash for some reason, a simple restart of the PC should bring it back up regardless of whether an adapter was in the process of creating or not.

This crash from the service sounds like an issue from the 1.3.1 service. Can you make sure you are running the latest version of the software? That being 1.3.2. If you are running 1.3.2, we have a couple of theories as to why it crashed that we are already looking into.

Thanks for your feedback.

Regards,

Eric
Eric Thorpe
Viscosity Developer

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

cliffennis

Posts: 1
Joined: Fri Jan 27, 2012 1:48 pm

Post by cliffennis » Fri Jan 27, 2012 1:52 pm
I've been running the OpenVPN GUI client on my machine. Tonight I installed Viscosity and connected the VPN. It showed as being connected, got a valid client IP, but it wouldn't route any traffic through. So I disconnected, disabled the TAP-Win32 Adapter V9 and Viscosity works great now. Glad I found this thread, the problem was driving me crazy!

Elo

Posts: 1
Joined: Sat Jan 28, 2012 2:53 am

Post by Elo » Sat Jan 28, 2012 2:56 am
I have the same issue and the same action resolved it for me. Been running OpenVPN GUI +++ with a lot of comments about the bad user interface. During testing we and connected ok but could not get anything through the channel. Will now roll out on all our machines since the product is good and reasonbaly priced..

Thx

Eric

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

Post by Eric » Mon Jan 30, 2012 7:06 pm
Thanks for the feedback guys!

We're still having problems reproducing this problem on our test machines. If either of you are able, would you be able to provide us with a copy of your configuration, with anything confidential omitted of course, and the version of OpenVPN you are using? We really want to get to the bottom of this one.

Cheers,

Eric
Eric Thorpe
Viscosity Developer

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