Vittorio is right. Some seconds I got with disabling testing all my public keys. I tried add dns to /etc/hosts, but no gain.
It waits where Vittorio wrote. I searched for disabling ciphers but didnt found anything. Probably it cannot be done. -- S pozdravom Jakub Janco 2015-09-08 18:00 GMT+02:00 Vittorio G (VittGam) <open...@vittgam.net>: > Il 08.09.2015 17:42 Brent Thomson ha scritto: >> >> Slowness probably depends on hardware as well as all the possibilities >> listed by others. I have a model of router that always takes 2-3 >> seconds to initiate an SSH connection, just to set up encryption >> (brief, but computationally intensive; happens with every connection). >> 10 seconds seems really slow, though. Smells like DNS. > > > It might not be DNS in fact. On AR9331 (MIPS 24k CPU, not that fast...) > starting from Barrier Breaker SSH is pretty slow (3-4 seconds), so on > slower routers the login time can be longer. > > If you login with ssh -v, you can see that it waits between > >> debug1: expecting SSH2_MSG_KEXDH_REPLY > > > and > >> debug1: Server host key: RSA [...] > > > If you check the CPU usage on the router while the client is waiting for > the reply, you can see that dropbear is at 100%. > > Cheers, > Vittorio > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
