From owner-freebsd-hackers Tue Oct 8 2:18:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F87137B401 for ; Tue, 8 Oct 2002 02:18:22 -0700 (PDT) Received: from hotmail.com (f120.law3.hotmail.com [209.185.241.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AD3B43E8A for ; Tue, 8 Oct 2002 02:18:22 -0700 (PDT) (envelope-from riaal@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 8 Oct 2002 02:18:22 -0700 Received: from 196.30.152.3 by lw3fd.law3.hotmail.msn.com with HTTP; Tue, 08 Oct 2002 09:18:21 GMT X-Originating-IP: [196.30.152.3] From: "Riaal Domingues" To: freebsd-hackers@freebsd.org Cc: pk@nanoteq.com Subject: Network connections keep dropping Date: Tue, 08 Oct 2002 09:18:21 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 08 Oct 2002 09:18:22.0215 (UTC) FILETIME=[A5EED170:01C26EAB] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there! I have a strange problem and I hope you guys can help me. We have several 4.6-RELEASE boxes running SSH, after connected for a while (varies between 5 min. and an +-40) the connection dies. The SSH on the server only writes out the following message: "fatal: Write failed : permission denied". I looked in the SSH source code, and the only file that generates an error like that is /usr/src/crypto/openssh/packet.c. The permissions denied (errno set by system) error is generated in an attempt to write to the "connection_out" socket. I then tried a connection to the servers using telnet, and exactly the same behaviour as with SSH !! So, it is not SSH related, we upgrade the server to 4.6.2-RELEASE but still the same thing, it looks like it may have something to do with the kernel or network sockets or something. I tried it on different hardware combinations as well with the same results. We use a plain installation with a vanilla SSH config, nothing unusual, the kernel is configured to use ipfirewall, striped from some SCSI devices, I386 I486 and that's it. A quick way to generate the error is to log on to the server, leave it for a while then add a firewall rule and delete it again, on deletion the connection to that server (using ssh) is immediately disconnected with the same error message from sshd as described above. This trick generates the problem about 99% of the time. I can't find anything in the mailing list of similar problems. Has anyone else experienced something like this? or can anybody please give me a hint what else I can do to try and find the problem. Cheers Peut Kotze ------------------------------------------------------- _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message