From owner-freebsd-questions@FreeBSD.ORG Fri Mar 31 15:20:17 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9C4F16A400 for ; Fri, 31 Mar 2006 15:20:17 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 654C343D48 for ; Fri, 31 Mar 2006 15:20:15 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 1281 invoked from network); 31 Mar 2006 15:20:14 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 31 Mar 2006 15:20:14 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id E832028425; Fri, 31 Mar 2006 10:20:13 -0500 (EST) Sender: lowell@be-well.ilk.org To: "Nikolas Britton" References: From: Lowell Gilbert Date: 31 Mar 2006 10:20:13 -0500 In-Reply-To: Message-ID: <44d5g2d4k2.fsf@be-well.ilk.org> Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd general questions Subject: Re: ssh session hangs when term is flooded with text. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd general questions List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 15:20:17 -0000 "Nikolas Britton" writes: > When I log into any FreeBSD box through the VPN (IPsec site-to-site) > my ssh session will eventually hang when a large amount of text/data > is displayed, for example compiler output, running top, running links > or lynx, etc. Obviously this is a networking problem but I'm not sure > where to start. 1) Look at the state of the sshd task handling your shell. 2) Look at the network traffic for the sshd session. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/