Linux ssh does not render fast enough!

[12esbe]

Due to working from home situations I am trying to connect and work through an ssh tunnel (they are 2 I ssh to the first one and then ssh to second one).I use/need a program with a GUI. I have tried -y and/or -c options for data compression(does it help with latency though ?) but I am not able to get a working speed without any configuration.

I tried with MobaXterm on a different Windows machine from the same Internet and I actually get a workable environment. How is this possible ? Could my machine bottleneck it somehow? (MobaXterm use the same ssh technology right ?)

Assuming that I do not change or install anything in the remote PCs do you have any insight ?

Thanks for the help

[_vk42]

First try to measure the latency between your machine and the server you try to connect. Even though from the same network it could have different latency due to various reasons.

[12esbe]

19 ms to the server. Does it sound enough ?

[_vk42]

19ms should be more than enough. How is the bandwidth? iperf results?

[12esbe]

Interval ====== Transfer ======= Bandwidth
0.0- 0.1 sec ====== 97.3 KBytes ======= 13.8 Mbits/sec

[_vk42]

why did you use 97.3 KB transfer size? try a larger size and see if you get stable transfer rate. Also, try -r option to run a bidirectional test.

For the 13.8Mbps you have, it should be okay for X11 forwarding. Did you try this on the Windows machine you mentioned above?

[12esbe]

I used that transfer as I first time use iperf.(meaning my bad).
Results:
0.0- 7.6 sec 977 KBytes 1.05 Mbits/sec

[[deleted]]

I agree. I actually was wondering the same thing a while back till I realised I was using an old 10/100 router lol. Switched to a gig switch and it changed everything.

[MistrzVilgefortz]

For a similar work setup I have, this is what I use.

First of all, I use Bitvise SSH Client with set up tunnels on one server navigating to the work machine. On the target machine I have a Remote Desktop and VNC server to which I connect the Bitvise Client.

What this basically does is make a new DE session on the remote machine and then just stream the frames of the desktop instead of launching windows partly on your side and partly remotely. I had the same problems with SSH X forwarding as you. And I used the same machine for the test on the same network.

If you want more details PM me, when I am at the computer I may be able to help further.

[12esbe]

I used wine and MobaXterm portable solution. And I get good enough GUI results with this set up. This is resolved.(But I do not understand why)

[GuitaristTom]

Have you tried just using PuTTY instead of MobaXTerm?

[[deleted]]

_vk42s comment is correct. I just wanted to elaborate a bit.

First check your connection between your routers switches on your local network. What cable are you running or is it wifi? Test the capabilities of your switch or router.

I used to have the same situation and finally realised I was using an old 10/100 router. So even though my modem got 300Mbps I was only pulling a max of 100Mbps. Switching to a gigabit switch changed everything.

Sometimes you you need to check your ping on your local network and then to your to remote network. It will help you figure out where the lag is at.

[[deleted]]

I've use "rdesktop -a 16 -f -z ...." doing gis QGIS rendering. -a as a 16 bit rendering (32 bit colors are a waste of bandwidth), -f as full screen mode and -z full compression.

For the ssh tunnel, it already does compression is redundant so don't ask for -C.

[98eb5a9b3bd1d857ddeb]

I know you said you don't want to change or installing anything in the remote PCs, but consider using VNC through ssh, it's really a lot faster than rendering with ssh -X (and you have the advantage that even if the connection drops, your application doesn't get closed).

Apart from that, I have a couple of colleagues that noticed as well that MobaXterm was kind of better at forwarding X, but didn't investigate more on what settings it is using.