Date: Tue, 16 Oct 2001 20:19:18 -0500 (EST) From: Doug Hass <dhass@imagestream.com> To: Julian Elischer <julian@elischer.org> Cc: Ted Mittelstaedt <tedm@toybox.placo.com>, Jim Bryant <kc5vdj@yahoo.com>, MurrayTaylor <taylorm@bytecraft.au.com>, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen <ashippen@metromatics.com.au> Subject: RE: FYI Message-ID: <Pine.LNX.3.96.1011016201841.936B-100000@ims1.imagestream.com> In-Reply-To: <Pine.BSF.4.21.0110161726510.61181-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.96.1011016201841.936B-100000>