Mac OS 10.6 (Snow Leopard) Support

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

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Fri Aug 28, 2009 11:39 pm
Hi All,

Update: A beta version of 1.0.6 is now available. This release includes full 64 bit kernel support, fixes the alternate DNS support issue, and a few additional small improvements. It can be downloaded here.

Version 1.0.5 users can continue to use Viscosity under Snow Leopard if they are booted into 32 bit kernel mode, and are using Viscosity's default DNS support.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

sbe08

Posts: 1
Joined: Sat Aug 29, 2009 10:50 pm

Post by sbe08 » Sat Aug 29, 2009 10:54 pm
Hello James,

I've just upgraded and the configuration that I had is now failing. Here is the Viscosity log:
Code: Select all
Sat Aug 29 08:45:53 2009: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Sat Aug 29 08:45:53 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sat Aug 29 08:45:53 2009: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Sat Aug 29 08:45:53 2009: LZO compression initialized
Sat Aug 29 08:45:53 2009: UDPv4 link local: [undef]
Sat Aug 29 08:45:53 2009: UDPv4 link remote: 64.254.252.194:1194
Sat Aug 29 08:45:53 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat Aug 29 08:45:53 2009: [aragorn] Peer Connection Initiated with 64.254.252.194:1194
Sat Aug 29 08:45:54 2009: TUN/TAP device /dev/tap0 opened
Sat Aug 29 08:45:54 2009: /sbin/ifconfig tap0 delete
Sat Aug 29 08:45:54 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Sat Aug 29 08:45:54 2009: /sbin/ifconfig tap0 192.168.23.177 netmask 255.255.252.0 mtu 1500 up
Sat Aug 29 08:45:54 2009: /Applications/Viscosity.app/Contents/Resources/dnsupalt.py tap0 1500 1590 192.168.23.177 255.255.252.0 init
Sat Aug 29 08:45:55 2009: script failed: external program exited with error status: 1
Anything that I can try to get it to work?

Thanks,

Sylvain

GrantYN

Posts: 1
Joined: Sun Aug 30, 2009 2:26 am

Post by GrantYN » Sun Aug 30, 2009 2:33 am
Since installing Max OS X 10.6 last night I can not reach certain IPs with Viscosity running.

My Viscocity log:
Sat Aug 29 11:22:55 2009: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Sat Aug 29 11:22:55 2009: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sat Aug 29 11:22:55 2009: LZO compression initialized
Sat Aug 29 11:22:55 2009: Attempting to establish TCP connection with 69.93.174.106:443 [nonblock]
Sat Aug 29 11:22:56 2009: TCP connection established with 69.93.174.106:443
Sat Aug 29 11:22:56 2009: TCPv4_CLIENT link local: [undef]
Sat Aug 29 11:22:56 2009: TCPv4_CLIENT link remote: 69.93.174.106:443
Sat Aug 29 11:22:56 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat Aug 29 11:23:00 2009: [ComodoVPNS-2] Peer Connection Initiated with 69.93.174.106:443
Sat Aug 29 11:23:01 2009: TUN/TAP device /dev/tap0 opened
Sat Aug 29 11:23:01 2009: /sbin/ifconfig tap0 delete
Sat Aug 29 11:23:01 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Sat Aug 29 11:23:01 2009: /sbin/ifconfig tap0 172.20.1.107 netmask 255.255.255.0 mtu 1500 up
Sat Aug 29 11:23:01 2009: openvpn_execve: external program may not be called unless '--script-security 2' or higher is enabled. Use '--script-security 3 system' for backward compatibility with 2.1_rc8 and earlier. See --help text or man page for detailed info.
Sat Aug 29 11:23:01 2009: Route script failed: external program fork failed
Sat Aug 29 11:23:01 2009: Initialization Sequence Completed
I've never checked my log before I upgraded, so I don't no if those messages really mean anything.

When I disconnect my VPN connection all is good. Some sites will be reachable by http: after I disconnect and reconnect. POP3 addresses never seem reachable.

