October 21, 2009
Solid list of enhancements, mostly related to tunnel auto-reconnection, but also some better handling of tunnel problems and a couple bug fixes from the previous beta.
http://codesorcery.net/downloads/Meerkat_1.3b2.zip
Full change list:
- Enhancement: Certain tunnel errors will be marked as fatal and will disable automatic retry.
- Enhancement: Let the user know when a password or other authentication problem is at fault.
- Enhancement: If a password fails, remove it from the keychain before prompting for it again.
- Enhancement: Allow copying of SSH output to the clipboard if there is a fatal tunnel error.
- Enhancement: Provide quick link to support forums if there is a fatal tunnel error and the output is copied to the clipboard.
- Enhancement: Let the user know if retries were made, and how many, if there is eventually an error.
- Enhancement: Added a helper tooltip window as a guide to tunnel checkbox states.
- Enhancement: Automatically retry tunnels only if online.
- Fix: Tunnels now sortable by active status again.
- Fix: App triggers caused a save error when trigger apps were launched.
October 23, 2009
#1
A few bugs I've
A few bugs I've noticed:
- When starting Meerkat using the NetworkLocation plugin the Meerkat icon starts the "..." as if it were connecting. No tunnels are registered as active, however. Seems the plugin doesn't work.
- Probably related but NetworkLocation doesn't stop Meerkat tunnels when switching locations even if the option is selected.
- Meerkat asks if an app triggered tunnel should be started when modifying the tunnel settings. Meerkat does not check if a trigger application is running on startup however. It should do this for cases where Meerkat has crashed.
Additionally (separate from NetworkLocation) I think Meerkat should have the option for each tunnel to disable the tunnel after a network state change and/or system location change. The auto-retry feature is great but some tunnels I don't want to keep trying to connect.
October 27, 2009
#3
I use Meerkat every day at
I use Meerkat every day at work (via NetworkLocation) to connect to the Internet (via another machine) and my home machine for streaming iTunes. I end up using most of the features regularly. That and the fact I've worked at a Mac software developer for 13 years now means I've gotten pretty good at testing. :-)
While I'm at it I have a couple long-standing annoyances: I have noticed that Meerkat always indicates the tunnel is up (showing a number not the "...") before Internet access works (via the SOCKS5 proxy). I haven't taken the time to isolate exactly what's happening but my guess is the DNS servers aren't not resolving because Safari reports that it couldn't find "www.google.com". It usually takes 30-60 seconds for this to clear up. I suspect this isn't fixable on your end but I'd love an option to "verify DNS resolution" before marking the tunnel as up.
Also I notice you start the Bonjour advertisement for iTunes as soon as the tunnel starts trying to connect rather than once it has connected. This has confused me a few times when I click on the "Shared" link in iTunes and it hasn't worked.
These are nitpicks since they don't hurt the functionality of Meerkat but I thought I'd mention them in case you have some extra time. Either way, thanks for all the hard work Justin!
December 1, 2009
#4
Would you mind giving this
Would you mind giving this version of the plugin a try? I think it's got those issues covered.
http://codesorcery.net/downloads/Meerkat%20NL%20Plugin%201.1.zip
March 2, 2010
#5
Justin,
I had a chance to
Justin,
I had a chance to test this updated version and confirmed it does work correctly with the latest Meerkat.
Want to join the forums? Create an account or login.
Thanks for these reports. You're a great beta tester!
I have not tried the betas with the NL plugin yet. I'll get on that.
With regards to bringing up a tunnel on launch if the trigger is running, that's a great idea.
And finally, that's good input on the auto-retry, too.