From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: RE: [Cerowrt-devel] reproducing network research results with mosh
Date: Fri, 22 Mar 2013 09:35:23 -0400 (EDT) [thread overview]
Message-ID: <1363959323.942511859@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw5jEfjG5K+C0-AZK3dLOo1rUS7dfbJEZKQVsqepS27Vbg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
Just curious... have you run RRUL-style testing of mosh over a congested link? Not knowing in what way mosh is "UDP-based" I wonder what happens to it when you run a program like, say, "top", over mosh when there is heavy file transfer load.
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Friday, March 22, 2013 9:27am
To: "bloat" <bloat@lists.bufferbloat.net>, "bloat-devel" <bloat-devel@lists.bufferbloat.net>, cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] reproducing network research results with mosh
http://reproducingnetworkresearch.wordpress.com/2013/03/14/mosh-cs244-13/
I embraced mosh wholeheartedly about a year ago. I've been installing
it everywhere I go, with much of the same enthusiasm I had for putting
mosaic on everything back in the early 90s.
As a ssh replacement for interactive traffic, mosh is of tremendous
use, particularly in the case where machines are suspended/resumed,
move access points, or are experiencing wildly variable latency and/or
long RTTs.
It's now available across most unix OSes, and often installable via
the standard package manager.
http://mosh.mit.edu/
Try it!
It would be awesome if this tech could make it into a generation of
command line interfaces for embedded gear like routers and switches.
However at the moment the server code requires C++ and libstd++, which
makes it overlarge for the lowest end of gear.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 2120 bytes --]
next prev parent reply other threads:[~2013-03-22 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 13:27 Dave Taht
2013-03-22 13:35 ` dpreed [this message]
2013-03-22 13:51 ` [Cerowrt-devel] " Dave Taht
2013-03-22 13:58 ` [Bloat] " Mikael Abrahamsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1363959323.942511859@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox