So, I've been trying to work from a really flaky hotel net, and getting constantly dropped or badly lagged. Mosh (http://mosh.mit.edu) looks like it would be a really good solution for this. The basic authentication story is that it uses ssh for bootstrapping, and then each session starts up a UDP speaking daemon authenticated with a one time private key (communicated to the client via the ssh bootstrap). Details are here: http://mosh.mit.edu/#faq At the same time, since most of my connections are made via [np]amby, I wanted to query the group before starting to use this on one of our admin bastions. As a side note, this would also potentially require UDP conduits. Opinions? -nld
On Fri, Apr 05, 2013 at 12:32:47AM -0500, Narayan Desai wrote:
So, I've been trying to work from a really flaky hotel net, and getting constantly dropped or badly lagged.
Mosh (http://mosh.mit.edu) looks like it would be a really good solution for this.
That looks really cool. I'd say give it a try; main issue would be if UDP gets blocked at the Lab's border, as there's been some talk of doing, but I don't think that's being done yet. Don't know the source of the flakiness, but for hotel (and auto mechanic...) networks I've been on in the past with really short DHCP lease times, simply running a continuous ping (sending out a packet every, say 10s) has been enough to keep my network connections alive. John
The flakiness was mainly the 1-20% packet loss. ;) mosh is pretty excellent. I've already tried it out in less sensitive environments. There is a good talk from usenix FCW last week about it as well. Its approach is really different from other remote shells. -nld On Apr 5, 2013, at 3:15 AM, John Valdes wrote:
On Fri, Apr 05, 2013 at 12:32:47AM -0500, Narayan Desai wrote:
So, I've been trying to work from a really flaky hotel net, and getting constantly dropped or badly lagged.
Mosh (http://mosh.mit.edu) looks like it would be a really good solution for this.
That looks really cool. I'd say give it a try; main issue would be if UDP gets blocked at the Lab's border, as there's been some talk of doing, but I don't think that's being done yet.
Don't know the source of the flakiness, but for hotel (and auto mechanic...) networks I've been on in the past with really short DHCP lease times, simply running a continuous ping (sending out a packet every, say 10s) has been enough to keep my network connections alive.
John
As far as I can tell, once you have setup a session you basically have a passphrase-less key on your workstation. I'm a little uncomfortable with no timeout on the key, using the bastions. Our network policies currently allow high port udp through. I don't have a problem with you running this directly on the machines you're trying to reach through the bastions. You should be able to setup a connection without ssh following the "Q: How do I run the mosh client and server separately?" in the FAQ. ----- Original Message -----
From: "Narayan Desai" <[email protected]> To: "[email protected] Admins" <[email protected]> Sent: Thursday, April 4, 2013 10:32:47 PM Subject: mosh
So, I've been trying to work from a really flaky hotel net, and getting constantly dropped or badly lagged.
Mosh ( http://mosh.mit.edu ) looks like it would be a really good solution for this. The basic authentication story is that it uses ssh for bootstrapping, and then each session starts up a UDP speaking daemon authenticated with a one time private key (communicated to the client via the ssh bootstrap). Details are here: http://mosh.mit.edu/#faq
At the same time, since most of my connections are made via [np]amby, I wanted to query the group before starting to use this on one of our admin bastions.
As a side note, this would also potentially require UDP conduits.
Opinions? -nld
Yeah, not comfortable with this on namby or pamby. Dan Olson <[email protected]> wrote:
As far as I can tell, once you have setup a session you basically have a passphrase-less key on your workstation. I'm a little uncomfortable with no timeout on the key, using the bastions.
Our network policies currently allow high port udp through.
I don't have a problem with you running this directly on the machines you're trying to reach through the bastions. You should be able to setup a connection without ssh following the "Q: How do I run the mosh client and server separately?" in the FAQ.
----- Original Message -----
From: "Narayan Desai" <[email protected]> To: "[email protected] Admins" <[email protected]> Sent: Thursday, April 4, 2013 10:32:47 PM Subject: mosh
So, I've been trying to work from a really flaky hotel net, and getting constantly dropped or badly lagged.
Mosh ( http://mosh.mit.edu ) looks like it would be a really good solution for this. The basic authentication story is that it uses ssh for bootstrapping, and then each session starts up a UDP speaking daemon authenticated with a one time private key (communicated to the client via the ssh bootstrap). Details are here: http://mosh.mit.edu/#faq
At the same time, since most of my connections are made via [np]amby, I wanted to query the group before starting to use this on one of our admin bastions.
As a side note, this would also potentially require UDP conduits.
Opinions? -nld
-- Craig
participants (4)
-
Craig Stacey -
Dan Olson -
John Valdes -
Narayan Desai