From owner-freebsd-isdn Mon Oct 7 7:41:25 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B951337B401 for ; Mon, 7 Oct 2002 07:41:19 -0700 (PDT) Received: from fep03-svc.swip.net (fep03.swip.net [130.244.199.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7146B43E6A for ; Mon, 7 Oct 2002 07:41:18 -0700 (PDT) (envelope-from hselasky@c2i.net) Received: from mta-int.swip.net ([192.168.145.27]) by fep03-svc.swip.net with SMTP id <20021007144117.CCC23699.fep03-svc.swip.net@mta-int.swip.net> for ; Mon, 7 Oct 2002 16:41:17 +0200 X-Originating-IP: [128.39.202.148] From: To: freebsd-isdn@freebsd.org Subject: New ihfc driver Date: Mon, 7 Oct 2002 16:41:17 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=____1034001677145_I.C2G'rDRh" Message-Id: <20021007144117.CCC23699.fep03-svc.swip.net@mta-int.swip.net> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=____1034001677145_I.C2G'rDRh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi. There is another version of new_ihfc available. For more information please see attached file driver_info.txt. Some bugs have been fixed: - ifpi2: had a missing include file which broke LINT - memset was replaced with a local copy due to a compile issue which caused TIGERJET to send 0x00 instead of 0xff on IOM2 bus. - code should be sync with current unless new patches have been committed since last week. - All B-channels should now work with wibusb. - with some luck LINT should compile. Yours - HPS ------------------------------------------------- WebMail fra Tele2 http://www.tele2.no ------------------------------------------------- ------=____1034001677145_I.C2G'rDRh Content-Type: text/plain; name="driver_info.txt" Content-Disposition: inline; filename="driver_info.txt" For developers and others wanting to help debug: Driver can be downloaded from: http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/new_ihfc_0_3.tar.bz2 A diff has also been made for existing files (not the new ones) so that it is easier to check where changes have been made, hence current may change. http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/new_ihfc_0_3.diff.bz2 NOTE: This code should work with the current sources of 2. of October 2002. Using this driver with earlier current sources may break other drivers, but new_ihfc. List of new features currently not found in I4B: - Driver uses mutexes to protect chip access. - Direct access to D-channel and B-channel(not finished, but works) - D-channel encoding support. - Support for: - NT-mode (IPAC chips support line switch instead) - data filters (``as plug-ins'') - drivers (``as plug-ins'') - polled interrupt mode - chip reset - HFCS-PCI - USB About the driver: ================= The driver supports generic IPAC/ISAC/HSCX/HFC chips and allows the drivers to emulate behind one or more of those chips. As a consequence of this any ring-buffer or block-buffer isdn device can easily be implemented with a minimum of code. To have more people being able to test the driver there has been added support for some cards already found in ISDN4BSD. Please see the new_ihfc.4 manual. NOTE: Only HFC based and Dynalink compatible cards have been tested. Please send patches using `diff -crN` and include the complete file if the patch is big. NOTE: Code outside of i4b/layer1/ was rewritten. Possible kernel bugs found: =========================== 1. (not patched, only temporary workaround) In the function static int isa_find_irq(device_t child, struct isa_config *config, struct isa_config *result) the following lines have been added, though it is bus_alloc_resource that doesn't check that RF_SHAREABLE is not present?! + /* Don't share IRQ unless the driver wants */ + if(res[i]->r_sharehead) { + bus_release_resource(child, + SYS_RES_IRQ, i, res[i]); + res[i] = 0; + continue; + } 2. (not patched, only temporary workaround) the function device_get_namenunit(dev) in /sys/kern/subr_bus.c returns one text pointer value at probe time and another after attach. device_get_nameunit(dev) should be considered the same way as device_get_softc(dev) in my opinion. 3. (no patch) when using Polled mode the KERNEL provides no function to switch the interrupt output of a card to an unused pin. All PnP controllers should support this (and maybe PCI controllers too), but there are no routines to call that will do this! Currently only HFC chips support switching of IRQ in hardware, any maybe the old ISA cards if you can remove the IRQ jumper! This might be interesting for people wanting to use their old ISA cards, but doesn't want to spend time on configuration. 4. (local patch) memset in ../sys/libkern.h does not work when sizeof(*src) > sizeof(char) (reason unknown, maybe a compiler issue) TODO: ===== 1. Currently freeing an mbuf takes ``so long time'' that if it is done before an ISAC/HSCX cmdr write, that command may fail (no fix). Is this a mutex sleeping problem? Also when switching the console there may occur glitches in the output stream. Maybe ISDN4BSD should use a fixed ring of mbufs to speed up allocation and freeing? Some tests in polled mode showed that enabling the Giant mutex before interrupt call caused an extra delay in the range 10ms! How to install: ============= 1. manually add these lines to /sys/conf/files.i386 at the line saying: # # isdn4bsd, needed for isic | iwic | ifpi | ifpi2 | ihfc | ifpnp | itjc # # add this: i4b/layer1/i4b_l1dmux.c optional new_ihfc i4b/layer1/i4b_l1lib.c optional new_ihfc i4b/layer1/i4b_hdlc.c optional new_ihfc # # and this: # # isdn4bsd, new_ihfc # i4b/layer1/ihfc2/i4b_ihfc2_l1if.c optional new_ihfc i4b/layer1/ihfc2/i4b_ihfc2_pnp.c optional new_ihfc i4b/layer1/ihfc2/i4b_ihfc2_drv.c optional new_ihfc i4b/layer1/ihfc2/i4b_ihfc2_dev.c optional new_ihfc 2. make sure the following lines are in your kernel configuration file: (NOTE: please only use one of new_ihfc and (ihfc or isic or itjc) at a time). # I4B section options IPR_VJ device "i4bq921" device "i4bq931" device "i4b" device "i4btrc" 8 device "i4bctl" device "i4brbch" 8 device "i4btel" 8 device "i4bipr" 8 device "i4bisppp" 8 device new_ihfc 3. make backup of these directories if you don't want to develop the driver mkdir /usr/i4b_bak || exit mkdir /usr/i4b_bak/sys || exit cp -rv /usr/include/machine /usr/i4b_bak/ cp -rv /usr/src/sys/i386/include /usr/i4b_bak/sys/ cp -rv /usr/src/usr.sbin/i4b /usr/i4b_bak/ cp -rv /usr/src/sys/i4b /usr/i4b_bak/sys/ cp -rv /usr/src/sys/isa/isa_common.c /usr/i4b_bak/ rm -rv /usr/src/sys/i4b/* 4. install the driver like this tar -jxvf new_ihfc*.tar.bz2 -C /usr/src/ cp -rv /usr/src/sys/i386/include/*i4b* /usr/include/machine/ 5. run your kernel configuration script 6. recompile the kernel (remove all *i4b*.o files from the compile directory or make clean build) 7. hopefully no errors should occur during compilation. 8. after the kernel has been compiled recompile isdndebug and manual pages (`man new_ihfc' should work afterwards) cd /usr/src/usr.sbin/i4b/ make all install 9. make a backup of the old kernel in case it doesn't work. 10. reboot -HPS ------=____1034001677145_I.C2G'rDRh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Oct 7 9:58: 7 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E042637B401 for ; Mon, 7 Oct 2002 09:58:01 -0700 (PDT) Received: from nexus.tmp.com.br (nexus.tmp.com.br [200.255.204.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 280A243E3B for ; Mon, 7 Oct 2002 09:57:59 -0700 (PDT) (envelope-from prallon@nexus.tmp.com.br) Received: (from prallon@localhost) by nexus.tmp.com.br (8.8.8/8.8.8) id NAA15012; Mon, 7 Oct 2002 13:57:49 -0300 Date: Mon, 7 Oct 2002 13:57:49 -0300 From: Sergio de Souza Prallon To: hselasky@c2i.net Cc: freebsd-isdn@freebsd.org Subject: Re: New ihfc driver Message-ID: <20021007135749.A14322@tmp.com.br> References: <20021007144117.CCC23699.fep03-svc.swip.net@mta-int.swip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20021007144117.CCC23699.fep03-svc.swip.net@mta-int.swip.net>; from hselasky@c2i.net on Mon, Oct 07, 2002 at 04:41:17PM +0200 X-URL: http://www.tmp.com.br Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, From the fragment below I noticed that your driver also works with the Tiger chips. In fact,if I understood right, it can replace the entire set of layer drivers. Apparently you tried very hard to eliminate duplicated code spread among the various drivers, what is, IMHO, a `Good Thing' (tm). The only critic I do is the legibility of the code. In a brief look I've made, I didn't manage to grasp how the gears of your "macro driver programing language" work under the hood. There isn't another, a bit more readable, way around it? Do you have a -STABLE version of your driver? I want to give it a try but an upgrade to -CURRENT is out of question. May be I learn a thing or two from the experience as it was the case with the HDLC macros. []'s -- Prallon On Mon, Oct 07, 2002 at 04:41:17PM +0200, hselasky@c2i.net wrote: > Hi. > > There is another version of new_ihfc available. For more information please see > attached file driver_info.txt. > > Some bugs have been fixed: > - ifpi2: had a missing include file which broke LINT > - memset was replaced with a local copy due to a compile issue which > caused TIGERJET to send 0x00 instead of 0xff on > IOM2 bus. > - code should be sync with current unless new > patches have been committed since last week. > - All B-channels should now work with wibusb. > - with some luck LINT should compile. > > Yours > - HPS > > > ------------------------------------------------- > WebMail fra Tele2 http://www.tele2.no > ------------------------------------------------- > For developers and others wanting to help debug: > > Driver can be downloaded from: > > http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/new_ihfc_0_3.tar.bz2 > > A diff has also been made for existing files (not the new ones) so that > it is easier to check where changes have been made, hence current may > change. > > http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/new_ihfc_0_3.diff.bz2 > > NOTE: > > This code should work with the current sources of 2. of October 2002. Using this > driver with earlier current sources may break other drivers, but new_ihfc. > > List of new features currently not found in I4B: > - Driver uses mutexes to protect chip access. > - Direct access to D-channel and B-channel(not finished, but works) > - D-channel encoding support. > - Support for: > - NT-mode (IPAC chips support line switch instead) > - data filters (``as plug-ins'') > - drivers (``as plug-ins'') > - polled interrupt mode > - chip reset > - HFCS-PCI > - USB > > About the driver: > ================= > > The driver supports generic IPAC/ISAC/HSCX/HFC chips and allows the > drivers to emulate behind one or more of those chips. As a consequence > of this any ring-buffer or block-buffer isdn device can easily be > implemented with a minimum of code. To have more people being able to > test the driver there has been added support for some cards already > found in ISDN4BSD. Please see the new_ihfc.4 manual. > > NOTE: Only HFC based and Dynalink compatible cards have been tested. > Please send patches using `diff -crN` and include the complete file > if the patch is big. > NOTE: Code outside of i4b/layer1/ was rewritten. > > Possible kernel bugs found: > =========================== > > 1. (not patched, only temporary workaround) > > In the function > > static int > isa_find_irq(device_t child, > struct isa_config *config, > struct isa_config *result) > > the following lines have been added, though it is bus_alloc_resource > that doesn't check that RF_SHAREABLE is not present?! > > + /* Don't share IRQ unless the driver wants */ > + if(res[i]->r_sharehead) { > + bus_release_resource(child, > + SYS_RES_IRQ, i, res[i]); > + res[i] = 0; > + continue; > + } > > 2. (not patched, only temporary workaround) > > the function device_get_namenunit(dev) in /sys/kern/subr_bus.c > returns one text pointer value at probe time and another after > attach. device_get_nameunit(dev) should be considered the same way as > device_get_softc(dev) in my opinion. > > 3. (no patch) > > when using Polled mode the KERNEL provides no function to switch the > interrupt output of a card to an unused pin. All PnP controllers > should support this (and maybe PCI controllers too), but there are no > routines to call that will do this! Currently only HFC chips support > switching of IRQ in hardware, any maybe the old ISA cards if you can > remove the IRQ jumper! This might be interesting for people wanting to > use their old ISA cards, but doesn't want to spend time on > configuration. > > 4. (local patch) > > memset in ../sys/libkern.h does not work when sizeof(*src) > sizeof(char) > (reason unknown, maybe a compiler issue) > > TODO: > ===== > > 1. Currently freeing an mbuf takes ``so long time'' that if it is done > before an ISAC/HSCX cmdr write, that command may fail (no fix). Is > this a mutex sleeping problem? Also when switching the console there > may occur glitches in the output stream. Maybe ISDN4BSD should use a > fixed ring of mbufs to speed up allocation and freeing? Some tests in > polled mode showed that enabling the Giant mutex before interrupt call > caused an extra delay in the range 10ms! > > How to install: > ============= > > 1. manually add these lines to /sys/conf/files.i386 > at the line saying: > > # > # isdn4bsd, needed for isic | iwic | ifpi | ifpi2 | ihfc | ifpnp | itjc > # > # add this: > i4b/layer1/i4b_l1dmux.c optional new_ihfc > i4b/layer1/i4b_l1lib.c optional new_ihfc > i4b/layer1/i4b_hdlc.c optional new_ihfc > # > # and this: > # > # isdn4bsd, new_ihfc > # > i4b/layer1/ihfc2/i4b_ihfc2_l1if.c optional new_ihfc > i4b/layer1/ihfc2/i4b_ihfc2_pnp.c optional new_ihfc > i4b/layer1/ihfc2/i4b_ihfc2_drv.c optional new_ihfc > i4b/layer1/ihfc2/i4b_ihfc2_dev.c optional new_ihfc > > 2. make sure the following lines are in your kernel configuration > file: (NOTE: please only use one of new_ihfc and (ihfc or isic or > itjc) at a time). > > # I4B section > options IPR_VJ > device "i4bq921" > device "i4bq931" > device "i4b" > device "i4btrc" 8 > device "i4bctl" > device "i4brbch" 8 > device "i4btel" 8 > device "i4bipr" 8 > device "i4bisppp" 8 > > device new_ihfc > > 3. make backup of these directories if you don't want to > develop the driver > > mkdir /usr/i4b_bak || exit > mkdir /usr/i4b_bak/sys || exit > > cp -rv /usr/include/machine /usr/i4b_bak/ > cp -rv /usr/src/sys/i386/include /usr/i4b_bak/sys/ > cp -rv /usr/src/usr.sbin/i4b /usr/i4b_bak/ > cp -rv /usr/src/sys/i4b /usr/i4b_bak/sys/ > cp -rv /usr/src/sys/isa/isa_common.c /usr/i4b_bak/ > > rm -rv /usr/src/sys/i4b/* > > 4. install the driver like this > > tar -jxvf new_ihfc*.tar.bz2 -C /usr/src/ > > cp -rv /usr/src/sys/i386/include/*i4b* /usr/include/machine/ > > 5. run your kernel configuration script > > 6. recompile the kernel (remove all *i4b*.o files > from the compile directory or make clean build) > > 7. hopefully no errors should occur during > compilation. > > 8. after the kernel has been compiled recompile isdndebug and > manual pages (`man new_ihfc' should work afterwards) > > cd /usr/src/usr.sbin/i4b/ > make all install > > 9. make a backup of the old kernel in case > it doesn't work. > > 10. reboot > > -HPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Oct 9 17: 8:25 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E29237B401 for ; Wed, 9 Oct 2002 17:08:24 -0700 (PDT) Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id C89C743E6E for ; Wed, 9 Oct 2002 17:08:23 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id D760A10A; Wed, 9 Oct 2002 17:03:46 +0200 (CEST) Date: Wed, 9 Oct 2002 17:03:46 +0200 From: Guido van Rooij To: freebsd-isdn@freebsd.org Subject: sniffing voice calls Message-ID: <20021009150346.GA62592@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Would it be possible to use the i4b software to sniff the isdn bus and thus record phone conversations that are taking place (from a switch on the same bus). -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Oct 9 22:23:46 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7577A37B401 for ; Wed, 9 Oct 2002 22:23:45 -0700 (PDT) Received: from beverly.kleinbus.org (p508E3E4D.dip.t-dialin.net [80.142.62.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A59943E3B for ; Wed, 9 Oct 2002 22:23:44 -0700 (PDT) (envelope-from is@beverly.kleinbus.org) Received: by beverly.kleinbus.org (Postfix, from userid 1501) id 42CE665B3; Thu, 10 Oct 2002 07:23:41 +0200 (CEST) Date: Thu, 10 Oct 2002 07:23:40 +0200 From: Ignatios Souvatzis To: Guido van Rooij Cc: freebsd-isdn@freebsd.org Subject: Re: sniffing voice calls Message-ID: <20021010072340.A15641@marie> References: <20021009150346.GA62592@gvr.gvr.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021009150346.GA62592@gvr.gvr.org>; from guido@gvr.org on Wed, Oct 09, 2002 at 05:03:46PM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 09, 2002 at 05:03:46PM +0200, Guido van Rooij wrote: > Would it be possible to use the i4b software to sniff the isdn bus > and thus record phone conversations that are taking place (from > a switch on the same bus). I guess, no, unless you use a special cable and two cards (you won't be=20 able to hear your local talker otherwise). Some of the monitor commands should be able to be used oar adapted for this. I guess, however, that monitoring usage of B-Channels (and maybe even their= =20 usage type), and monitoring the remote talker, should be possible without a normal cable. Hoever, a bit of software change will be necessary, I guess. Regards, -is --=20 seal your e-mail: http://www.gnupg.org/ --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (NetBSD) Comment: For info see http://www.gnupg.org iD8DBQE9pQ7cPCRcZ/VMtk4RAqOXAKCXUohsJMx1fkXfYQFX/JZfkG09cQCfaFPp ZkLDB8w8vxpUncSiJDe2CTo= =j6dp -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Oct 10 0:15:20 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3907537B401 for ; Thu, 10 Oct 2002 00:15:19 -0700 (PDT) Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52B5943E7B for ; Thu, 10 Oct 2002 00:15:18 -0700 (PDT) (envelope-from hm@kts.org) Received: from fwd01.sul.t-online.de by mailout05.sul.t-online.com with smtp id 17zXXP-0001wP-0C; Thu, 10 Oct 2002 09:15:15 +0200 Received: from ernie.kts.org (520021727764-0001@[217.5.45.91]) by fmrl01.sul.t-online.com with esmtp id 17zXXI-11zigSC; Thu, 10 Oct 2002 09:15:08 +0200 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 112A04C95C; Thu, 10 Oct 2002 09:15:07 +0200 (CEST) Received: by bert.kts.org (Postfix, from userid 100) id DC06E54A1; Thu, 10 Oct 2002 09:15:06 +0200 (CEST) Subject: Re: sniffing voice calls In-Reply-To: <20021009150346.GA62592@gvr.gvr.org> To: Guido van Rooij Date: Thu, 10 Oct 2002 09:15:06 +0200 (CEST) Cc: freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hellmuth.michaelis@t-online.de X-Mailer: ELM [version 2.4ME+ PL95a (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20021010071506.DC06E54A1@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) X-Sender: 520021727764-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Guido van Rooij wrote: > Would it be possible to use the i4b software to sniff the isdn bus > and thus record phone conversations that are taking place (from > a switch on the same bus). Yes. However, it will not work out of the box. hellmuth -- Hellmuth Michaelis Hamburg, Europe hm@kts.org www.kts.org There is a difference between an open mind and a hole in the head. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Oct 10 4:58:44 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BE1C37B401 for ; Thu, 10 Oct 2002 04:58:43 -0700 (PDT) Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF6AB43E77 for ; Thu, 10 Oct 2002 04:58:42 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 07B93FC; Thu, 10 Oct 2002 13:58:41 +0200 (CEST) Date: Thu, 10 Oct 2002 13:58:40 +0200 From: Guido van Rooij To: hellmuth.michaelis@t-online.de Cc: freebsd-isdn@freebsd.org Subject: Re: sniffing voice calls Message-ID: <20021010115840.GA68320@gvr.gvr.org> References: <20021009150346.GA62592@gvr.gvr.org> <20021010071506.DC06E54A1@bert.kts.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021010071506.DC06E54A1@bert.kts.org> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Oct 10, 2002 at 09:15:06AM +0200, Hellmuth Michaelis wrote: > Guido van Rooij wrote: > > > Would it be possible to use the i4b software to sniff the isdn bus > > and thus record phone conversations that are taking place (from > > a switch on the same bus). > > Yes. However, it will not work out of the box. What should be done in your opinion? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Oct 10 8:15:12 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E62237B410 for ; Thu, 10 Oct 2002 08:15:10 -0700 (PDT) Received: from fep02-svc.swip.net (fep02.swip.net [130.244.199.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FBCF43E91 for ; Thu, 10 Oct 2002 08:15:08 -0700 (PDT) (envelope-from hselasky@c2i.net) Received: from mta-int.swip.net ([192.168.145.28]) by fep02-svc.swip.net with SMTP id <20021010151506.MYTL122.fep02-svc.swip.net@mta-int.swip.net>; Thu, 10 Oct 2002 17:15:06 +0200 X-Originating-IP: [128.39.202.148] From: To: prallon@tmp.com.br Cc: freebsd-isdn@freebsd.org Subject: Re: New ihfc driver Date: Thu, 10 Oct 2002 17:15:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20021010151506.MYTL122.fep02-svc.swip.net@mta-int.swip.net> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > Fra: Sergio de Souza Prallon > Dato: 2002/10/07 Mon PM 06:57:49 CEST > Til: hselasky@c2i.net > CC: freebsd-isdn@freebsd.org > Emne: Re: New ihfc driver > > Hello, > > From the fragment below I noticed that your driver also works with > the Tiger chips. In fact,if I understood right, it can replace the > entire set of layer drivers. Apparently you tried very hard to > eliminate duplicated code spread among the various drivers, what is, > IMHO, a `Good Thing' (tm). The only critic I do is the legibility > of the code. In a brief look I've made, I didn't manage to grasp how > the gears of your "macro driver programing language" work under the > hood. There isn't another, a bit more readable, way around it? > > Do you have a -STABLE version of your driver? > I want to give it a try but an upgrade to -CURRENT is out of question. > May be I learn a thing or two from the experience as it was the case > with the HDLC macros. > > []'s > > -- > Prallon re: New ihfc Maybe there is need for a preprocessor that does more than just expanding macros? If you get the raw c++ code you might get a better picture. About -stable support there is no plans for such. If you want to use the code on a -stable machine, a substitution for mutexes must be found, like disabling interrupts, if -stable is not supporting mutexes. (This workaround is for single CPU systems.) Otherwise the system setup is very similar to your driver, which I assume compiles and runs on -stable. -- HPS ------------------------------------------------- WebMail fra Tele2 http://www.tele2.no ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message