xshell5 compression doesn't work [4]
xshell5 compression doesn't work
Tuesday, March 21, 2017 4:58 PM - koalaftw
Hello,
Because i'm using 3D apps via X11 forwarding, i need the ssh compression (400 mbps to 15 mbps in this case with putty), the problem is that even if the compression button is checked in xshell (screen in attachments), the compression doesn't work and in the xshell log, it says "compression: none".
Is there another option for enabling compression ?
Is this a bug ?
Thanks in advance.
Program Ver. : Xshell 5
Because i'm using 3D apps via X11 forwarding, i need the ssh compression (400 mbps to 15 mbps in this case with putty), the problem is that even if the compression button is checked in xshell (screen in attachments), the compression doesn't work and in the xshell log, it says "compression: none".
Is there another option for enabling compression ?
Is this a bug ?
Thanks in advance.
Program Ver. : Xshell 5
Re: xshell5 compression doesn't work
Monday, March 27, 2017 7:13 PM - Support
Re: xshell5 compression doesn't work
Tuesday, March 28, 2017 4:42 PM - koalaftw
Hello,
Thanks for your tips, it works. However, modify the sshd_config wasn't required by others ssh clients (ssh compression worked just by enabling the checkbox on the client side), how do you explain this ?
Thanks for your tips, it works. However, modify the sshd_config wasn't required by others ssh clients (ssh compression worked just by enabling the checkbox on the client side), how do you explain this ?
Re: xshell5 compression doesn't work
Wednesday, March 29, 2017 10:37 PM - Support
In light of your issue, we've discussed internally about how Xshell should behave when the ssh server is set to delayed compression. We've come to the conclusion that our current behavior is incorrect and the behavior you desire is the right way to go.
We're conducting a few tests and barring any major setbacks, the "correct" behavior should be rolled out with the next build release.
Thanks!
Technical Support
Like us on Facebook
Follow us on Twitter
Visit our blog Blog
We're conducting a few tests and barring any major setbacks, the "correct" behavior should be rolled out with the next build release.
Thanks!
Technical Support
Like us on Facebook
Follow us on Twitter
Visit our blog Blog
Previous views: 834