From owner-freebsd-net@FreeBSD.ORG Fri Jul 20 18:34:53 2007 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23A3816A476 for ; Fri, 20 Jul 2007 18:34:53 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outO.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 5735C13C4A8 for ; Fri, 20 Jul 2007 18:34:50 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Fri, 20 Jul 2007 11:34:49 -0700 Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 7858E125A24; Fri, 20 Jul 2007 11:34:49 -0700 (PDT) Message-ID: <46A10063.9010902@elischer.org> Date: Fri, 20 Jul 2007 11:35:15 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Eli Dart References: <200707150237.l6F2bAgZ011098@redrock.karels.net> <469E0FFF.8070802@seclark.us> <20070720172021.8EA3D13C4B3@mx1.freebsd.org> In-Reply-To: <20070720172021.8EA3D13C4B3@mx1.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: 6.2 mtu now limits size of incomming packet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2007 18:34:53 -0000 Eli Dart wrote: > > > Stephen Clark wrote: > >>> >> So was any decision reached on this issue - will FreeBSD changed to >> accept a packet on an >> interface that is larger than the mtu on that interface? > > If possible, I'd like to see the ability to enforce interface MTU for > received packets preserved in a sysctl if it is removed for the default > config... In other words, something like: > > net.link.mtu_limits_received_pktsize = 0|1 > > Then, default it to 0 to preserve 4.x behavior. what would this achieve? Answering himself.. it MAY allow a driver to optimise a bit by not needing to cope with the posibility of receiving jubo packets? I can not think of any other reason.. (except to break networks that are apparently working fine). > > Thanks, > > --eli >