Date: Tue, 21 Apr 1998 21:28:27 -0400 (EDT) From: "Matthew N. Dodd" <winter@jurai.net> To: Paul Norton <pnorton@ccnvhi.com> Cc: "Larry S. Lile" <lile@stdio.com>, tokenring@FreeBSD.ORG Subject: Re: Current work... Message-ID: <Pine.BSF.3.96.980421211656.523n-100000@sasami.jurai.net> In-Reply-To: <199804212320.QAA00694@grumpy.ccnvhi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. :) /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980421211656.523n-100000>