From owner-freebsd-hackers  Tue Oct 10 12:00:27 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA00549
          for hackers-outgoing; Tue, 10 Oct 1995 12:00:27 -0700
Received: from etinc.com (etinc-gw.new-york.net [165.254.13.209])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA00532
          for <hackers@freebsd.org>; Tue, 10 Oct 1995 12:00:19 -0700
Received: from trumpet.etnet.com (trumpet.etnet.com [129.45.17.35]) by etinc.com (8.6.11/8.6.9) with SMTP id PAA01532; Tue, 10 Oct 1995 15:09:09 -0400
Date: Tue, 10 Oct 1995 15:09:09 -0400
Message-Id: <199510101909.PAA01532@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Julian Elischer <julian@ref.tfs.com>
From: dennis@etinc.com (dennis)
Subject: Re: IPX
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
Precedence: bulk

> yes please!
>and I'd like to know whether this fits in with what dennis was saying they had
>there..
>dennis?
>
It doesn't seem likely that there would be much inter-operability. Our
router product is 
embedded in our kernel driver and does RIP and SAP in the kernel (no
daemons). There is an internal
routing table and separate utilities (we haven't hacked any FreeBSD stuff)
that can be used
to display and manage the tables. We use a simple filter (about 3 lines of
code have to be added
to any ethernet driver) that passes packets to our driver. Its designed to
be an autonomous system, 
not something to be permanently included in the system.

Dennis
----------------------------------------------------------------------------
Emerging Technologies, Inc.      http://www.etinc.com

Synchronous Communications Cards and Routers For
Discriminating Tastes. 56k to T1 and beyond. Frame
Relay, PPP, HDLC, and X.25