From owner-freebsd-questions Tue Oct 16 18:39:36 2001 Delivered-To: freebsd-questions@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id C527337B40C; Tue, 16 Oct 2001 18:39:25 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id UAA01080; Tue, 16 Oct 2001 20:19:18 -0500 Date: Tue, 16 Oct 2001 20:19:18 -0500 (EST) From: Doug Hass To: Julian Elischer Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Better than a published interface and white paper, we also provide the direct code itself. You could certainly make a netgraph/SAND interface module. Doug On Tue, 16 Oct 2001, Julian Elischer wrote: > > > On Tue, 16 Oct 2001, Doug Hass wrote: > > > > The "hardware API" or the actual register interface code, is a binary-only > > > module that is "snapped in" to SAND. SAND is GPL and is similar to the > > > FreeBSD Netgraph module - it provides all the higher-level protocol stuff, > > > like > > > Frame Relay, PPP, HDLC, and such. SAND goes between the OS TCP/IP stack and > > > that binary only module. > > > > That's rather simplified, since SAND also does alot of other things, but > > you have the basics. > > > > If there's a published interface, we could make a netgraph/SAND interface > module > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message