Skip to content
Snow Leopard - again
Got a problem with Viscosity or need help? Ask here!
Hi,
just upgraded to Snow Leopard..Viscosity works bad (cannot load any pages 15 seconds after connecting). So I check the forums, download the latest beta..but unfortunately it still does the same. Any other hints to work it under SL ?
just upgraded to Snow Leopard..Viscosity works bad (cannot load any pages 15 seconds after connecting). So I check the forums, download the latest beta..but unfortunately it still does the same. Any other hints to work it under SL ?
Code: Select all
Tue Sep 15 13:20:54 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Tue Sep 15 13:20:54 2009: LZO compression initialized
Tue Sep 15 13:20:54 2009: UDPv4 link local: [undef]
Tue Sep 15 13:20:54 2009: UDPv4 link remote: 77.78.98.217:39194
Tue Sep 15 13:20:55 2009: [server] Peer Connection Initiated with 77.78.98.217:39194
Tue Sep 15 13:20:56 2009: TUN/TAP device /dev/tap0 opened
Tue Sep 15 13:20:56 2009: /sbin/ifconfig tap0 delete
Tue Sep 15 13:20:56 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Tue Sep 15 13:20:56 2009: /sbin/ifconfig tap0 81.0.220.1 netmask 255.255.254.0 mtu 1500 up
Tue Sep 15 13:20:56 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tap0 1500 1574 81.0.220.1 255.255.254.0 init
Tue Sep 15 13:20:57 2009: Initialization Sequence Completed
The same happens to me either if i connect via LAN or via wireless or via usb broadband key ....
I' ve noticed that the command netstat -nr from terminal gives a lot of tap interfaces linked to unknown IP addresses ... could you verify if is the same for you ??
Thanks ..... Bye.
Fred.
I' ve noticed that the command netstat -nr from terminal gives a lot of tap interfaces linked to unknown IP addresses ... could you verify if is the same for you ??
Thanks ..... Bye.
Fred.
Hi Michal,
It's possible there may be some differences between Viscosity's OpenVPN config file and Tunnelblick's - you may like to compare the two and see if there are any noticeable differences (for example missing or added OpenVPN commands). You can find Viscosity's OpenVPN config file for your connection at:
Your Home Directory->Library->Application Support->Viscosity->OpenVPN->#->config.conf
While Tunnelblick's can be found at:
Your Home Directory->Library->openvpn->name.conf
If you are using a TAP connection, like Fred, you may have Viscosity's DHCP support turned on when it's not needed (which can cause issues like being assigned multiple IPs, extra routes, etc). Try editing your connection in Viscosity, and under the General tab un-tick the "Enable DHCP" checkbox.
I'd also recommend you try increasing the route delay incase they are being added before the TAP network interface is fully setup. Please see this post for instructions.
Finally, you may like to try disabling Viscosity's DNS support to see if it could be interfering. To do this, edit your connection in Viscosity, un-tick the "Enable DNS Support" checkbox, and then click Save.
Cheers,
James
It's possible there may be some differences between Viscosity's OpenVPN config file and Tunnelblick's - you may like to compare the two and see if there are any noticeable differences (for example missing or added OpenVPN commands). You can find Viscosity's OpenVPN config file for your connection at:
Your Home Directory->Library->Application Support->Viscosity->OpenVPN->#->config.conf
While Tunnelblick's can be found at:
Your Home Directory->Library->openvpn->name.conf
If you are using a TAP connection, like Fred, you may have Viscosity's DHCP support turned on when it's not needed (which can cause issues like being assigned multiple IPs, extra routes, etc). Try editing your connection in Viscosity, and under the General tab un-tick the "Enable DHCP" checkbox.
I'd also recommend you try increasing the route delay incase they are being added before the TAP network interface is fully setup. Please see this post for instructions.
Finally, you may like to try disabling Viscosity's DNS support to see if it could be interfering. To do this, edit your connection in Viscosity, un-tick the "Enable DNS Support" checkbox, and then click Save.
I know the moderators here won't like this post, sorryWell only as we want Viscosity to be the best OpenVPN client out there for every user! Obviously if it is not working for you it means it isn't achieving that aim!
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
It seems to work after unticking the DHCP option ..... i am now able to connect to my home VPN .... on Friday i'll be at work and i could test viscosity to connect remote sites over LAN with a lot of route pushed by the VPN server and some inserted by the client itself.
Thank you for the trick James ....
Stay tuned ....
Bye !!
Fred
Thank you for the trick James ....
Stay tuned ....
Bye !!
Fred
Although I'm 100% sure my issue isn't related to DHCP i decided to post here instead of starting a new thread, because my issue is a Snow Leopard Issue.
I'm having the exact same console messages (also in 10.6), except i'm using tun on the server, but it doesn't with a university tap server i have either. The exact same settings, for both connections, work on another mac (also on 10.6), and at one point i also got a message that the tun startup item in /Library/StartupItems didn't have the correct security permissions.
Also worth mentioning, it works on a machine running the 64-bit kernel, this machine runs the 32-bit kernel, though.
* So I have 2 questions, is there an uninstall script?
* Could you give me a list of things to remove if i were to do a complete reinstall of viscosity?
Other than that, here's a paste of my console log. First the tun server. (I obscured the IPs). Keep up the good work guys, viscosity has been recommended and adopted by all my IT friends, and colleagues, it also makes a great Christmas gift at $9
I'm having the exact same console messages (also in 10.6), except i'm using tun on the server, but it doesn't with a university tap server i have either. The exact same settings, for both connections, work on another mac (also on 10.6), and at one point i also got a message that the tun startup item in /Library/StartupItems didn't have the correct security permissions.
Also worth mentioning, it works on a machine running the 64-bit kernel, this machine runs the 32-bit kernel, though.
* So I have 2 questions, is there an uninstall script?
* Could you give me a list of things to remove if i were to do a complete reinstall of viscosity?
Other than that, here's a paste of my console log. First the tun server. (I obscured the IPs). Keep up the good work guys, viscosity has been recommended and adopted by all my IT friends, and colleagues, it also makes a great Christmas gift at $9
Code: Select all
The tap server. (also obscured the ips)
17.9.09 13:53:59 openvpn[489] OpenVPN 2.1_rc15 i386-apple-darwin9.6.0 [SSL] [LZO2] built on Jan 6 2009
17.9.09 13:54:00 openvpn[490] WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
17.9.09 13:54:00 openvpn[490] NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
17.9.09 13:54:00 openvpn[490] LZO compression initialized
17.9.09 13:54:00 openvpn[490] UDPv4 link local: [undef]
17.9.09 13:54:00 openvpn[490] UDPv4 link remote: 66.xxx.xxx.xxx:1194
17.9.09 13:54:03 openvpn[490] [server] Peer Connection Initiated with 66.xxx.xxx.xxx:1194
17.9.09 13:54:05 openvpn[490] TUN/TAP device /dev/tun0 opened
17.9.09 13:54:05 openvpn[490] /sbin/ifconfig tun0 delete
17.9.09 13:54:05 openvpn[490] NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
17.9.09 13:54:05 openvpn[490] /sbin/ifconfig tun0 10.yyy.yyy.6 10.yyy.yyy.5 mtu 1500 netmask 255.255.255.255 up
17.9.09 13:54:05 openvpn[490] /Applications/Viscosity.app/Contents/Resources/dnsupalt.py tun0 1500 1542 10.yyy.yyy.6 10.yyy.yyy.5 init
17.9.09 13:54:05 openvpn[490] script failed: external program exited with error status: 1
17.9.09 13:54:05 openvpn[490] Exiting
17.9.09 13:54:05 Viscosity[259] *** __NSAutoreleaseNoPool(): Object 0x40e3a00 of class NSCFString autoreleased with no pool in place - just leaking
Code: Select all
17.9.09 13:57:23 openvpn[513] OpenVPN 2.1_rc15 i386-apple-darwin9.6.0 [SSL] [LZO2] built on Jan 6 2009
17.9.09 13:57:24 /Applications/Viscosity.app/Contents/MacOS/Viscosity[259] -[Keychain internetServer:forAccount:port:path:inSecurityDomain:protocol:auth:]:1670: Unable to find internet keychain item, error errSecItemNotFound (#-25300) - The item cannot be found.
17.9.09 13:57:24 [0x0-0x16016].com.viscosityvpn.Viscosity[259] /Applications/Viscosity.app/Contents/Resources/UserpassWinController.py:35: UninitializedDeallocWarning: leaking an uninitialized object of type NSApplication
17.9.09 13:57:33 openvpn[514] WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
17.9.09 13:57:33 openvpn[514] NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
17.9.09 13:57:33 openvpn[514] LZO compression initialized
17.9.09 13:57:33 openvpn[514] UDPv4 link local (bound): [undef]:1194
17.9.09 13:57:33 openvpn[514] UDPv4 link remote: 193.yyy.yyy.yyy:1196
17.9.09 13:57:35 openvpn[514] WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
17.9.09 13:57:35 openvpn[514] [openvpn1.tubit.tu-berlin.de] Peer Connection Initiated with 193.yyy.yyy.yyy:1196
17.9.09 13:57:36 openvpn[514] TUN/TAP device /dev/tap0 opened
17.9.09 13:57:36 openvpn[514] /sbin/ifconfig tap0 delete
17.9.09 13:57:36 openvpn[514] NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
17.9.09 13:57:36 openvpn[514] /sbin/ifconfig tap0 130.xxx.xxx.xxx netmask 255.255.254.0 mtu 1500 up
17.9.09 13:57:36 openvpn[514] /Applications/Viscosity.app/Contents/Resources/dnsupalt.py tap0 1500 1574 130.xxx.xxx.xxx 255.255.254.0 init
17.9.09 13:57:36 openvpn[514] script failed: external program exited with error status: 1
17.9.09 13:57:36 openvpn[514] Exiting
Hi russo017,
It looks like you have solved this in your other thread, however basically the latest beta version should solve the problem, which you can download here.
Cheers,
James
It looks like you have solved this in your other thread, however basically the latest beta version should solve the problem, which you can download here.
Could you give me a list of things to remove if i were to do a complete reinstall of viscosity?A list of files can be found here. However the latest beta version will prompt you to upgrade your TUN/TAP drivers if the old version is found, and automatically uninstall them. The new drivers are now bundled inside Viscosity, rather than installed into the Extensions/StartupItems directories.
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
10 posts
Page 1 of 1