From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 29 18:52:01 2004 Return-Path: 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 8BDC116A4CE; Mon, 29 Nov 2004 18:52:01 +0000 (GMT) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BB543D69; Mon, 29 Nov 2004 18:52:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iATIpwMv030230 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Nov 2004 05:51:59 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iATIpwxP061235; Tue, 30 Nov 2004 05:51:58 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iATIprXg061234; Tue, 30 Nov 2004 05:51:53 +1100 (EST) (envelope-from pjeremy) Date: Tue, 30 Nov 2004 05:51:52 +1100 From: Peter Jeremy To: Claudiu Dragalia-Paraipan Message-ID: <20041129185152.GF804@cirb503493.alcatel.com.au> References: <41AA0043.5070109@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AA0043.5070109@gmail.com> User-Agent: Mutt/1.4.2i cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 18:52:01 -0000 On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: >Since the problem occurs only when I connect to the firewall or to a >server behind it, I started to suspect a hardware failure. Could a >network card cause such problems ? A couple of people have mentioned path-MTU problems. I've also bumped into this problem when playing with VLANs where one end of the VLAN trunk doesn't support long frames - an oversize packet will get ignored by the receiver without any error being returned. -- Peter Jeremy