You received this message because you are subscribed to a topic in the Google Groups "tunnelblick-discuss" group. Good luck to all of you, trying to resolve similar cases! Please if you see something, which is not right in the text above, feel free to correct me. Plus, Viscosity is available for both Mac and Windows, unlike Tunnelblick that only runs on Mac computers. Basically, it performs the same job, but it looks nicer. Leave the interface, protocol, and local port as default (WAN, UDP on IPv4 only, 1194). Tunnelblick vs Viscosity Viscosity is a paid alternative to Tunnelblick and it provides a rich user interface for creating, editing, and controlling VPN connections. would be nice to have the option to export its configuration similar to how Viscosity is currently supported. At the next step, give the OpenVPN server a description. OpenVPN Client Export support Tunnelblick. This holding time allowed my tap adapter to receive a proper network configuration from my DHCP server and from that point all other commands make sense. Give the certificate a name and like the last step, populate the location information if you’d like. You can try updating to the latest beta version of Viscosity which ships with OpenVPN 2.
If the server is configured to rely on a feature only in 2.5 it may be rejecting the connection attempt. When I introduced the –route-delay 10 command, I set a 10 seconds holding time, before the execution of –redirect-gateway and route-gateway commands. A possible difference is that you're likely using OpenVPN 2.5 with Tunnelblick, while Viscosity 1.9.x uses OpenVPN 2.4. Since my tap adapter didn’t have an IP address, the -route-gateway command was assigning the pre-defined gateway IP address to my Wi-Fi adapter. Because of that OpenVPN was just skipping the fact that my tap adapter doesn’t have any IP address and proceeding to routing table modification, but since there was nothing to route, the client was proceeding to the next command –route-gateway. The problem was that when I was using both redirect-gateway and route-gateway in my client configuration file, my tap adapter was not receiving any IP address from the DHCP server. In Tunnelblick my configuration works only with: Set nameserver (3.0b10) I’m not sure whether this had any effect on my configuration or not, but it’s good to know what I’ve done.
Just for reference, today I installed security update 2014-005 for OS X Mavericks and disabled ipv6 protocol by typing the following command in Bash: When you need to connect several devices to the VPN, a very convenient option is to set up the VPN on your router.
Also the final goal is to route all traffic via the VPN tunnel. PureVPN to get started with this VPN service, subscribe to the 7-day trial for 0.99, install the Mac app, open the App Settings tab, and select the L2TP protocol.
Please be aware, that this solution is valid only for Mac users, trying to connect to OpenVPN server, which is bridged with a DHCP server using tap interface and UDP protocol.