![]() It looks ok, but you cannot directly press ‘}’ on most keyboards It’s SHIFT+], so this makes the default shortcut CMD+SHIFT+]. In Terminal you can see the default shortcuts for this in the menu: I forgot how easy this can be done in OSX, so I’ll describe it below so others can benefit as well.įor example, I want the shortcuts in Terminal for Next and Previous tab to be CMD+right arrow, and CMD+left arrow. The downside is that all customisations I did over the past years are also gone. The good thing is that everything is now fast and clean. I decided to install from scratch instead of migrating or cloning the old disk. I’ve upgraded my 3 year old MBP with a fast SSD. Then I bought Viscosity that just works and has been stable from the start. Update: I did go back to Tunnelblick a few times but had no lock and didn’t want to spend more time on it. Otherwise Viscosity probably has a lot of new users to welcome in the coming months. I hope Tunnelblick is able to sort out what goes wrong with Mountain Lion. Since I have 30 days to try Viscosity, I’ll soon enough know □įor me this is a fast en good solution. It’s a bit early to tell if that is gone for good. Also, I haven’t seen the slow connection issue. Just like when I was running Tunnelblick on Lion. It uses the OpenVPN specified DNS servers while connected, and the DHCP specified DNS servers while disconnected. I tried connecting, disconnecting and all but can’t find any problem. I just works, a few seconds later I’m connected and. From the upper menu, you can now connect. ![]() What surprised me was that it has an import feature that imports from Tunnelblick. ![]() Viscosity is $9 for a license, that sounds ok to me.ĭownloading and installing is easy, like any other OSX app you open the dmg and drag the application to the application folder. 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 |