May 19, 2009
Just a quick note again of how useful I'd find it if meerkat would not use control masters. Since SSH uses an available control master port by default, and since you can't add tunnels to existing connections, failarity ensues unless I disable control masters and end all of my existing connections whenever I turn on tunnels.
It's a simple ssh option to fix, but of course I know it's never quite so simple to add options to interfaces. On the command line, it looks like this:
ssh -o "controlpath ~/.ssh/control-master/!socket" sitename
Where '!socket' is a unique filename per connection. This will bypass any existing control masters and open a new socket, and thus a new connection, saving the day.
Thanks,
Ben
May 19, 2009
#1
I've definitely still got
I've definitely still got this on my list. In 1.3, I plan on focusing on both the addition of custom SSH options, as well as combining tunnels on the same host into the same process. So I'm sure there will be some conflict to be worked out with regard to the control master option.
September 3, 2009
#2
Just to followup,
Just to followup, ControlMaster support is disabled automatically in Meerkat as of 1.2.2. So you can keep any ControlMaster configs that you have for non-tunnel SSH use and Meerkat will ignore them.
Want to join the forums? Create an account or login.
