Tunnelblick and Mountain Lion clearly doesn’t work for me. Don’t get me wrong: I always prefer open source software, but it does have to work. I just wanted to compare and see if it has the same issues. So I thought it’d be wise to look for an alternative, and I came across Viscosity. It kept me from working effectively. If somebody knows what to do to get this working properly, let me know! Sorry guys □ Connections to public hosts are fine by the way I wasn’t really able to pinpoint this issue. I’d already blamed the guys in the office for heavy downloading only to discover it was Tunnelblick that was the problem. Problem two is more annoying: the connection is not stable, it’s slow and when working in a shell it is annoying to wait for the cursor to move. I thought there’d be an update soon enough that’d solve this.Ģ. I’ve then to manually restore the right DNS servers. What goes wrong more often is the opposite: when disconnecting the connection, the OpenVPN advertised DNS server is still being used but since we’re disconnected, it doesn’t resolve anymore and so nothing works. This happened a few times last week, although most of the time it works ok. This is annoying: while connected to the vpn, hosts behind it do not resolve because the DNS server advertised by the OpenVPN server is not being used. I’ve seen /etc/nf with the right content, but still the old DNS servers were used by Mountain Lion. DNS servers do not always get set properly, it feels unstable to me. But after a week working with it, I’m not too happy how it works right now. The two issues I have are:ġ. I managed to get things to work using the latest Tunnelblick beta. Last week I wrote a small blog about OpenVPN on OSX Mountain Lion using Tunnelblick.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |