Date: Tue, 15 Dec 1998 15:10:04 -0800 (PST) From: Archie Cobbs <archie@whistle.com> To: garyj@muc.de Cc: isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! Message-ID: <199812152310.PAA04618@bubba.whistle.com> In-Reply-To: <199812152144.WAA10556@peedub.muc.de> from Gary Jennejohn at "Dec 15, 98 10:44:48 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Jennejohn writes:
> >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 ?
[ trimming recipients to -isdn after this reply ]
We have a (very big) node that does this based on a 3rd party
ISDN stack. Unfortunately, we can't give away their software
without their permission...
> 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.
Yep.
> Unfortunately, the effort involved in converting isdn4bsd to use the
> netgraph mechanism boggles the mind :-(
It's probably not that hard. I mean, the netgraph part of it is
fairly minimal and can just be a wrapper around existing code.
It more depends on how modular the code is to begin with.
It would definitely be nice if all the different ISDN drivers could
export the same type of netgraph "ISDN BRI" node. Then you could use
the user-mode PPP with any of them, for example.
The command/response stuff makes it kindof object oriented.. eg,
netgraph node
|
+------- ISDN BRI node
|
+-------- Foo ISDN card
|
+-------- Bar ISDN card
Each "type" has a certain API for the synchronous command/response
messages. Eg, for ISDN they would be things like "dial this number",
"configure SPID", etc. There are generic commands at the netgraph
level too, like "reset node", etc. In the other direction, the Foo
type could extend the set of commands with card-specific stuff.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812152310.PAA04618>