3 ms·
I'm not sure I've ever seen screen add latency. (And yes, I do regularly use mosh to deal with packet loss over a 3G/4G connection; that's its primary value fo
by geofft 14y ago
I'm not sure I've ever seen screen add latency.
(And yes, I do regularly use mosh to deal with packet loss over a 3G/4G connection; that's its primary value for me.)
"Pervasive modern firewalls" is an anecdote. Even at cafes and such, mosh works, anecdotally, for me.
- jspthrowaway2 14y agoIn theory, screen will absolutely add latency because it's another indirection terminal (your input has to traverse SSH, then SSH's terminal, then screen's terminal, then your process, then back). Again in theory, that addition should be fairly small on the surface. In practice, and merely anecdotally on my part, I can attest that screen "feels" slower than a shell when I'm using it via SSH.
- TheAmazingIdiot 14y agoToo bad Mosh cannot work with X display redirects. That one would have been rather handy.
- geofft 14y agoThe X protocol is not particularly well-designed for this. (The X protocol is not particularly well-designed for lots of things.) One of mosh's advantages is that it does screen rendering on the server, and then synchronizes the screen with the client. So, if there's been ten screenfuls of outputs, and those packets were lost or delayed or the connection couldn't keep up, the client only needs to receive what's currently on the screen. (This doesn't work in the other direction, but there's typically a lot less traffic in that direction.) You can't quite do that with X, since the X protocol itself involves no way to get / diff / synchronize the contents of the screen -- it involves a bunch of rendering operations, so if there's a delay, it needs to re-send those operations. Still, there's an open ticket: https://github.com/keithw/mosh/issues/41 https://github.com/keithw/mosh/issues/41
- cbhl 14y agoI would consider you to be very lucky to have not run into a firewall that auto-blocks all UDP. Both my high school and my first employer blocked UDP altogether. (The former went as far as only white-listing outbound TCP connections on ports 21, 80, and 443, with ports on the latter two being transparently redirected through a very restrictive filter.)
- Nullabillity 14y agoFunny, my school's network is very restrictive about TCP (out of the ports I've tested only 80 and 443 have worked properly), but it doesn't do any deeper filtering, and has no restrictions at all for UDP.
- vidarh 14y ago> "Pervasive modern firewalls" is an anecdote. Even at cafes and such, mosh works, anecdotally, for me. We have a firewall rule set up to allow inbound ssh on port 443 to one of our office servers because several of our clients have networks that are so locked down that whenever one of us needs to work from their offices from time to time, it's the easiest way of ensuring they'll have ssh access... Cafe's are not a good example. Cafe-run public wifi tends to be some of the least secured internet access you can find.