From owner-freebsd-isdn Tue Jan 2 1:38: 5 2001 From owner-freebsd-isdn@FreeBSD.ORG Tue Jan 2 01:38:01 2001 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from gw2.dnepr.net (CoreGW2-TBone.dnepr.net [195.24.156.97]) by hub.freebsd.org (Postfix) with ESMTP id 0EE0F37B400 for ; Tue, 2 Jan 2001 01:37:58 -0800 (PST) Received: from dnepr.net (dnepr.net [195.24.156.98]) by gw2.dnepr.net (8.8.8/8.6.18/01) with ESMTP id LAA15990; Tue, 2 Jan 2001 11:37:33 +0200 (EET) Received: (from land@localhost) by dnepr.net (8.8.8/8.8.8) id LAA12169; Tue, 2 Jan 2001 11:37:27 +0200 (EET) Date: Tue, 2 Jan 2001 11:37:27 +0200 From: Andrey Lakhno To: freebsd-isdn@freebsd.org Cc: hm@hcs.de Subject: Re: 2 Teles PCI cards in one PC Message-ID: <20010102113727.B829@dnepr.net> Mail-Followup-To: freebsd-isdn@freebsd.org, hm@hcs.de References: <20010102093844.A10729@dnepr.net> <20010102085741.ED8243A1@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010102085741.ED8243A1@hcswork.hcs.de>; from hm@hcs.de on Tue, Jan 02, 2001 at 09:57:41 +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Hellmuth! On Tue, 02 Jan 2001, Hellmuth Michaelis wrote: > > I encountered with problem. I can't make work two ISDN Teles PCI adapters. > > When I working only with one of two cards things going ok. > > I wasn't even aware that the Teles PCI adapters work at all, i have never > seen them. How did you configure them, what does the boot messages (-v) say ? I forgot to attach README file to previous letter. -- Best regards, Andrey --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="README.itjc" A T T E N T I O N = = = = = = = = = THIS IS EXPERIMENTAL SOFTWARE. IT HAS AT LEAST ONE SERIOUS BUG WHICH CAUSES DATA CORRUPTION. THE INTENTION OF PUBLISHING IT AT THIS STAGE IS TO GATHER FEEDBACK FROM SKILLED VOLUNTEERS OUT ON THE NET WHICH ARE WILLING TO HELP US DEBUG THIS DRIVER. THIS IS NOT FOR THE LIGHTHEARTED. 1 - Description This is a driver for passive ISDN cards based on the TJNet Tiger300/320 PCI ASICs/Siemens ISAC ISDN chip combo. It is NOT for AMD based cards. It was developed in a FreeBSD 4.[12].X with versions 0.95 and 0.96 of ISND4BSD. It would be nice if it also worked on NetBSD or OpenBSD but I currently have not the knowledge or the resources to adapt or test it on these platforms; feedback (in the form of docs or patches) is welcome on this subject. I've successfully (in terms, I mean) tested it on a couple of NETJet-S cards equiped with Tiger300 and 320 ASICs. It also worked on a Teles PCI-TJ with Tiger300. I believe it can also work with other TJNet based cards. 2 - The BUG This driver seems to work well with phone or userland PPP. The problem shows up with kernel SPPP (ISP driver) when I try to send large (>200KB) files to a peer which is able to sustain a moderate to high transfer rate. When this happens, small parts of the upstream get replaced by what looks like previously received TCP ACKs after VJ decompression and TCP checksum performed. This garbage has another interesting property: it shows up on tcpdump, which means it is not being (directly) produced by the driver. My guess is that I have a dangling pointer somewhere that corrupted something in the kernel mbuf/if_queues control blocks. Another possibility is that I'm dealing with a race condition of some sort. I do not experience any problems at all while downloading from the net; only the uploads are afected. I have not tested it with IPR or Cisco HDLC: it may also exhibit other bugs with these drivers. 3 - How to install The driver is packaged as a recursive context diff against a vanilla 0.96b I4B distribution (as of 2000.10.10). To install follow theses steps. Create the /usr/local/src/i4b directory and `cd' to it. Unpack the I4B sources. Cd to /usr/local/src. Execute `patch -p < itjc_patches'. Cd to /usr/local/src/i4b/FreeBSD. Follow the instructions there to conclude the installation the usual way. NOTE: If you already have I4B in your kernel config file, be sure to update it from /usr/local/src/i4b/FreeBSD/CONFIG. 4 - Acknowledgements This driver would not exist at all if we didn't receive support from the following people: Hellmuth Michaelis, for writing I4B in the first place, and for providing very useful docs & pointers to get the job started. Hans Petter Selasky, for the software HDLC package and the time & efort spent to adapt it to my peculiar needs. Gary Jennejohn for the IFPI driver which I used as a very handy starting point for ITJC. The gang at Traverse Technologies (http://www.traverse.com.au/), specially Guy Ellis & Mike Woodhams for providing docs & pointers on Tiger ASICs and for sending 2 cards to help development and compatibility tests. 5 - How can you help First, if you live near Victoria (Australia) and have previous experience with I4B, you can help Traverse get their FreeBSD box going. They offered their ISDN benchmarking and certification hardware, but I was unable to use it till now, because I failed in `remote controlling' them in installing the stuff on a machine they have there. They are skilled in network, ISDN & the like but had never used *BSD before; I think that their *ix experience is mostly on Linux but they are willing to learn *BSD also, since they want to support their product on this platform. If you know network driver architecture or I4B from an inside perspective, you can have a look at the driver. Perhaps, I'm doing some silly mistake that someone went over before. Even if you don't have that flash of intuition I'm looking for, sugestions on the design are welcome. Needless to say, bug reports are even more welcome. -- Sergio de Souza Prallon TMP Consultoria S/C Ltda prallon@tmp.com.br --Kj7319i9nmIyA2yE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message