From owner-freebsd-tokenring Tue Apr 21 19:20:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21233 for freebsd-tokenring-outgoing; Tue, 21 Apr 1998 19:20:28 -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 CAA21191 for ; Wed, 22 Apr 1998 02:20:13 GMT (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id WAA17027; Tue, 21 Apr 1998 22:17:58 -0400 (EDT) Date: Tue, 21 Apr 1998 22:17:57 -0400 (EDT) From: "Larry S. Lile" To: "Matthew N. Dodd" cc: Paul Norton , tokenring@FreeBSD.ORG Subject: Re: Current work... In-Reply-To: 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, Matthew N. Dodd wrote: > On Tue, 21 Apr 1998, Paul Norton wrote: > > Two bytes for the RCF and 16 bytes for the route fields. > > 3.2.5 Routing information (RI) field > > When a frame's routing information indicator bit in the source address > field is equal to 1 (RII=1), the RI field shall be included in the frame. > The following provides sufficient information for the MAC entity to > determin the size of the RI field and parse the frame properly. The > detailed structure and contents for the RI field is described in ISO/IEC > 10038:1993 and ISO/IEC 88022-2 : 1994 > > <- RI Field (Length represented by LTH Field) -> > | | > +------+--------+------------------------------+ > | 3 | LTH | | > | bits | 5 bits | | > +------+--------+------------------------------+ > > RI = Routing Information (2 to 30 octets when present) > LTH = Lenght (5 bits) (number of octets) > > > 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. > > iso88025subr.c : iso88025_ioctl() must insure that such misconfiguration > will not happen. > > And will when I get a chance to write it. :) I am already working on iso88205_ioctl that is why I was trying to determine the limits for 802.5. Larry lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message