Working in terminal (linux ssh) over bad internet

Question

linux

I have a very bad Internet at the moment: low speed, big delays. Approximately as through bad GPRS.

Sometimes the connection is lost for several minutes.

What can be done with the ssh client or server to make it more comfortable to work? Perhaps some kind of compression, timeouts or something else ... Perhaps mc has some settings on this topic? Now, if a command runs on the server for more than a few seconds, I don't see the result at all until I start typing something on the keyboard. Is there any way to tell the ssh client to try harder to get a response?

PING ya.ru (87.250.251.3) 56(84) bytes of data.
64 bytes from www.yandex.ru (87.250.251.3): icmp_req=1 ttl=47 time=548 ms
64 bytes from www.yandex.ru (87.250.251.3): icmp_req=2 ttl=47 time=537 ms
64 bytes from www.yandex.ru (87.250.251.3): icmp_req=3 ttl=47 time=886 ms

Answer 1

autossh+screen/tmux

Answer 2

You can try to abandon mc. Bash and readline are quite comfortable environments to work with. And they require much less bandwidth from the channel. Plus, in the end, you can feel the spirit of the Jedi, and generally work without a permanent ssh connection, running the necessary commands something like this: ssh abcd.xyz find /dev -iname '*tty*' | (grep 12 && echo BINGO).

Answer 3

use screen... it will be much more convenient when connection is lost

Answer 4

Compression can be enabled with ssh -C.
If nothing arrives until something is sent, then the problem is most likely not in ssh itself, but in TCP - if the packet is lost, then the retransmission itself occurs after a rather large timeout, but if something is pushed into the socket , it starts immediately. For some reason, this timer cannot be reduced via /proc/sys/net (the Internet suggests that “making TCP more aggressive is considered anti-social”), but you can rebuild the kernel, as the person did here .

Answer 5

Do you have bad internet???
Wow, it's considered normal here :)
[email protected]:~$ ping ya.ru
PING ya.ru (93.158.134.3) 56(84) bytes of data.
64 bytes from www.yandex.ru (93.158.134.3): icmp_seq=1 ttl=55 time=640 ms
64 bytes from www.yandex.ru (93.158.134.3): icmp_seq=2 ttl=55 time=639 ms
64 bytes from www.yandex.ru (93.158.134.3): icmp_seq=3 ttl=55 time=639 ms
64 bytes from www.yandex.ru (93.158.134.3): icmp_seq=4 ttl=55 time=646 ms
^C
- ya .ru ping statistics - 5 packets transmitted, 4 received, 20% packet loss, time 4004ms
rtt min/avg/max/mdev = 639.010/641.294/646.157/2.950 ms

Answer 6

Nothing will help, my traffic on ssh is less than 20 kilobits, what kind of compression is there, the screenshots save a little but also not ice, if there is a skylink, you can sit on it there is more or less some kind of stability.