Date: Mon, 29 Nov 2004 21:20:54 +0100 From: Andre Oppermann <andre@freebsd.org> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 Message-ID: <41AB84A6.50309@freebsd.org> In-Reply-To: <20041129185152.GF804@cirb503493.alcatel.com.au> References: <Pine.NEB.3.96L.1041128141510.94120D-100000@fledge.watson.org> <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41AB84A6.50309>