From owner-freebsd-current@freebsd.org Fri May 19 02:28:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48457D74C53 for ; Fri, 19 May 2017 02:28:24 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 286CDF28 for ; Fri, 19 May 2017 02:28:24 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (125-209-146-2.dyn.iinet.net.au [125.209.146.2]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v4J2SJ6i069517 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 18 May 2017 19:28:22 -0700 (PDT) (envelope-from julian@freebsd.org) To: freebsd-current From: Julian Elischer Subject: Ssh.. can we please have HPN back? Message-ID: <65e88d85-ca38-26dc-fe0a-910db11d470b@freebsd.org> Date: Fri, 19 May 2017 10:28:13 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2017 02:28:24 -0000 So after stripping out the HPN version of ssh from our product becasue "it was no longer needed" we dicovered that we were premature in doing so. Apparently ssh still really needs HPN to get any throughput at all when there are latencies involved. For example, with HPN we get 13MB/sec between the Azure US west Data center and the Azure East data center.But the standard ssh in 10.3 (with HPN stripped out) can barely manage 2MB/sec transfers. I did ask at the time whether it was proved that the new ssh didn't require the HPN changes, and was assured, "no" but it would appear that the picture isn't as clear. tht seems silly to have to import the port when we have what would otherwise be a perfectly good ssh as part of hte system, and it's really annoying having to specify /usr/local/bin/scp or /usr/local/bin/ssh in every script. So can we please have the latest version of the HPN changes back in the default system please? It seem rather odd that the upstream openssh has had this problem for SO LONG and not fixed it. Julian