From owner-freebsd-questions@FreeBSD.ORG Mon Apr 18 13:15:19 2005 Return-Path: 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 8741716A4CE for ; Mon, 18 Apr 2005 13:15:19 +0000 (GMT) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44DF643D39 for ; Mon, 18 Apr 2005 13:15:19 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 24801 invoked from network); 18 Apr 2005 13:15:18 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 18 Apr 2005 13:15:17 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 35A7E52; Mon, 18 Apr 2005 09:15:16 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Dino Vliet References: <20050417113938.65650.qmail@web51102.mail.yahoo.com> From: Lowell Gilbert Date: 18 Apr 2005 09:15:15 -0400 In-Reply-To: <20050417113938.65650.qmail@web51102.mail.yahoo.com> Message-ID: <44acnwz0nw.fsf@be-well.ilk.org> Lines: 24 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-questions@freebsd.org Subject: Re: ssh terminates connection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 13:15:19 -0000 Dino Vliet writes: > Hi all, > > when using ssh I encounter the following situation > after a short moment of inactivity: > > "write failed: permission denied" > > Then I'm logged out and have to re-login. > The problem is anoying because whenever I let > postgresql for instance start a script, I can't walk > away. > > I'm using openSSH 3.5p1 (from the ports tree) on my > freebsd 4.10 system. > > Can anyone advise me what to do to stop this? Sounds like you're running afoul of your own firewall. Perhaps the session state is being timed out by the firewall or NAT software? We can't really give much more of a pointer without more information...