Mac OS 10.6 (Snow Leopard) Support

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

hayssam

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

Post by hayssam » Tue Sep 01, 2009 3:20 am
thanks a lot and I dearly hope that these help everybody else, but for me they didn't do the trick, any other idea ?? Maybe anything you can read out of the log ?
For my stupid eye it looks like the connection establishes (green locked icon in the menu bar) and then is dropped again. Right about here:

Mon Aug 31 19:18:43 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 19:18:44 2009: Initialization Sequence Completed
Mon Aug 31 19:18:45 2009: Connection reset

does this help ?

James

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

Post by James » Tue Sep 01, 2009 5:48 am
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
James Bekkema
Viscosity Developer

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

James

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

Post by James » Tue Sep 01, 2009 5:52 am
Hi hayssam,

Your issue doesn't seem linked directly to Snow Leopard - it appears to either be a configuration issue, or the OpenVPN server is disconnecting you once you have connected. Can you try connecting again using the beta version of 1.0.6 (linked above), and post the full log from the Details window again?

Cheers,
James
James Bekkema
Viscosity Developer

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

hayssam

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

Post by hayssam » Tue Sep 01, 2009 6:53 am
Thanks a lot James for having a look, 1.0.6 installed, lots of checkmarks set and removed and I haven't gotten anywhere.
Here the requested log:
Code: Select all
Mon Aug 31 22:46:22 2009: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Mon Aug 31 22:46:22 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Aug 31 22:46:22 2009: LZO compression initialized
Mon Aug 31 22:46:22 2009: Attempting to establish TCP connection with xxx:443 [nonblock]
Mon Aug 31 22:46:23 2009: TCP connection established with xxx:443
Mon Aug 31 22:46:23 2009: TCPv4_CLIENT link local: [undef]
Mon Aug 31 22:46:23 2009: TCPv4_CLIENT link remote: xxx:443
Mon Aug 31 22:46:23 2009: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Aug 31 22:46:27 2009: [FW01MRKDE] Peer Connection Initiated with xxx:443
Mon Aug 31 22:46:28 2009: TUN/TAP device /dev/tun0 opened
Mon Aug 31 22:46:28 2009: /sbin/ifconfig tun0 delete
Mon Aug 31 22:46:28 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Mon Aug 31 22:46:28 2009: /sbin/ifconfig tun0 192.168.111.10 192.168.111.9 mtu 1500 netmask 255.255.255.255 up
Mon Aug 31 22:46:28 2009: /Users/sam/Downloads/Viscosity.app/Contents/Resources/dnsup.py tun0 1500 1556 192.168.111.10 192.168.111.9 init
Mon Aug 31 22:46:28 2009: Initialization Sequence Completed
Mon Aug 31 22:46:30 2009: Connection reset, restarting [-1]
Mon Aug 31 22:46:30 2009: SIGUSR1[soft,connection-reset] received, process restarting
Mon Aug 31 22:46:30 2009: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Mon Aug 31 22:46:30 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Aug 31 22:46:30 2009: Re-using SSL/TLS context
Mon Aug 31 22:46:30 2009: LZO compression initialized
Mon Aug 31 22:46:30 2009: Attempting to establish TCP connection with xxxx:443 [nonblock]
Mon Aug 31 22:46:31 2009: TCP: connect to xxx:443 failed, will try again in 5 seconds: Connection refused
Mon Aug 31 22:46:37 2009: TCP: connect to xxx:443 failed, will try again in 5 seconds: Connection refused

pdan

Posts: 1
Joined: Tue Sep 01, 2009 11:00 pm

Post by pdan » Tue Sep 01, 2009 11:02 pm
An alternative patch (source code available) that ports the TunTap OSX kexts to SnowLeopard x64 is available at http://blog.esync.org/ (or directly http://pastebin.com/mfecc895)

Enjoy
Dan

ldm

Posts: 1
Joined: Wed Sep 02, 2009 12:54 am

Post by ldm » Wed Sep 02, 2009 12:59 am
Hi,

I upgraded to the 1.0.6 (I have SL on my MBP). Unfortunately, I still have DNS issues (it used to work with Leopard).

