From owner-freebsd-current@FreeBSD.ORG Sat Nov 1 15:24:21 2003 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 BD08916A4D8 for ; Sat, 1 Nov 2003 15:24:21 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F9EC43F85 for ; Sat, 1 Nov 2003 15:24:20 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9p2/8.12.9) with ESMTP id hA1NOIp4097734; Sat, 1 Nov 2003 18:24:18 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9p2/8.12.9/Submit) id hA1NOI62097733; Sat, 1 Nov 2003 18:24:18 -0500 (EST) (envelope-from barney) Date: Sat, 1 Nov 2003 18:24:18 -0500 From: Barney Wolff To: Terry Lambert Message-ID: <20031101232418.GA97622@pit.databus.com> References: <20031029183808.M99053@prg.traveller.cz> <3FA223AB.797B2528@mindspring.com> <20031031175030.GB78910@pit.databus.com> <3FA420F3.35045EF6@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA420F3.35045EF6@mindspring.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.37 cc: Barney Wolff cc: Michal Mertl cc: current@freebsd.org Subject: Re: jumbograms (& em) & nfs a no go 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: Sat, 01 Nov 2003 23:24:21 -0000 On Sat, Nov 01, 2003 at 01:09:07PM -0800, Terry Lambert wrote: > Barney Wolff wrote: > > > Implies the sending host is not honoring the MTU restriction when > > > deciding whether or not to frag packets. > > > > 67582 looks awfully bogus even as a pre-frag length. How could that come > > over the wire? > > The sending host is not honoring the MTU restriction? > > 8-) 8-). > > Most likely, a direct call to ether_output, or a code path that > results in fragmentation not being implemented; see my other post: > it could be that he's using NFS over UDP, and that's doing it. Er, how is it possible to send a UDP packet > 65535? Last time I looked it was a 16-bit field. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.