From owner-freebsd-tokenring Wed Apr 22 08:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00903 for freebsd-tokenring-outgoing; Wed, 22 Apr 1998 08:23:15 -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 PAA00888 for ; Wed, 22 Apr 1998 15:23:08 GMT (envelope-from pnorton@ccnvhi.com) Received: by charon.ccnvhi.com; (5.65v3.2/1.3/10May95) id AA07773; Wed, 22 Apr 1998 08:23:07 -0700 Date: Wed, 22 Apr 1998 08:23:05 -0700 Message-Id: <199804221523.IAA03697@grumpy.ccnvhi.com> From: Paul Norton Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Paul_Labadie@tivoli.com Cc: tokenring@FreeBSD.ORG Subject: Re: Current work... In-Reply-To: <852565EE.004C23D7.00@notes-brahms2.tivoli.com> References: <852565EE.004C23D7.00@notes-brahms2.tivoli.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul_Labadie@tivoli.com writes: > not sure how most drivers handle the packet when there is no RIF, No problem. No RIF? Then it came from the local ring and not from across a source-routing bridge. BTW, we'll need to keep track of MAC addresses of network peers and their associated RIFs in a cache. > first 3 bits > 0XX = Non-Broadcast > 10X = All-Route Broadcast > 11X = Single-route broadcast > X means either a 1 or a 0. > > > since the information field follows the RI, i never understood how > a driver knows if the next field is an IF, RIF or the CRC/end code. You never see the CRC/end code. If the RII is set you know a RIF is present. The length of the RIF is encoded in the RCF, which is within the RIF and is called the LTH/Broadcast bits in your diagram. RCF may be the IBM designation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message