From owner-freebsd-firewire@FreeBSD.ORG Mon Aug 9 07:59:35 2004 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 215FD16A4CE; Mon, 9 Aug 2004 07:59:35 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EBA543D31; Mon, 9 Aug 2004 07:59:34 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i797xUvl064326; Mon, 9 Aug 2004 08:59:30 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-firewire@freebsd.org Date: Mon, 9 Aug 2004 08:59:34 +0100 User-Agent: KMail/1.6.2 References: <4116EA33.8040405@FreeBSD.org> In-Reply-To: <4116EA33.8040405@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Message-Id: <200408090859.34574.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: Alexander Nedotsukov Subject: Re: max MTU for fwip device. X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 07:59:35 -0000 On Monday 09 August 2004 04:06, Alexander Nedotsukov wrote: > Hi again, > Is there any reason why we do not support MTUs higher than 1500 bytes > on firewire links? Basically, we are limited by the specification. The rfc states that the default MTU should be 1500 bytes. From the spec: "NOTE: IP-capable nodes may operate with an MTU size larger than the default, but the means by which a larger MTU is configured are beyond the scope of this document."