From owner-freebsd-net Tue Jun 29 6:54:37 1999 Delivered-To: freebsd-net@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 61CA314DB9 for ; Tue, 29 Jun 1999 06:54:34 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id JAA18454; Tue, 29 Jun 1999 09:50:16 -0400 (EDT) Message-Id: <199906291350.JAA18454@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 29 Jun 1999 08:46:44 -0400 To: maillist@xinetron.com From: Dennis Subject: Re: Frame Relay Driver? Cc: freebsd-net@freebsd.org In-Reply-To: <7l8vol$nbqe@eGroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 04:16 PM 6/28/99 -0700, you wrote: >Hi Group, > >Is there any "traditional" frame relay driver available for FreeBSD. I know that NetGraph supports frame relay, but I am really not ready to bring in an entire new network architecture just to support Frame Relay. I am looking for some "traditional" driver for frame relay, like those used with ETinc sync cards. Does the ET cards come with driver source code? Is there any DLCI device driver like that in Linux (dlci and dlcicfg)? What is "traditional"? The DLCI driver for linux is more of a kludge than a frame relay protocol driver. There are different philosophies for implementing protocols, ours is to make is as transparent (and painless) as possible for the user without sacrificing functionality. Unfortunately the most common frame relay switch available (cascades) are very much broken, so its a lot of fun supporting frame. Dennis Emerging Technologies, Inc. http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX HSSI/T3 UNIX-based Routers Bandwidth Manager http://www.etinc.com/bwmgr.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message