Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi all
ssh is slowed down by ISP therefor socks proxy is slowed down
is there any work around?
if i could do absolutely nothing at all, could i build ssh from source and change it somehow to make it unrecognizable by ISP servers? i mean manipulating both ssh on client and ssh on my server?
by the way, changing the port ssh connected to from 22 to 9999 did not help
how do they actually realize when i'm using ssh to slow it down? it's supposed to be encrypted! ssl (https) is not slow at all, just ssh
someone told me maybe they are sniffing each packet's header sent through network, too see which is ssh, could this be?
loolooyyyy,
I don't know why you assume that your ISP is pouring molasses in your tunnel. It's more likely that the combination of low throughput and encryption overhead is slowing things down. Do a "man ssh" to read about the options. In particular, the man page describes the compression option and the cipher option. You can experiment with the following.
This command says, "use gzip compression with the Blowfish cipher, and dump debug info to the screen". From the man page: "Compression is desirable on modem lines and other slow connections, but will only slow down things on fast networks."
Code:
[user@host1 ~]$ ssh -vv -C -c blowfish user@host2
This command says "use the Blowfish cipher and dump debug info to the screen". Again, from the man page: "blowfish is a fast block cipher; it appears very secure and is much faster than 3des." Some people have noticed a measurable performance improvement after switching to Blowfish encryption from triple DES or AES.
dear agenbuzz
i'm assuming that because government has ordered all the ISPs to do so,
they actually made it impossible to use VPN ( except sstp which i couldnt get it working on linux), dont know how, does it use a particular port? if so, they have probably closed the port
but i'll try blowfish, i used compression without any luck before
ssh over https seems interesting,
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.