From owner-freebsd-tokenring Tue Apr 21 16:21:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18984 for freebsd-tokenring-outgoing; Tue, 21 Apr 1998 16:21:44 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from charon.ccnvhi.com (wkstn.ccnvhi.com [207.247.3.162] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA18881 for ; Tue, 21 Apr 1998 23:20:59 GMT (envelope-from pnorton@ccnvhi.com) Received: by charon.ccnvhi.com; (5.65v3.2/1.3/10May95) id AA01080; Tue, 21 Apr 1998 16:20:54 -0700 Date: Tue, 21 Apr 1998 16:20:53 -0700 Message-Id: <199804212320.QAA00694@grumpy.ccnvhi.com> From: Paul Norton Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Larry S. Lile" Cc: tokenring@FreeBSD.ORG Subject: Re: Current work... In-Reply-To: References: <199804212242.PAA00550@grumpy.ccnvhi.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry S. Lile writes: > So we should dump it. Yup. > So ISO88025_MIN_LEN = ISO88025_HDR_LEN > How much space for the source routes? Two bytes for the RCF and 16 bytes for the route fields. > This would still be valid because we are really looking at absolute > maximums and minimums. Each driver could reject packets based on > its current configured MTU. Yes, but you really need to tell the user when they attempt to configure the interface with an invalid MTU as well. Otherwise their first clue that they've misconfigured the interface is that some connections just don't work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message