Add Mosh

[geoffreyd]

http://mosh.mit.edu/

Mosh makes remote logins much more robust and reliable, with support for changing IP's, reduces lag (by intelligently updating the local screen immediately).

Build instructions: http://mosh.mit.edu/#build-instructions

While it is possible to install mosh server into a users home directory, it is easier to use, if it's installed in a system path.

[petejkim]

AFAIK right now mosh works on Nitrous.IO boxes only through SSH tunnels. Were you able to get it working?

[gerbal]

👍 to this. I do a lot of remoting into my nitrous box on crappy connections. mosh installed at a system level would make my life easier.

[jeffjewiss]

I'm also very interested in having mosh added.

I tried to set it up locally as an autoparts package, but I couldn't configure protoc/protobuf properly so it failed to compile.

Would it be possible to get some help debugging this so it could be added as a package?

[gerbal]

I was able to get Mosh compiled and running, but I wasn't able to connect to the mosh instance on Nitrous box. I ran into problems with Mosh needing to open UDP ports to talk back to my client, something Nitrous is not configured for.

[ghost]

I have complied the mosh on user path.But cannot login from juicessh "mosh" type. How to solve ?

[ghost]

Mosh is a great tool.I have installed mosh and mosh-server on nitrous.io. But when i connect from my pc to nitrous.io .

mosh did not make a successful connection to 54.215.6.163:60001.
Please verify that UDP port 60001 is not firewalled and can reach the server.

(By default, mosh uses a UDP port between 60000 and 61000. The -p option
selects a specific UDP port number.)

[mosh is exiting.]

[gerbal]

It looks like Nitrous restricts udp ports being exposed to the outside world. sudoer privileges seem to be required to open up a udp port. We likely need Nitrous.io engineer intervention to progress Mosh support further.

[acook]

I'd also like to see Mosh support. Mosh over SSH is not nearly as useful.

[marcinwyszynski]

+1