From owner-freebsd-isdn Sun Dec 14 21:26:07 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA20833 for isdn-outgoing; Sun, 14 Dec 1997 21:26:07 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from horizon.ppp.ripco.net (horizon.ppp.ripco.net [208.216.242.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA20828 for ; Sun, 14 Dec 1997 21:25:52 -0800 (PST) (envelope-from aphor@horizon.ppp.ripco.net) Received: from horizon.ppp.ripco.net (horizon.ppp.ripco.net [208.216.242.26]) by horizon.ppp.ripco.net (8.8.7/8.8.5) with ESMTP id XAA20100 for ; Sun, 14 Dec 1997 23:22:44 -0600 (CST) Message-ID: <3494BEA2.238F2F07@horizon.ppp.ripco.net> Date: Mon, 15 Dec 1997 05:22:43 +0000 From: Jeremy McMillan Reply-To: aphor@ripco.com Organization: horizon.interlabs.org X-Mailer: Mozilla 4.03 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: [Fwd: What kind of serial card should I use with ISDN and FreeBSD] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a response to a question not specific to FreeBSD or ISDN, but is more about connecting high-speed serial devices (in gerneral) to PCs. Peter Haight wrote: > I just got an ISDN line and I'm using a 486/33 with FreeBSD on it to route > our internal network to the outside world. Anyway, my 486 has a 16450 UART > serial card. My understanding is that there are many limitations to this > kind of card and I am wondering what my options are in terms of upgrades > that work with FreeBSD. The 16xxx number refers to the type of FIFO buffer chip (UART) that takes data from your computer's processor and pumps it out a serial port interface. Higher numbers mean later standards and higher speeds. A 16450 will not accept any more than 9600bps. A 16550 will take 57600 bps at a time, and later UARTs will allow higher speeds on up. > The ISDN adapter I'm using is a 3Com ImpactIQ and it says that with > compression it can get speeds up to 230kbps. I'm getting about 85kbps with > it now. In general, compression is advertised at about a 2:1 ratio, and thus I'm guessing your TA has 2 "B" (data) channels at 64Kbps each. Your computer can't even use the bandwidth of one of these channels at 9.6Kbps. Your serial port is a major bottleneck. > The 3Com ImpactIQ came with advetisements for serial cards with 16750 UARTS > on them. Do these work with FreeBSD? Does anyone have any opinions on them? You need one to get your money's worth out of your ISDN line. Get one, but shop around. If you had bought an internal TA, it would have had it's own UART built in. If you bought an ISDN router, you could have just plugged the thing into your favorite ethernet port and you'd be practically up and running. You took the hard way, and now you have to worry about adding a serial card with all of the address line/IRQ/DMA problems associated with it. I hope your 486 is cooperative, though you will likely get it working without unreasonable pains. BTW: Pay extra for a good IEEE certified serial cable rated for 230+kbps. The higher the rated speed the better, since you will have a royal pain in the neck if your cable introduces data errors. --- Jeremy McMillan | Finger for PGP Pursuant to US Code, Title 47, Chapter 5, Subchapter II, '227, any and all unsolicited commercial E-mail sent to this address is subject to a download and archival fee in the amount of $500 US. E-mailing denotes acceptance of these terms. From owner-freebsd-isdn Mon Dec 15 02:28:31 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA15679 for isdn-outgoing; Mon, 15 Dec 1997 02:28:31 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from strange.il.fontys.nl (root@strange.il.fontys.nl [145.85.127.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA15666 for ; Mon, 15 Dec 1997 02:28:20 -0800 (PST) (envelope-from edwinm@charm.il.fontys.nl) Received: from charm.il.fontys.nl (edwinm@charm.il.fontys.nl [145.85.127.2]) by strange.il.fontys.nl (8.8.5/8.8.5) with ESMTP id LAA25384 for ; Mon, 15 Dec 1997 11:27:13 +0100 (CET) Received: (from edwinm@localhost) by charm.il.fontys.nl (8.8.5/8.7.3) id LAA25441 for freebsd-isdn@freebsd.org; Mon, 15 Dec 1997 11:28:12 +0100 (CET) From: Edwin Mons Message-Id: <199712151028.LAA25441@charm.il.fontys.nl> Subject: Teles 16/3 To: freebsd-isdn@FreeBSD.ORG Date: Mon, 15 Dec 1997 11:28:12 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. Has anyone installed and used the bISDN patches with a Teles 16/3 interface? I didn't get to it, yet. Since I don't have access to a machine with a Teles card until Thursday, I'd like to head about it from others. Where are the catches, tricky parts, etc.? Has anyone succeded in using SyncPPP with a Teles card? Grtz, Edwinm -----8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<----- public PGP key: send an E-mail with subject "auto-reply" and "send pgp-key" in the messagebody From owner-freebsd-isdn Mon Dec 15 05:30:44 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA27262 for isdn-outgoing; Mon, 15 Dec 1997 05:30:44 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA27231 for ; Mon, 15 Dec 1997 05:30:20 -0800 (PST) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0xha9s-0032hKC; Mon, 15 Dec 97 14:02 MET Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Mon, 15 Dec 1997 13:31:13 +0100 (MET) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for freebsd-isdn@FreeBSD.ORG; Mon, 15 Dec 1997 13:22:47 +0100 (CET) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Teles 16/3 In-Reply-To: <199712151028.LAA25441@charm.il.fontys.nl> from Edwin Mons at "Dec 15, 97 11:28:12 am" To: edwinm@il.fontys.nl (Edwin Mons) Date: Mon, 15 Dec 1997 13:22:47 +0100 (CET) Cc: freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Edwin Mons wrote: > Has anyone installed and used the bISDN patches with a Teles 16/3 interface? I run a 16.3, but without the PPP patches. It runs without problems for so long now, that i don't remember when i installed it. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe "Those who can, do. Those who can't, talk. And those who can't talk, talk about talking." (B. Shaw) From owner-freebsd-isdn Mon Dec 15 09:39:26 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16915 for isdn-outgoing; Mon, 15 Dec 1997 09:39:26 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA16888 for ; Mon, 15 Dec 1997 09:39:08 -0800 (PST) (envelope-from kevinb@relay.csd.SGI.COM) Received: from odin.corp.sgi.com (odin.corp.sgi.com [192.26.51.194]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id JAA29470 for <@external-mail-relay.sgi.com:freebsd-isdn@freebsd.org>; Mon, 15 Dec 1997 09:39:18 -0800 env-from (kevinb@rock.csd.sgi.com) Received: from rock.csd.sgi.com by odin.corp.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1502/951211.SGI) for <@fddi-odin.corp.sgi.com:freebsd-isdn@freebsd.org> id JAA11597; Mon, 15 Dec 1997 09:38:51 -0800 Received: from oblivion.csd.sgi.com by rock.csd.sgi.com via ESMTP (950413.SGI.8.6.12/910805.SGI) for <@rock.csd.sgi.com:freebsd-isdn@freebsd.org> id JAA05090; Mon, 15 Dec 1997 09:38:50 -0800 Received: from csd.sgi.com by oblivion.csd.sgi.com via ESMTP (950413.SGI.8.6.12/911001.SGI) for id JAA20519; Mon, 15 Dec 1997 09:38:49 -0800 Message-ID: <34956B29.97070B13@csd.sgi.com> Date: Mon, 15 Dec 1997 09:38:49 -0800 From: "Kevin L. Brokaw" Organization: Silicon Graphics X-Mailer: Mozilla 4.03C-SGI [en] (X11; I; IRIX 6.3 IP32) MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: Re: [Fwd: What kind of serial card should I use with ISDN and FreeBSD] References: <3494BEA2.238F2F07@horizon.ppp.ripco.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeremy McMillan wrote: > The 16xxx number refers to the type of FIFO buffer chip (UART) that takes data > from your computer's processor and pumps it out a serial port interface. > Higher numbers mean later standards and higher speeds. A 16450 will not accept > any more than 9600bps. A 16550 will take 57600 bps at a time, and later UARTs > will allow higher speeds on up. I would have to disagree with that overall description of the chip model versus interface speeds. An original 8580 UART is pretty much limited to 9600 BPS, but a 16450 UART can theoretically run at a DTE rate of up to 115,200 BPS. The difference between the 16450 and the 16550 is that the 16550 adds a FIFO buffer. Both the 16450 and 16550 are capable of handling the same serial port rates, but with a machine like a 486/33, you are going to drop data on a 16450 port at high rates of speed, since the CPU most probably can't cycle quickly enough to service the serial port interrupt in a timely manner. The FIFO buffer added in the 16550 allows for some latency in handling the interrupt without losing data. I have been using a 16450-based serial board on an AMD 5x86-133 system for some time, at a port rate of 38400 without losing any data. It's simply a matter of how fast the system is, and how loaded it is. It's a crapshoot. > > > The ISDN adapter I'm using is a 3Com ImpactIQ and it says that with > > compression it can get speeds up to 230kbps. I'm getting about 85kbps with > > it now. > > In general, compression is advertised at about a 2:1 ratio, and thus I'm > guessing your TA has 2 "B" (data) channels at 64Kbps each. Your computer can't > even use the bandwidth of one of these channels at 9.6Kbps. Your serial port > is a major bottleneck. Another place to look is to the PPP protocol negotiation taking place. Is compression even being enabled on the link? There are so many different compression algorithm available under PPP, that a non-optimum one may be selected in negotiation, or if the client only supports one (VJ, for example), and the host does not support that particular algorithm, the link may in fact be running with no compression at all. Most modern PPP implementations can achieve optimum compression close to 4:1. Depending upon your system setup (and if you're using a 16450 chip, this is advisable), it may be best to disable all hardware compression in the ISDN device, and rely upon software compression within the PPP protocol. This will take some of the load off the serial port while still maintaining decent throughput. > > > The 3Com ImpactIQ came with advetisements for serial cards with 16750 UARTS > > on them. Do these work with FreeBSD? Does anyone have any opinions on them? > > You need one to get your money's worth out of your ISDN line. Get one, but > shop around. If you had bought an internal TA, it would have had it's own UART > built in. If you bought an ISDN router, you could have just plugged the thing > into your favorite ethernet port and you'd be practically up and running. You > took the hard way, and now you have to worry about adding a serial card with > all of the address line/IRQ/DMA problems associated with it. I hope your 486 > is cooperative, though you will likely get it working without unreasonable > pains. There's no *technical* reason I see why a 16750 card won't work, since you'd simply replace the existing serial port board with it, and presumably use the previous existing IRQ and I/O port address (most serial boards don't use DMA). However, I don't see support in my release (which is still 2.2.2, so I'm not sure about 2.2.5) for a serial rate above 115200. That may be a limiting factor in getting full-bore throughput. I would agree with the comment above that going with an ethernet-based solution like a low-end Ascend Pipeline would probably be a better solution for full rate throughput. -- Kevin Brokaw (kevinb@sgi.com) | Cynic (SIN-ick) n. : Member, Technical Staff - WebForce | Someone who, upon Silicon Graphics Computer Systems | smelling the flowers, Customer & Professional Services | looks for the casket. From owner-freebsd-isdn Mon Dec 15 10:15:35 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA20793 for isdn-outgoing; Mon, 15 Dec 1997 10:15:35 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from unlisys.unlisys.NET (mail.unlisys.net [195.21.255.252]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA20763 for ; Mon, 15 Dec 1997 10:15:23 -0800 (PST) (envelope-from root@mscu.snafu.de) Received: by unlisys.unlisys.NET (Smail3.2.0.96inx) from desert.de (194.64.152.210) with smtp id ; Mon, 15 Dec 1997 19:15:04 +0100 (MET) Received: by desert.de with UUCP (Smail3.1.29.1 #18) id m0xheYh-000TQ0C; Mon, 15 Dec 97 18:43 MET Received: (from root@localhost) by mscu.snafu.de (8.8.8/8.8.5) id SAA03064 for freebsd-isdn@FreeBSD.ORG; Mon, 15 Dec 1997 18:46:32 +0100 (CET) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 15 Dec 1997 18:14:22 +0100 (CET) Organization: Private FreeBSD site (UUCP) From: Matthias Schuendehuette To: ISDN-Mailinglist Subject: PPP over (b)ISDN Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, maybe I´m too stupid but I cannot get PPP via ISDN up and running.... First of all, I installed bisdn 0.97 on my TELES 16.3 (w/o PnP!) to connect to my Machine at work via RawIP and it works flawlessly - even today. Then I installed the PPP-Patches (BISDN-ppp-FreeBSD2.2.tgz) and tried to connect to my provider (which works under CALDERA with isdn4linux and under OS/2 with ISDNPM, so the provider seems off duty). I did a ´ifconfig ppp0 up´ and ´route add default -iface ppp0´ and ´ping 194.64.64.1´ (which is the nameserver of my provider) bisdnd dialed, isdnpppd came up and nothing happens furthermore..... After I squeezed syslogd a bit the following output from isdnpppd appeared: Dec 6 23:18:55 mscu isdnpppd[2236]: isdnpppd 2.2.0 started by root, uid 0 Dec 6 23:18:55 mscu isdnpppd[2236]: Using interface ppp0 Dec 6 23:18:55 mscu isdnpppd[2236]: Connect: ppp0 <--> /dev/tty Dec 6 23:18:55 mscu isdnpppd[2236]: ioctl1: Broken pipe Dec 6 23:18:55 mscu isdnpppd[2236]: Couldn't restore device fd flags: Bad file descriptor Dec 6 23:18:55 mscu isdnpppd[2236]: Exit. I posted to de.comp.os.bsd and a friendly guy told me to do a ´ifconfig ppp0 inet 10.0.0.1 10.0.0.2 up´ ´ping 10.0.0.2´ with the defaultroute-option in the isdnpppd-command but all what happens was: "ping: sendto: Network is down" and bisdnd didn´t even THINK to dial.... So, after all RawIP via ISDN works, PPP via Modem (ppp2) works but PPP via ISDN has its difficulties (mildly spoken :-). Sure, that are not all informations necessary to solve the problem but is there anybody outside to help me? Ciao/BSD - Matthias ********************************************************************* Matthias Schündehütte E-Mail: Matthias Schuendehuette Solmsstrasse 44 Phone: +49-30-69409824 D-10961 Berlin Data/Fax: +49-30-69409825 GERMANY This message was sent by XF-Mail on FreeBSD 2.2.5-STABLE ********************************************************************** From owner-freebsd-isdn Mon Dec 15 10:30:33 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA22608 for isdn-outgoing; Mon, 15 Dec 1997 10:30:33 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from teligent.se (iservern.teligent.se [194.17.198.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA22473 for ; Mon, 15 Dec 1997 10:29:11 -0800 (PST) (envelope-from jakob@teligent.se) Received: from datorn.teligent.se (datorn.teligent.se [192.168.2.31]) by teligent.se (8.7/8.6.12) with SMTP id TAA27949 for ; Mon, 15 Dec 1997 19:28:55 +0100 Date: Mon, 15 Dec 1997 16:25:29 +0100 (CET) From: Jakob Alvermark To: freebsd-isdn@FreeBSD.ORG Subject: CAPI driver? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA22587 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello isdn:ers! I'm currently running a ZyXEL omni.net TA. I works great, I must say, with MLPPP and BOD and all that stuff. I also use it's a/b ports to make and recieve voice calls. That part work very well too. Now I'm interested in if there is CAPI drivers available for FreeBSD, or if there is some develompent going on. I would be great to have like a "control panel", where I can see which B-channel that are in use, who is calling on my voice number while I'm on the internet and so on.. TIA /Jakob Alvermark ------------------------------------------------------- Teligent AB, P.O. Box 213, S-149 23 Nynäshamn, Sweden Telephone +46-(0)8 520 660 00 * Fax +46-(0)8 520 193 36 Direct +46-(0)8 520 660 32 * GSM +46-(0)70 792 16 57 From owner-freebsd-isdn Mon Dec 15 13:22:36 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA15861 for isdn-outgoing; Mon, 15 Dec 1997 13:22:36 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA15823 for ; Mon, 15 Dec 1997 13:22:12 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.8/8.6.9) with ESMTP id WAA22541; Mon, 15 Dec 1997 22:22:00 +0100 (CET) Message-Id: <199712152122.WAA22541@peedub.muc.de> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jakob Alvermark cc: freebsd-isdn@FreeBSD.ORG Subject: Re: CAPI driver? Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 15 Dec 1997 16:25:29 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Mon, 15 Dec 1997 22:21:59 +0100 From: Gary Jennejohn Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA15838 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jakob Alvermark writes: >Hello isdn:ers! > >I'm currently running a ZyXEL omni.net TA. I works great, I must say, with >MLPPP and BOD and all that stuff. I also use it's a/b ports to make and >recieve voice calls. That part work very well too. Now I'm interested in >if there is CAPI drivers available for FreeBSD, or if there is some >develompent going on. I would be great to have like a "control panel", >where I can see which B-channel that are in use, who is calling on my >voice number while I'm on the internet and so on.. > no CAPI in FreeBSD. Want to write it ? --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com From owner-freebsd-isdn Mon Dec 15 14:31:56 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22023 for isdn-outgoing; Mon, 15 Dec 1997 14:31:56 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from iafnl.es.iaf.nl (root@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA21491 for ; Mon, 15 Dec 1997 14:25:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA11880 (5.67b/IDA-1.5 for freebsd-isdn@FreeBSD.ORG); Mon, 15 Dec 1997 22:55:28 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id WAA10057; Mon, 15 Dec 1997 22:30:38 +0100 (MET) From: Wilko Bulte Message-Id: <199712152130.WAA10057@yedi.iaf.nl> Subject: Re: Teles 16/3 To: hm@kts.org Date: Mon, 15 Dec 1997 22:30:38 +0100 (MET) Cc: edwinm@il.fontys.nl, freebsd-isdn@FreeBSD.ORG In-Reply-To: from "Hellmuth Michaelis" at Dec 15, 97 01:22:47 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Hellmuth Michaelis wrote... > Edwin Mons wrote: > > > Has anyone installed and used the bISDN patches with a Teles 16/3 interface? > > I run a 16.3, but without the PPP patches. It runs without problems for so > long now, that i don't remember when i installed it. I have one running with the 16.3 and PPP. Works ok. It was installed something like 3/4 of a year ago. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ---------------- Support your local daemons: run [Free,Net]BSD Unix ------ From owner-freebsd-isdn Mon Dec 15 16:39:33 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA02907 for isdn-outgoing; Mon, 15 Dec 1997 16:39:33 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from wartch.rih.org (ppp-206-170-3-18.okld03.pacbell.net [206.170.3.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA02848 for ; Mon, 15 Dec 1997 16:39:03 -0800 (PST) (envelope-from peterh@wartch.rih.org) Received: from wartch.rih.org (localhost [127.0.0.1]) by wartch.rih.org (8.8.8/8.8.8) with ESMTP id IAA07930 for ; Mon, 15 Dec 1997 08:37:36 -0800 (PST) (envelope-from peterh@wartch.rih.org) Message-Id: <199712151637.IAA07930@wartch.rih.org> To: freebsd-isdn@FreeBSD.ORG Subject: Re: What kind of serial card should I use with ISDN and FreeBSD In-reply-to: Your message of "Mon, 15 Dec 1997 05:22:43 GMT." <3494BEA2.238F2F07@horizon.ppp.ripco.net> Date: Mon, 15 Dec 1997 08:37:35 -0800 From: Peter Haight Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >This is a response to a question not specific to FreeBSD or ISDN, but is more >about connecting high-speed serial devices (in gerneral) to PCs. True, but I was also asking whether there would be any problems with using a 16750 UART with FreeBSD. I'm guessing that the speedup is transparent to the OS, but I want to confirm. For example, I'm not sure whether ppp will work at a set speed of 230400. I tried it, but when I sent the AT command that forced the modem to 230400 speed, I was unable to communicate with it any more. I'm assuming that this is because it is ridiculous to ask a 16450 to do that. > You need one to get your money's worth out of your ISDN line. Get one, but >shop around. If you had bought an internal TA, it would have had it's own UART >built in. If you bought an ISDN router, you could have just plugged the thing >into your favorite ethernet port and you'd be practically up and running. You >took the hard way, and now you have to worry about adding a serial card with >all of the address line/IRQ/DMA problems associated with it. I hope your 486 >is cooperative, though you will likely get it working without unreasonable >pains. Of course, there are few, if any, internal TAs supported by FreeBSD and they are all way more expensive than the modem I bought as part of a package deal with the ISDN line. Of course routers are the most expensive option. My parents have a Cisco ISDN router which was a pain in the rear to setup because we wanted to use it with two different ISPs (one for work and one for recreation) and it doesn't seem like it was really designed to do that. I think the serial ISDN modem is nice. It was really easy to setup and after buying the serial card it will have only run me $150. From owner-freebsd-isdn Mon Dec 15 20:01:34 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18653 for isdn-outgoing; Mon, 15 Dec 1997 20:01:34 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from horizon.ppp.ripco.net (horizon.ppp.ripco.net [208.216.242.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18639 for ; Mon, 15 Dec 1997 20:01:22 -0800 (PST) (envelope-from aphor@horizon.ppp.ripco.net) Received: from horizon.ppp.ripco.net (horizon.ppp.ripco.net [208.216.242.26]) by horizon.ppp.ripco.net (8.8.7/8.8.5) with ESMTP id VAA21240 for ; Mon, 15 Dec 1997 21:58:08 -0600 (CST) Message-ID: <3495FC4E.21738365@horizon.ppp.ripco.net> Date: Tue, 16 Dec 1997 03:58:07 +0000 From: Jeremy McMillan Reply-To: aphor@ripco.com Organization: horizon.interlabs.org X-Mailer: Mozilla 4.03 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: Serial UARTs for ISDN "modems" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On FreeBSD support for ISDN... There are reasons to choose the serial interface ISDN TA (which people like to call 'ISDN modems') over a router or an internal TA card, but there are limitations imposed by the FreeBSD serial i/o device code. Peter Haight wrote: > Of course, there are few, if any, internal TAs supported by FreeBSD and they > are all way more expensive than the modem I bought as part of a package deal > with the ISDN line. Of course routers are the most expensive option. My > parents have a Cisco ISDN router which was a pain in the rear to setup > because we wanted to use it with two different ISPs (one for work and one for > recreation) and it doesn't seem like it was really designed to do that. > > I think the serial ISDN modem is nice. It was really easy to setup and after > buying the serial card it will have only run me $150. > >This is a response to a question not specific to FreeBSD or ISDN, but is more > >about connecting high-speed serial devices (in gerneral) to PCs. > > True, but I was also asking whether there would be any problems with using a > 16750 UART with FreeBSD. I'm guessing that the speedup is transparent to the > OS, but I want to confirm. > > For example, I'm not sure whether ppp will work at a set speed of 230400. I > tried it, but when I sent the AT command that forced the modem to 230400 > speed, I was unable to communicate with it any more. I'm assuming that this > is because it is ridiculous to ask a 16450 to do that. If you have questions about open systems, I like to go to the source. What a luxury! >From /usr/src/sys/i386/isa/sio.c > /* > * Serial driver, based on 386BSD-0.1 com driver. > * Mostly rewritten to use pseudo-DMA. > * Works for National Semiconductor NS8250-NS16550AF UARTs. > * COM driver, based on HP dca driver. > * > * Changes for PC-Card integration: > * - Added PC-Card driver table and handlers > */ > which further specifies: > static struct speedtab comspeedtab[] = { > { 0, 0 }, > { 50, COMBRD(50) }, > { 75, COMBRD(75) }, > { 110, COMBRD(110) }, > { 134, COMBRD(134) }, > { 150, COMBRD(150) }, > { 200, COMBRD(200) }, > { 300, COMBRD(300) }, > { 600, COMBRD(600) }, > { 1200, COMBRD(1200) }, > { 1800, COMBRD(1800) }, > { 2400, COMBRD(2400) }, > { 4800, COMBRD(4800) }, > { 9600, COMBRD(9600) }, > { 19200, COMBRD(19200) }, > { 38400, COMBRD(38400) }, > { 57600, COMBRD(57600) }, > { 115200, COMBRD(115200) }, > { -1, -1 } > I don't know what happens if you try to specify -1 for your serial port speed, but the other choices seem obvious enough. Now each B channel will allow 64Kbps (65536bps), and hardware compression will get you twice that for data like long text transmissions. Most TA's are now (1997-98) dual B channel models, meaning the demand for through put on a serial port can reach about 262144bps. Source files (sio.c) seem to limit FreeBSD's compatibility. Since raw DCE data rates of paired B channels can reach 131072bps, and the serial port's limit is 115200bps, there's an obvious bottleneck going on here. As for using faster hardware: 16750UARTs may or may not function like 16550UARTs to FreeBSD, and even if they do, the software doesn't expllicitly support dual B ISDN at full blast with a serial TA. If you use a 16550 at 115200bps, then turn off the data compression in your TA, and use software compression like PPP's VJ compression. Then you will probably be able to squeak by. 16450s won't go fast enough, and we need to ask the experts whether the device code will support a 16750UART. My guess is "not really". --- Jeremy McMillan | Finger for PGP Pursuant to US Code, Title 47, Chapter 5, Subchapter II, '227, any and all unsolicited commercial E-mail sent to this address is subject to a download and archival fee in the amount of $500 US. E-mailing denotes acceptance of these terms. From owner-freebsd-isdn Mon Dec 15 23:52:18 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA04493 for isdn-outgoing; Mon, 15 Dec 1997 23:52:18 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA04479 for ; Mon, 15 Dec 1997 23:52:10 -0800 (PST) (envelope-from sandbec@ns1.yes.no) Received: (from sandbec@localhost) by ns1.yes.no (8.8.7/8.8.7) id HAA29818; Tue, 16 Dec 1997 07:51:57 GMT Message-ID: <19971216085157.03521@follonett.no> Date: Tue, 16 Dec 1997 08:51:57 +0100 From: Christian Sandberg To: aphor@ripco.com Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Serial UARTs for ISDN "modems" References: <3495FC4E.21738365@horizon.ppp.ripco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: <3495FC4E.21738365@horizon.ppp.ripco.net>; from Jeremy McMillan on Tue, Dec 16, 1997 at 03:58:07AM +0000 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 16, 1997 at 03:58:07AM +0000, Jeremy McMillan wrote: >Since raw DCE data rates of paired B channels can reach 131072bps, and the serial >port's limit is 115200bps, there's an obvious bottleneck going on here. As for >using faster hardware: 16750UARTs may or may not function like 16550UARTs to >FreeBSD, and even if they do, the software doesn't expllicitly support dual B ISDN >at full blast with a serial TA. Thats no problem at all. I have been using a Zyxel Omni.net for about 1 year and it works great with the Zyxel IO card. FreeBSD probes the IO card as a 16550A: sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A With the MS-DOS software that comes with the card you can f.ex. set the card to double the speed. If you set PPP to use 115200 you get 230400. Here in Norway you can buy the IO card for about $20. I get about 13-14 kb/s both ways (uploading and downloading at the same time) without any FIFO overruns or PPP/HDLC errors on my 486/66 FreeBSD networkserver at home.. The only problem I've had with the Zyxel is that is somethimes (once every month or something) get too hot. Then it reports "NO CARRIER" on ATD commands. I have to turn it of for some minutes to get it to dial out again. -- Christian Sandberg | Yes Interactive AS | voice: +47 64 855200 email: christian@yes.no | http://www.yes.no/ | fax: +47 64 855201 From owner-freebsd-isdn Tue Dec 16 00:31:44 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA06968 for isdn-outgoing; Tue, 16 Dec 1997 00:31:44 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from teligent.se (iservern.teligent.se [194.17.198.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA06950 for ; Tue, 16 Dec 1997 00:31:35 -0800 (PST) (envelope-from jakob@teligent.se) Received: from datorn.teligent.se (datorn.teligent.se [192.168.2.31]) by teligent.se (8.7/8.6.12) with SMTP id JAA07932; Tue, 16 Dec 1997 09:31:18 +0100 Date: Tue, 16 Dec 1997 06:27:59 +0100 (CET) From: Jakob Alvermark To: Gary Jennejohn cc: freebsd-isdn@FreeBSD.ORG Subject: Re: CAPI driver? In-Reply-To: <199712152122.WAA22541@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id AAA06954 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 15 Dec 1997, Gary Jennejohn wrote: > >I'm currently running a ZyXEL omni.net TA. I works great, I must say, with > >MLPPP and BOD and all that stuff. I also use it's a/b ports to make and > >recieve voice calls. That part work very well too. Now I'm interested in > >if there is CAPI drivers available for FreeBSD, or if there is some > >develompent going on. I would be great to have like a "control panel", > >where I can see which B-channel that are in use, who is calling on my > >voice number while I'm on the internet and so on.. > > > > no CAPI in FreeBSD. Want to write it ? I don't have any experience in writing drivers. But it could be a fun projekt to learn. It would not be a very fast moving projekt though, due to my lack of time. Maybe I'm not all alone on wanting CAPI? Maybe there is more people interested in writing CAPI driver? I think this is a two or more persons projekt. Is there CAPI drivers for unix's? (Linux?) /Jakob Alvermark ------------------------------------------------------- Teligent AB, P.O. Box 213, S-149 23 Nynäshamn, Sweden Telephone +46-(0)8 520 660 00 * Fax +46-(0)8 520 193 36 Direct +46-(0)8 520 660 32 * GSM +46-(0)70 792 16 57 From owner-freebsd-isdn Tue Dec 16 00:52:18 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA08393 for isdn-outgoing; Tue, 16 Dec 1997 00:52:18 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.49.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA08369 for ; Tue, 16 Dec 1997 00:52:10 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2236 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 16 Dec 1997 09:52:03 +0100 (MET) (Smail-3.2.0.97 1997-Aug-19 #16 built 1997-Oct-22) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0xhskJ-0000EXC; Tue, 16 Dec 97 09:52 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: CAPI driver? To: jakob@teligent.se (Jakob Alvermark) Date: Tue, 16 Dec 1997 09:52:55 +0100 (MET) Cc: garyj@muc.de, freebsd-isdn@FreeBSD.ORG In-Reply-To: from "Jakob Alvermark" at "Dec 16, 97 06:27:59 am" Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL15 (25)] Content-Type: text Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From the keyboard of Jakob Alvermark: > I don't have any experience in writing drivers. But it could be a fun > projekt to learn. It would not be a very fast moving projekt though, due > to my lack of time. Maybe I'm not all alone on wanting CAPI? Maybe there > is more people interested in writing CAPI driver? I think this is a two or > more persons projekt. Is there CAPI drivers for unix's? (Linux?) For Linux there is a CAPI interface available for the AVM B1 card (which already has sort of CAPI i/f onboard). As far as i remember it, there was a discussion in a newsgroup going on where some people wanted to add a general CAPI i/f to isdn4linux but i don't know if they did made any progress. The difficulty in producing a CAPI for BSD would be the lack of STREAMS in the BSD kernel(s) - when you have a look at CAPI 2.0 (or even CAPI 1.1) you will see that the Unix CAPI specification is STREAMS based, so before implementing a CAPI you will need to implement STREAMS. A CAPI would be a highly welcome thing, but i doubt we'll ever have one due to the huge amount of design and coding work necessary to get one. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm@hcs.de 22457 Hamburg WWW http://www.hcs.de From owner-freebsd-isdn Sat Dec 20 15:18:52 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA21602 for isdn-outgoing; Sat, 20 Dec 1997 15:18:52 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from carpe.net (news.carpe.net [194.162.243.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA21596 for ; Sat, 20 Dec 1997 15:18:34 -0800 (PST) (envelope-from grefen@carpe.net) Received: from helva.grefen.carpe.net (root@helva.grefen.carpe.net [194.162.243.129]) by carpe.net (8.8.6/8.8.6) with ESMTP id AAA26684; Sun, 21 Dec 1997 00:17:55 +0100 (MET) Received: from hex.grefen.carpe.net (root@hex [194.162.243.130]) by helva.grefen.carpe.net (8.7.5/8.7.3) with ESMTP id AAA03776; Sun, 21 Dec 1997 00:02:08 +0100 (MET) Received: from hex.grefen.carpe.net (grefen@localhost [127.0.0.1]) by hex.grefen.carpe.net (8.7.3/8.7.3) with ESMTP id AAA03260; Sun, 21 Dec 1997 00:02:06 +0100 (MET) To: hm@hcs.de Cc: jakob@teligent.se (Jakob Alvermark), garyj@muc.de, freebsd-isdn@FreeBSD.ORG Subject: Re: CAPI driver? Reply-To: grefen@carpe.net In-reply-to: Hellmuth Michaelis's message of Tue, 16 Dec 97 09:52:55 +0100. References: Date: Sun, 21 Dec 1997 00:02:05 +0100 Message-ID: <3257.882658925@hex.grefen.carpe.net> From: Stefan Grefen Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Hellmuth Michaelis wrote: > From the keyboard of Jakob Alvermark: > > The difficulty in producing a CAPI for BSD would be the lack of STREAMS > in the BSD kernel(s) - when you have a look at CAPI 2.0 (or even CAPI 1.1) > you will see that the Unix CAPI specification is STREAMS based, so before > implementing a CAPI you will need to implement STREAMS. Depends on what you need/want. It can be done in the socket enviroment for apllications (source compatible). The only problem is the Streams clone facility, but I have that already. > > A CAPI would be a highly welcome thing, but i doubt we'll ever have one > due to the huge amount of design and coding work necessary to get one. YUP, I can only offer my clone device but thats it (no spare time in the near/medium future ...) On the other hand wha would we gain? We could compile applications build for CAPI drivers, we couldn't use CAPI driver coming with the cards (unless we present a MSDOS/BIOS enviroment too). Stefan > > hellmuth > -- > Hellmuth Michaelis Tel +49 40 559747-70 > HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 > Oldesloer Strasse 97-99 Mail hm@hcs.de > 22457 Hamburg WWW http://www.hcs.de -- Stefan Grefen Am Hummertal 4, 55283 Nierstein, Germany grefen@carpe.net +49 6133 927484 Fax:+49 6133 927486 Idiot, n.: A member of a large and powerful tribe whose influence in human affairs has always been dominant and controlling. -- Ambrose Bierce, "The Devil's Dictionary"