Skip to content
no connection after upgrading to 1.3.1 / 1.3.0
Got a problem with Viscosity or need help? Ask here!
- Posts: 8
- Joined: Thu Jun 30, 2011 10:32 pm
Hi James,
the "script-security 2" (without the quotes ) did the trick. Now I'm back on my clients network.
I didn't change anything in my settings. Is this a new behavior from the openvpn software?
Thank you very much!
Volker
the "script-security 2" (without the quotes ) did the trick. Now I'm back on my clients network.
I didn't change anything in my settings. Is this a new behavior from the openvpn software?
Thank you very much!
Volker
Hi ElGrowZone,
Glad to hear it is now all working!
Well version 1.2.3 of Viscosity (and previous versions) used OpenVPN's up/down script options to implement DNS support. Versions 1.3 and above of Viscosity do this in a much nicer fashion, which frees up the up/down scripting support to anyone. Basically you had a up script (and possibly a down script set). With previous versions Viscosity DNS support scripts would have caused this to be ignored (and Viscosity elevating the script-security level may have also worked in your favour), however with this gone suddenly your connection's script options came back into play.
Cheers,
James
Glad to hear it is now all working!
Well version 1.2.3 of Viscosity (and previous versions) used OpenVPN's up/down script options to implement DNS support. Versions 1.3 and above of Viscosity do this in a much nicer fashion, which frees up the up/down scripting support to anyone. Basically you had a up script (and possibly a down script set). With previous versions Viscosity DNS support scripts would have caused this to be ignored (and Viscosity elevating the script-security level may have also worked in your favour), however with this gone suddenly your connection's script options came back into play.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hello.
Im having a similar if not same problem. I have not upgraded to lion and im using viscosity on the mac OSX 1.6. My log is below, I also have a Cisco RVS4000 VPN Router.
Jul 28 19:41:27: Viscosity 1.3.3 (1024)
Jul 28 19:41:27: Checking reachability status of connection...
Jul 28 19:41:27: Connection is reachable. Starting connection attempt.
Jul 28 19:41:29: OpenVPN 2.2.0 x86_64-apple-darwin10.7.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Jun 17 2011
What is wrong, and why can't I get VPN to work?
Thanks,
-Drew Toma
Im having a similar if not same problem. I have not upgraded to lion and im using viscosity on the mac OSX 1.6. My log is below, I also have a Cisco RVS4000 VPN Router.
Jul 28 19:41:27: Viscosity 1.3.3 (1024)
Jul 28 19:41:27: Checking reachability status of connection...
Jul 28 19:41:27: Connection is reachable. Starting connection attempt.
Jul 28 19:41:29: OpenVPN 2.2.0 x86_64-apple-darwin10.7.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Jun 17 2011
What is wrong, and why can't I get VPN to work?
Thanks,
-Drew Toma
Hi Drew,
Try checking the Console for messages from OpenVPN (see link below). It looks likely it is exiting abruptly for some reason and not sending the reason to the OpenVPN log.
http://www.thesparklabs.com/support/vie ... nsole_log/
Cheers,
James
Try checking the Console for messages from OpenVPN (see link below). It looks likely it is exiting abruptly for some reason and not sending the reason to the OpenVPN log.
http://www.thesparklabs.com/support/vie ... nsole_log/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs