The sys admin's daily grind: Mosh

Shell on the Beach

Article from Issue 156/2013
Author(s):

Dangling your legs in the sea while enjoying the Mediterranean sunshine can affect the prospect of a good Internet connection; fortunately, Charly knows what to do.

I am writing this column on the Costa Brava and currently dangling my feet in the Med. This stretch of coast is aptly named; "brava" can be translated as "wild, inhospitable." Unfortunately, this description also applies to Internet coverage beyond the tourist beaches – although WiFi is ubiquitous in hotels, campsites, and bars. At the moment, I'm using a network operated by the "Xiringuito" beach bar near the picturesque ruins of the ancient Greek trading exclave of Empúries, and the connection is pretty brava.

This situation is not going to spoil the sunny afternoon for me, however, because I still have Mosh [1] stashed away as an ace in my beach bag. The SSH replacement consists of a client component and a server component along with a wrapper script. Initially, Mosh connects the client and server via SSH on port 22 in the normal way. Then, the server hands the client a key, with which it identifies itself henceforth, and Mosh drops the TCP connection.

At this point, the client and server talk only on UDP, using a port in the range between 60000 and 61000 by default. I can use the --port=<Portnumber> parameter to force Mosh to prefer a specific port. UDP connections are very robust; they even survive client suspend phases.

What's even better is that, because the client uses the key initially received from the server to identify itself, it can even switch IP addresses. So, if the beach cafe network collapses and I swap to smartphone tethering, my Mosh session continues unfazed, and my seaside reverie is undisturbed.

Token of Appreciation

If the only available connection is unstable, this can lead to the known issue that SSH does not show you what you typed at the terminal until the TCP connection recovers. Although Mosh can't work miracles in this case, it is clever enough to guess what the terminal should be displaying, and it sends the characters for output just in case. Synchronization via UDP continues to run in the background. Thanks to Mosh's predictive mechanism, working at the command line is a much smoother experience for me than using SSH.

Mosh also doesn't leave you in the dark about what has actually been transferred and what bytes are just predicted: The characters that the Mobile Shell predicts are underlined (Figure 1). So, if I only want to see the whole truth, I can disable the prediction function by issuing --predict=never. Equally, I can force prediction using --predict=always. The default behavior is a compromise: Mosh measures the latency of UDP connection in the background and switches on the predictive function if the connection quality deteriorates.

Figure 1: Mosh underlines characters that have not been transmitted because of a poor connection.

Mosh has become indispensable for me on the road. It cannot completely replace SSH, because it currently does not support X11 or port forwarding and only speaks IPv4. However, the developers are working on IPv6 as well as on an app for Android mobile phones, which is due for release on some other sunny day.

Infos

  1. Mosh: http://mosh.mit.edu

The Author

Charly Kühnast is a Unix operating system administrator at the Data Center in Moers, Germany. His tasks include firewall and DMZ security and availability. He divides his leisure time into hot, wet, and eastern sectors, where he enjoys cooking, freshwater aquariums, and learning Japanese, respectively.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

SINGLE ISSUES
 
SUBSCRIPTIONS
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Mosh and AutoSSH

    SSH can make you crazy if the WLAN connection keeps breaking down, the IP address changes, or the data packets trickle over a slow mobile connection. AutoSSH and Mosh offer some features you won’t find in ordinary SSH.

  • Mosh: Shell for Users on the Move
  • Charly's Column: UFW

    Things were better back then. No way! Charly takes a look back at the bad old firewall days and explains why things are better today – assuming you have the right tools.

  • Muon/Snowflake

    Muon/Snowflake lets you manage SSH access via an easy-to-use GUI with a wealth of useful functions.

  • Charly's Column: Trickle

    If your data traffic suffers from congestion at times, don't worry. Now you can shoot down programs that are heavy on traffic to free up the inflow and outflow.

comments powered by Disqus
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters

Support Our Work

Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

Learn More

News