Date: Mon, 29 Nov 2004 23:19:43 +0200 From: Claudiu Dragalia-Paraipan <dr.clau@gmail.com> To: Andre Oppermann <andre@freebsd.org> Cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 Message-ID: <41AB926F.30003@gmail.com> In-Reply-To: <41AB84A6.50309@freebsd.org> References: <Pine.NEB.3.96L.1041128141510.94120D-100000@fledge.watson.org> <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au> <41AB84A6.50309@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig07BB196C97858DA16AF839F1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Andre Oppermann wrote: > 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. > When the MTU is set to a value below 1500, for example 1450, I get this messages: Nov 29 23:02:34 firewall kernel: rl0: discard oversize frame (ether type 800 flags 3 len 1466 > max 1464) Nov 29 23:03:00 firewall kernel: rl0: discard oversize frame (ether type 800 flags 3 len 1514 > max 1464) ... and much many of them. With MTU 1500 I didn't notice any such message in logs. So, can I safely assume that the problem occurs because somewhere packets are simply dropped, without any warning ? -- Claudiu Dragalina-Paraipan dr.clau@gmail.com --------------enig07BB196C97858DA16AF839F1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBq5Jvm0FWxb+swkQRAuCdAJ9rm+kLUMtczXxU6u9BJ560p13YQgCfcmyO M7Vj5ns5mS/Njs5t5uZuYx8= =WLTQ -----END PGP SIGNATURE----- --------------enig07BB196C97858DA16AF839F1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41AB926F.30003>