From owner-freebsd-current@FreeBSD.ORG Tue Jun 8 15:38:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 46E0E16A4CE; Tue, 8 Jun 2004 15:38:41 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i58FceJj045990; Tue, 8 Jun 2004 11:38:40 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i58FcdaD045989; Tue, 8 Jun 2004 11:38:39 -0400 (EDT) (envelope-from green) Date: Tue, 8 Jun 2004 11:38:38 -0400 From: Brian Feldman To: Andrey Chernov , Stephen McKay , freebsd-current@FreeBSD.ORG Message-ID: <20040608153838.GF23083@green.homeunix.org> References: <200406081157.i58BvGJd012588@dungeon.home> <20040608122735.GA10813@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040608122735.GA10813@nagual.pp.ru> User-Agent: Mutt/1.5.6i Subject: Re: sshd should not use TCP_NODELAY X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 08 Jun 2004 15:38:41 -0000 On Tue, Jun 08, 2004 at 04:27:35PM +0400, Andrey Chernov wrote: > On Tue, Jun 08, 2004 at 09:57:16PM +1000, Stephen McKay wrote: > > My quick and ready answer to my problem is to hack openssh/packet.c and take > > out the call to set_nodelay() from packet_set_interactive(). This means that > > TCP_NODELAY is no longer set on the socket. It also turns it off in the client > > but I may change my mind on that yet. > > Just FYI, PuTTY client have an option to enable/disable TCP_NODELAY per > user needs. If it will be an option, it should go to client part too. It sounds like there needs to be an option to switch from TCP_NODELAY to either one of the SSH1-type buffering mechanism or to a sockopt that can be set on both ends. I don't think TCP_NODELAY is really the problem, but I bet that without it there would be enough delay in-between various multi-character control sequences (arrow keys, etc.) that they'd become useless. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\