From owner-freebsd-stable Wed May 19 16:35:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from queasy.outpost.co.nz (outpost.inspire.net.nz [203.96.157.150]) by hub.freebsd.org (Postfix) with SMTP id 130B915164 for ; Wed, 19 May 1999 16:35:41 -0700 (PDT) (envelope-from crh@outpost.co.nz) Received: (qmail 5545 invoked from network); 19 May 1999 23:35:29 -0000 Received: from officedonkey.outpost.co.nz (HELO officedonkey) (192.168.1.3) by queasy.outpost.co.nz.1.168.192.in-addr.arpa with SMTP; 19 May 1999 23:35:29 -0000 Comments: Authenticated sender is From: "Craig Harding" Organization: Outpost Digital Media Ltd To: blitz@pdq.net Date: Thu, 20 May 1999 11:35:11 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: ISDN Terminal adapter no work Reply-To: isdn@freebsd.org Cc: stable@freebsd.org, isdn@freebsd.org In-reply-to: X-mailer: Pegasus Mail for Windows (v2.52) Message-Id: <19990519233544.130B915164@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Clay Smith wrote: > This is a multi-part message in MIME format. > > - ------=_NextPart_000_0007_01BEA175.949FD1A0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable Is it really necessary to send HTML versions of your email? > I have been working on a machine running FreeBSD 3.1-Stable and have > failed to get the ISDN terminal adapter that is hooked up to it to > work correctly. There is a generic 56k on com2 that works great. > On com 1, the ISDN terminal adapter is just...dead. PPP will not > communicate with it. The terminal adapter has been tested and > works fine on other machines, just not FreeBSD. Is there > something special about ISDN adapters that I don't know about? > (note: the terminal adapter is external and the modem is internal, > not that that makes a lot of difference as long as the ports are > set up right in the bios/jumpers) Most TA's act just like very fast modems. Have you configured PPP to do all the right initialisation of the TA? It should just require some AT command strings (including dialing) just like a normal modem. Most of the Windreck drivers that come with the TAs seem to do all this config for you automagically, so you won't be aware of what's required. Often the default config may be with command echoing and response codes off, so until you tell it otherwise the TA will act dumb. The important thing is to get the TA using the right protocol. In my experience (of a single Zyxel Omninet) the TA supports V.120, X.75, and PPP. Depending on your ISPs ISDN interface, you may have to use PPP to get multiple channel bonding. The TA does this weird semi-PPP mode (I don't know much about the details) where it acts as an intermediary between your machine and the ISP without PPP on your machine really knowing it's there. It transparently interfaces between two channels to the ISP and one channel back to your machine. -- C. -- Craig Harding Head of Postproduction, Outpost Digital Media Ltd "I don't know about God, I just think we're handmade" - Polly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message