Thanks,

Grant

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sun Aug 30, 2009 8:40 pm
Hi Sylvain,
Anything that I can try to get it to work?
It looks like you have alternate DNS support turned on. Please see "Issue: Alternate DNS Support Fails" in the post above.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sun Aug 30, 2009 8:43 pm
Hi Grant,
Since installing Max OS X 10.6 last night I can not reach certain IPs with Viscosity running.
Judging by your log it looks like something is overriding Viscosity's attempt to allow the DNS support scripts to run. Try the following:

1. Open Viscosity's Preferences window and Edit your connection
2. Click the Advanced tab
3. If there is a line beginning with "script-security", delete that line
4. Add the command "script-security 2" (no quotes) on a new line
5. Click the Save button and try connecting

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

tiktoor

Posts: 2
Joined: Sun Aug 30, 2009 9:28 pm

Post by tiktoor » Sun Aug 30, 2009 9:31 pm
Hi James,
I have the following issue:

Viscosity crashes completly.

30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] Traceback (most recent call last):
30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] File "/Applications/Viscosity.app/Contents/Resources/main.py", line 17, in <module>
30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] import CrystalVPNAppDelegate
30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] File "/Viscosity Project/Viscosity/build/Release/Viscosity.app/Contents/Resources/CrystalVPNAppDelegate.py", line 19, in <module>
30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] File "/Viscosity Project/Viscosity/build/Release/Viscosity.app/Contents/Resources/OpenVPNConn.py", line 20, in <module>
30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] File "/Viscosity Project/Viscosity/build/Release/Viscosity.app/Contents/Resources/GrowlSupport.py", line 22, in <module>
30.08.09 13:18:34 [0x0-0x63063].com.viscosityvpn.Viscosity[1518] objc.BadPrototypeError: Python signature doesn't match implied Objective-C signature for <unbound selector applicationNameForGrowl: of rcGrowl at 0x4128860>
30.08.09 13:18:34 Viscosity[1518] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '/Viscosity Project/Viscosity/main.m:44 main() PyRun_SimpleFile failed with file '/Applications/Viscosity.app/Contents/Resources/main.py'. See console for errors.'
*** Call stack at first throw:
(
0 CoreFoundation 0x9814058a __raiseError + 410
1 libobjc.A.dylib 0x96cd0f49 objc_exception_throw + 56
2 CoreFoundation 0x981402b8 +[NSException raise:format:arguments:] + 136
3 CoreFoundation 0x9814022a +[NSException raise:format:] + 58
4 Viscosity 0x00002a76 main + 796
5 Viscosity 0x0000272e start + 54
)
30.08.09 13:18:34 com.apple.launchd.peruser.501[532] ([0x0-0x63063].com.viscosityvpn.Viscosity[1518]) Job appears to have crashed: Trace/BPT trap
30.08.09 13:18:34 ReportCrash[1521] Saved crash report for Viscosity[1518] version ??? (???) to /Users/pascal/Library/Logs/DiagnosticReports/Viscosity_2009-08-30-131834_Epikur.crash

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Aug 31, 2009 4:06 pm
Hi tiktoor,
I have the following issue:

Viscosity crashes completly.
It looks like you are using an old version. Only version 1.0.5 (and above) are supported under Snow Leopard.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs

tiktoor

Posts: 2
Joined: Sun Aug 30, 2009 9:28 pm

Post by tiktoor » Mon Aug 31, 2009 7:08 pm
Ok James, this works.

I thought, my Installation had to be up to date because I am using Viscosity on a regular basis.
It would be a good hint to tell the Users, that the auto-update might not work if they installed SN.
I tried cmd-i but it only gave me the 1.0 info. So there is no possibility to now, if you are using the right version.

Thank you for your help!
Greeets,
pascal

hayssam

Posts: 5
Joined: Mon Aug 31, 2009 7:49 pm

Post by hayssam » Mon Aug 31, 2009 8:00 pm
Sorry but I can't connect (anymore).. :cry:
Using 10.6 on an unibody MacBook, tried the 32 thing, tried the "script-security 2" thing to no avail.
Connecting to an Astaro server,

