From owner-freebsd-tokenring Mon Oct 26 04:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04664 for freebsd-tokenring-outgoing; Mon, 26 Oct 1998 04:14:47 -0800 (PST) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04659 for ; Mon, 26 Oct 1998 04:14:45 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id NAA12764 for ; Mon, 26 Oct 1998 13:02:49 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1b4) id kwa12762; Mon Oct 26 13:02:30 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id NAA03390 for ; Mon, 26 Oct 1998 13:11:20 +0100 Original: Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id NAA08788 for freebsd-tokenring@freebsd.org; Mon, 26 Oct 1998 13:15:21 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199810261215.NAA08788@borg.kryptokom.de> Subject: Olicom driver To: freebsd-tokenring@FreeBSD.ORG Date: Mon, 26 Oct 1998 13:15:21 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I have read through the archive this morning and it seems that the olicom driver is entering it's final stages. I have a question in general ... How difficult would it be to implement bridging in the driver ? I would like to try this once we have a working driver. Bye Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Mon Oct 26 06:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18228 for freebsd-tokenring-outgoing; Mon, 26 Oct 1998 06:47:00 -0800 (PST) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18221 for ; Mon, 26 Oct 1998 06:46:57 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id JAA02611; Mon, 26 Oct 1998 09:48:57 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Mon, 26 Oct 1998 09:48:56 -0500 (EST) From: "Larry S. Lile" To: Reinier Bezuidenhout cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Olicom driver In-Reply-To: <199810261215.NAA08788@borg.kryptokom.de> 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 Mon, 26 Oct 1998, Reinier Bezuidenhout wrote: > Hi ... > > I have read through the archive this morning and it seems that > the olicom driver is entering it's final stages. I have to finish the transmit code, then the fun begins with source routing. Of course a lot of general cleanup in the generic code is neccesary also. > I have a question in general ... > > How difficult would it be to implement bridging in the driver ? > > I would like to try this once we have a working driver. The Olicom cards support promisc. mode all the way down to mac frames so this should be possible to do. Passive bridging should be trivial, take all packets (not destined for us) and copy them to another ring without any processing. This could be easily implemented in the driver. Passive bridging (learning) would be a little more difficult, it would have to create lists of mac's for each attached ring and only copy packets destined to a different ring based on the mac address. This would be a little more difficult to implement in the driver. You are welcome to give it a shot, I should have the driver transmitting before the end of the week. I am still unsure about how source routing will be implemented so that may be a little while longer. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Sat Oct 31 14:00:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22819 for freebsd-tokenring-outgoing; Sat, 31 Oct 1998 14:00:03 -0800 (PST) (envelope-from owner-freebsd-tokenring@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22762 for ; Sat, 31 Oct 1998 14:00:00 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id RAA02342 for ; Sat, 31 Oct 1998 17:03:17 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Sat, 31 Oct 1998 17:03:12 -0500 (EST) From: "Larry S. Lile" To: tokenring@FreeBSD.ORG Subject: Working Olicom Driver! (Somewhat unstable) 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 The Olicom driver will now transmit and recieve on a local-ring! The driver is very loud (w/console messages) but seems to be working well under light to medium loads. It will panic from a ping -f. I am working on the instability right now, it has only been transmitting for about 45 mins now. I know what most of the probelms are and should have them fixed shortly. Performance will increase once i remove some of the excess console messages and begin allocating memory in a more reasonable fashion, ie memory under 16m only when neccesary. But bottom line it works! Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message