Viscosity vs tunnelblick for mac os x#
Viscosity vs tunnelblick free#
Viscosity vs tunnelblick mac#
Viscosity vs tunnelblick windows#

My OpenVPN server config (sanitized for general consumption):Ĭlient-config-dir ccd # my client ccd file is currently empty My Viscosity config (client side, sanitized for general consumption): I've even tried providing absolute paths to the script, even placing it in /private/tmp so anything should be able to read it- nothing).Īny suggestions? By the way, I've tried this with both Viscosity 1.0.3 and the 1.0.4Beta I found posted on the forums. a standard script, made executable, owned and setuid to root, containing a few route commands as I'd type on the command-line (I would settle for this- even if I had to invoke some sort of 'sleep and background' to allow the VPN connection to finish then having these routes conveniently apply but I haven't had success in getting this to work with Viscosity yet. running a script via the 'up' command placed in the Advanced tab- to my detriment, I can't seem to get this to run. pushing the route from a 'client-config-dir' file for my connection (still no-go- I think I run into issues with tap0 not being ready, and the openvpn backend to Viscosity seems to apply the route before the route-delay is able to kick in).

introducing a 'route-delay #' (I've tried varying values, from 2-30) to see if it was an issue with the tap0 interface not being online in time (apparently not the case).

But having to manually run some commands external of Viscosity seems to detract from the conveniences that it offers- it would be nice if Viscosity could handle the entire process. With some experimentation, I notice that if I manually add the routes after the connection takes place, the routes are bound to the correct interface and I can ping successfully. But alas, Apple seems intent at times to cripple the underlying UNIX functionality of the system in strange and mysterious ways.

If Apple hadn't removed brconfig/bridging support from the system, I would have bound my local tap0 interface to en0 and been done with it. My problem with Viscosity: I can configure the routes in Preferences -> Networking:Īnd when I connect, I see in the Viscosity log that it does apply those routes, but the problem is, it binds them to my local ethernet interface (en0, the same one that is talking to my Linksys router), and NOT my VPN (tap0) interface. When on the network locally, all traffic routes as it is supposed to. The catch, however, is that this isn't the only network that exists here. I'm running a UDP'ed TAP connection and DHCP'ing an IP from this network (I bridged the tun0 interface on the server to the ethernet interface so DHCP can serve to the VPN clients).

Viscosity vs tunnelblick mac#

In the general case, this actually works fine- I can connect my Mac using Viscosity, and everything gets set up correctly- I can ping machines on the 10.80.1.x network. Linksys Router serving a DHCP'ed 192.168.12.x/24 network, my Mac (an iMac running OS X 10.5.6), DHCPs and talks out to the internet just fine. I've recently discovered Viscosity and would love to switch over to using it in place of TunnelBlick, but I am encountering an annoying routing issue that I can't seem to get resolved. Viscosity is an OpenVPN client for Mac, providing a rich Cocoa user interface for creating, editing, and controlling VPN connections.Hi. Viscosity 1.6.7 – Graphical user interface for OpenVPN.

Viscosity vs tunnelblick windows#

OpenVPN MI GUI is a Windows graphical user interface for the OpenVPN client management interface. It allows a user to connect to a VPN server and establish a VPN connection.

Viscosity vs tunnelblick for mac os x#

Viscosity is a VPN client for Mac OS X and Windows. (Might work with earlier versions, but this is not tested).

Viscosity vs tunnelblick free#

Free and open source Graphical User Interface for OpenVPN that offers quick and easy control of th.