resolv-retry infinite
--proto tcp-client
auth MD5
cipher AES-192-CBC
tls-remote /C=de/L=xxxx/O=xxx/CN=xxxx/emailAddress=[email protected]
reneg-sec 0

that used to work, now it looks like viscosity is connecting for a second (green icon) and then is reconnecting.
My log (the ip's are xxxed) :

Mon Aug 31 11:56:28 2009: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Mon Aug 31 11:56:28 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Aug 31 11:56:28 2009: LZO compression initialized
Mon Aug 31 11:56:28 2009: Attempting to establish TCP connection with xxxxx:443 [nonblock]
Mon Aug 31 11:56:29 2009: TCP connection established with xxxxx:443
Mon Aug 31 11:56:29 2009: TCPv4_CLIENT link local: [undef]
Mon Aug 31 11:56:29 2009: TCPv4_CLIENT link remote: xxxxxx:443
Mon Aug 31 11:56:30 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Aug 31 11:56:32 2009: [FW01MRKDE] Peer Connection Initiated with xxxxxxx:443
Mon Aug 31 11:56:33 2009: TUN/TAP device /dev/tun0 opened
Mon Aug 31 11:56:33 2009: /sbin/ifconfig tun0 delete
Mon Aug 31 11:56:33 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Mon Aug 31 11:56:33 2009: /sbin/ifconfig tun0 192.168.111.10 192.168.111.9 mtu 1500 netmask 255.255.255.255 up
Mon Aug 31 11:56:33 2009: /Applications/Internet/VPN - Viscosity/Viscosity.app/Contents/Resources/dnsup.py tun0 1500 1556 192.168.111.10 192.168.111.9 init
Mon Aug 31 11:56:33 2009: Initialization Sequence Completed
Mon Aug 31 11:56:34 2009: Connection reset
Mon Aug 31 11:56:34 2009: SIGUSR1[soft
Mon Aug 31 11:56:34 2009: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Mon Aug 31 11:56:34 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Aug 31 11:56:34 2009: Re-using SSL/TLS context
Mon Aug 31 11:56:34 2009: LZO compression initialized
Mon Aug 31 11:56:34 2009: Attempting to establish TCP connection with xxxxxxxxx:443 [nonblock]
Mon Aug 31 11:56:35 2009: TCP: connect to xxxxxx:443 failed
Mon Aug 31 11:56:41 2009: TCP: connect to xxxxxxxxxx:443 failed
Mon Aug 31 11:56:47 2009: TCP connection established with xxxxxxxxx:443
Mon Aug 31 11:56:47 2009: TCPv4_CLIENT link local: [undef]
Mon Aug 31 11:56:47 2009: TCPv4_CLIENT link remote: xxxxxxxxxx:443
Mon Aug 31 11:56:48 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Aug 31 11:56:50 2009: [FW01MRKDE] Peer Connection Initiated with xxxxxxxxxx:443
Mon Aug 31 11:56:51 2009: Preserving previous TUN/TAP instance: tun0
Mon Aug 31 11:56:51 2009: Initialization Sequence Completed
Mon Aug 31 11:56:53 2009: Connection reset
Mon Aug 31 11:56:53 2009: SIGUSR1[soft
Mon Aug 31 11:56:53 2009: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Mon Aug 31 11:56:53 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Aug 31 11:56:53 2009: Re-using SSL/TLS context
Mon Aug 31 11:56:53 2009: LZO compression initialized
Mon Aug 31 11:56:53 2009: Attempting to establish TCP connection with xxxxxxx:443 [nonblock]
Mon Aug 31 11:56:54 2009: TCP: connect to xxxxxxxx:443 failed


Any help would be gratefully appreciated

mmk

Posts: 1
Joined: Tue Sep 01, 2009 1:51 am

Post by mmk » Tue Sep 01, 2009 1:52 am
19 posts Page 1 of 2