From owner-freebsd-tokenring Tue Apr 21 16:29:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20163 for freebsd-tokenring-outgoing; Tue, 21 Apr 1998 16:29:17 -0700 (PDT) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20092 for ; Tue, 21 Apr 1998 23:29:05 GMT (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id TAA15931; Tue, 21 Apr 1998 19:26:51 -0400 (EDT) Date: Tue, 21 Apr 1998 19:26:50 -0400 (EDT) From: "Larry S. Lile" To: Paul Norton cc: tokenring@FreeBSD.ORG Subject: Re: Current work... In-Reply-To: <199804212320.QAA00694@grumpy.ccnvhi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Apr 1998, Paul Norton wrote: > Larry S. Lile writes: > > 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. I assume they would go into the HDR_LEN corret? > > 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. That can be handled in the ioctl routines. In iso88025_ioctl you must check that they have not exceeded ISO88025MTU (or absolute max) and then in the interface ioctl ex tok_ioctl that they have not exceeded the cards capacity. Actually I think that is reversed :) On another note, could you look at my code for iso88025_ioctl it is panic'ing when I set the ip address or netmask, oops. Larry lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message