You are not logged in.
Hi everyone,
I just thought that it was time to give mosh a try.
I installed community/mosh 1.3.2-1 on my server and 1.2.5-2 on my client (Mint). I then applied the following firewall rule on my server:
iptables -A INPUT -p udp -m multiport --dports 60000:61000 -m comment --comment "MOSH Ports" -j ACCEPT
When I then connect to my server using
mosh user@myserver
it seems to work: "ps" shows a running instance of mosh and the pkts and bytes - count for that new iptables rule grows by 1 package / ~100 bytes:
10:15 root@tango003:~# ps wwaux | grep mosh
root 16572 0.7 0.0 52552 5240 ? S 10:15 0:00 mosh-server new -c 8 -s -l LANG=de_DE.UTF-8 -l LANGUAGE=
root 16594 0.0 0.0 13192 2228 pts/8 S+ 10:15 0:00 grep --colour=auto mosh
10:15 root@tango003:~# iptables -L -v -n | grep -i mosh
3 297 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 multiport dports 60000:61000 /* MOSH Ports */
10:22 root@tango003:/etc/ssh#
So far so good.
But also, I notice the following things:
When I type, I do not see any of mosh's promises like "no delay due to local echo" kept; even I have quite a good line, I can notice a delay for the echo of typed characters when hitting the keys fast. Also, I do not see that "server has acknowledged receiving" - bold from mosh's demo video.
The Firewall counter does not grow after the initial connection anymore. I would have expected to have it grown ongoing while I utilize the mosh connection.
Does anybody have an idea why this is?
Last edited by DerJudge (2017-08-15 08:50:21)
Offline
Let me give answers here myself:
mosh's UDP ports seem to not be utilized for all data but only for synchronisation in some situations, when the line was gone to re-establish the connection and to exchange the diffs.
The reason I did not see those underlined characters on delay is that my line quality was just too good As soon as I disconnect and continue typing, I see that I indeed deal with an predictive local echo and that I am missing some server confirmations and see underlined characters.
Offline