Here is a simple test:
Code: Select all
tanatlocwl /Users/ldm [27] -> nslookup lamp
;; Got recursion not available from 10.44.100.7, trying next server
;; Got recursion not available from 10.44.100.7, trying next server
Server:		10.44.100.1
Address:	10.44.100.1#53

** server can't find lamp: NXDOMAIN

tanatlocwl /Users/ldm [28] -> nslookup 
> server 10.44.100.7
Default server: 10.44.100.7
Address: 10.44.100.7#53
> lamp
Server:		10.44.100.7
Address:	10.44.100.7#53

Name:	lamp.dynadec.local
Address: 10.44.100.6
As you can see, a direct NSlookup fails. But if I manually go in, it works fine. The content of resolv.conf is as follows:
Code: Select all
tanatlocwl /Users/ldm [29] -> cat /etc/resolv.conf 
#
# Mac OS X Notice
#
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
#
# This file is automatically generated.
#
domain dynadec.local
nameserver 10.44.100.7
nameserver 10.44.100.1

Any idea on how I can resolve this issue?

Thanks!
--
Laurent

hayssam

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

Post by hayssam » Wed Sep 02, 2009 9:28 pm
trying to help without knowing:

my IT contact tells me it's fine on their side, he doesn't get any errors and is not sending a disconnect. The only hint he had was from eperience with a windows machine. There the problem was an underlying service which didn't have admin rights and therefore was not able to modify routing tables.
So lets make this a more general question:
am I the only one to have problems - is it just me - ? or is it more of a general nature ?

marco_coisson

Posts: 1
Joined: Thu Sep 03, 2009 5:27 am

Post by marco_coisson » Thu Sep 03, 2009 5:37 am
Hi, I'd like to add my experience with Viscosity (which is by far my favorite VPN software) and Snow Leopard. I can correctly login to my VPN using the same configuration that works on Leopard, and I even get my IP address. But after that I can't surf the web, or even ping any host, not even by directly typing the IP address. If I enable the alternate DNS support in version 1.0.6 beta, then I can visit web sites, but I still can't access resources in my VPN: pinging hosts even with their IP address results in 100% packet loss (reason: request timeout).
I'm sure that the configuration is correct, because it works with Viscosity under Leopard and it even works with Tunnelblick 3 under Snow Leopard.
Thank you for your support: I can't wait for a Viscosity update fully compatible with MacOS X 10.6. :)

pdccd

Posts: 1
Joined: Thu Sep 03, 2009 8:35 pm

Post by pdccd » Thu Sep 03, 2009 8:39 pm
Hi, update macbookpro unibody to SL, after that 1.0.5 viscosity connects successfull but i can't connect to any host, updated to 1.0.6 version the same, connected to ip, no traffic. here is log :

Thu Sep 3 13:32:48 2009: IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Thu Sep 3 13:32:48 2009: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Thu Sep 3 13:32:48 2009: LZO compression initialized
Thu Sep 3 13:32:48 2009: Attempting to establish TCP connection with 95.211.2.34:443
Thu Sep 3 13:32:48 2009: TCP connection established with 95.211.2.34:443
Thu Sep 3 13:32:48 2009: TCPv4_CLIENT link local: [undef]
Thu Sep 3 13:32:48 2009: TCPv4_CLIENT link remote: 95.211.2.34:443
Thu Sep 3 13:32:50 2009: [NL1] Peer Connection Initiated with 95.211.2.34:443
Thu Sep 3 13:32:51 2009: gw 192.168.0.1
Thu Sep 3 13:32:51 2009: TUN/TAP device /dev/tap0 opened
Thu Sep 3 13:32:51 2009: /sbin/ifconfig tap0 delete
Thu Sep 3 13:32:51 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Thu Sep 3 13:32:51 2009: /sbin/ifconfig tap0 10.8.2.91 netmask 255.255.0.0 mtu 1500 up
Thu Sep 3 13:32:51 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tap0 1500 1576 10.8.2.91 255.255.0.0 init
Thu Sep 3 13:32:53 2009: Initialization Sequence Completed


My old macbook with 1.0.5 and leopard mac os works with same exactly settings.
19 posts Page 2 of 2