From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 20:20:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8075416A4CE for ; Mon, 29 Nov 2004 20:20:57 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8DAF43D45 for ; Mon, 29 Nov 2004 20:20:56 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 4129 invoked from network); 29 Nov 2004 20:12:28 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 29 Nov 2004 20:12:28 -0000 Message-ID: <41AB84A6.50309@freebsd.org> Date: Mon, 29 Nov 2004 21:20:54 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au> In-Reply-To: <20041129185152.GF804@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: Claudiu Dragalia-Paraipan cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 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: Mon, 29 Nov 2004 20:20:57 -0000 Peter Jeremy wrote: > 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. If the oversized ethernet frame makes it to the FreeBSD box it will drop the frame in the ethernet hardware or in ether_input() with a message. If you don't get a message on the console you have to look at the driver statistics if it got any oversized frames. If the switches along the patch can't handle the oversized frame they will simply drop it. No way to work around that. -- Andre