From owner-freebsd-net@FreeBSD.ORG  Thu Jul 19 01:30:43 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 7DDE716A401
	for <freebsd-net@freebsd.org>; Thu, 19 Jul 2007 01:30:43 +0000 (UTC)
	(envelope-from karels@redrock.karels.net)
Received: from redrock.karels.net (redrock.karels.net [206.196.45.2])
	by mx1.freebsd.org (Postfix) with ESMTP id 247CE13C474
	for <freebsd-net@freebsd.org>; Thu, 19 Jul 2007 01:30:42 +0000 (UTC)
	(envelope-from karels@redrock.karels.net)
Received: from redrock.karels.net (localhost.karels.net [127.0.0.1])
	by redrock.karels.net (8.13.8/8.13.6) with ESMTP id l6J1UfS4027169;
	Wed, 18 Jul 2007 20:30:41 -0500 (CDT)
	(envelope-from karels@redrock.karels.net)
Message-Id: <200707190130.l6J1UfS4027169@redrock.karels.net>
To: Tom Judge <tom@tomjudge.com>
From: Mike Karels <karels@karels.net>
In-reply-to: Your message of Wed, 18 Jul 2007 23:04:15 +0100.
	<469E8E5F.9000707@tomjudge.com> 
Date: Wed, 18 Jul 2007 20:30:41 -0500
Sender: karels@karels.net
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
Reply-To: karels@karels.net
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2007 01:30:43 -0000

> There are also things to consider such as if a GigE card is connected to 
> a GigE device (switch/card etc) and the card supports jumbo frames 
> should the MRU be set to the max jumbo receive size for the card? This 
> could cause confusion when people plug jumbo capable devices in with 
> hardware limitations making the MRU lower than other devices on the network.

Although we don't have an MRU explicitly, we don't enable reception
of jumbo frames without administrator action.  There is an IFCAP_JUMBO_MTU
flag defined, but not previously used as far as I know.  We added the
ability to set that flag with ifconfig, which enables reception of
jumbo frames without changing the MTU.  Then, in ether_input, we accept
any packet that a NIC sees fit to receive.

		Mike