From owner-freebsd-hackers  Tue Feb 24 17:10:07 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA22730
          for freebsd-hackers-outgoing; Tue, 24 Feb 1998 17:10:07 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from monk.via.net (monk.via.net [140.174.204.10])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA22642
          for <hackers@FreeBSD.ORG>; Tue, 24 Feb 1998 17:10:00 -0800 (PST)
          (envelope-from joe@via.net)
Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id QAA28713; Tue, 24 Feb 1998 16:58:47 -0800
Date: Tue, 24 Feb 1998 16:58:47 -0800
From: Joe McGuckin <joe@via.net>
Message-Id: <199802250058.QAA28713@monk.via.net>
To: AdamT@smginc.com
Subject: RE: Token Ring for FreeBSD yet?
Cc: hackers@FreeBSD.ORG
X-Sun-Charset: US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


We had this same problem. There was a legacy AS/400 network
connected to a few hundred PC's that we wanted to control via
ISC-DHCP. We initially installed BSDI because it has token ring
support. After a few weeks of the BSDI box causing network jams,
we bought a  Cisco 2503 router to bridge token ring to ethernet.

Works great now.

Oh yeah, we scrubbed BSDI off and installed FreeBSD.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message