From owner-freebsd-current Tue Dec 15 13:58:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02282 for freebsd-current-outgoing; Tue, 15 Dec 1998 13:58:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02254; Tue, 15 Dec 1998 13:58:03 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id WAA10556; Tue, 15 Dec 1998 22:44:48 +0100 (CET) Message-Id: <199812152144.WAA10556@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 15 Dec 1998 12:56:21 PST." <199812152056.MAA00665@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 22:44:48 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: >Johan Granlund writes: >> What i was thinking about was something more like lowbandwidth / high >> processing protocols. If the endpoint is a serial port, network interface >> or the network protocol stack (for tunneling) should't be a issue if >> it's used right. > >Here's some examples of what we use the netgraph stuff for on the >InterJet. > [snip] > - ISDN node > > Is a device driver and a netgraph node. Performs the D channel > signalling and has a hook for each B channel. Accepts synchronous > commands for things like dialing, etc. > [snip] does this handle the full I.430, Q.93x stuff too ? In other words, passive ISDN cards ? >Of course the other major benefit is modularity. Instead of having >if_ppp.c, if_sppp.c, if_foo1.c, if_foo2.c, where you are reimplementing >the interface behavior code over and over again, you just keep this >code in a single place: ng_iface.c, the interface node. Then anybody >who needs to export an interface can do so by connecting it to an >interface node (example: cisco hdlc node). > >These little guys make great LKM/KLD modules too.. > >Anyway, one reason I'm hyping this a little bit is because we >(Julian and me) want to clean up, and update, and unencumber the >netgraph code that was released a year or so ago, and check it in >so people can start playing with it more. It will take a little time >though, not to mention approval from the kernel gargoyles... > wow ! This sounds like it would be great for the CAPI stuff I'm trying to implement for isdn4bsd right now. If the card needs CAPI, just hang a CAPI node in the graph. Unfortunately, the effort involved in converting isdn4bsd to use the netgraph mechanism boggles the mind :-( --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message