From owner-freebsd-isdn Sun Feb 4 9:55:20 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (sproxy.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 6410037B4EC for ; Sun, 4 Feb 2001 09:55:03 -0800 (PST) Received: (qmail 9801 invoked by uid 0); 4 Feb 2001 17:55:01 -0000 Received: from pd903746e.dip.t-dialin.net (HELO gmx.net) (217.3.116.110) by mail.gmx.net (mp002-rz3) with SMTP; 4 Feb 2001 17:55:01 -0000 Message-ID: <3A7D975A.5ABF9CDB@gmx.net> Date: Sun, 04 Feb 2001 18:54:34 +0100 From: Jens Trzaska X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Subject: ELSA Quickstep 3000 supported by i4bsd? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Am I right that the ELSA Quickstep 3000 card isn't supported in i4bsd? Its not in the list of supported cards...but perhaps it is compatible to one? Regards Jens Trzaska To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 5:17:46 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 18C2537B491 for ; Tue, 6 Feb 2001 05:17:28 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id B84A95D2C; Tue, 6 Feb 2001 14:16:12 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id A429738F; Tue, 6 Feb 2001 14:27:17 +0100 (MET) Subject: Re: ELSA Quickstep 3000 supported by i4bsd? In-Reply-To: <3A7D975A.5ABF9CDB@gmx.net> "from Jens Trzaska at Feb 4, 2001 06:54:34 pm" To: Jens Trzaska Date: Tue, 6 Feb 2001 14:27:17 +0100 (MET) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010206132717.A429738F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Jens Trzaska: > Am I right that the ELSA Quickstep 3000 card isn't supported in i4bsd? > Its not in the list of supported cards...but perhaps it is compatible > to one? The ELSA Quickstep 3000 ISA seems to be compatible to the ELSA Quickstep 1000 ISA but there seems to be a minor difference between the 3000 PCI and the 1000 PCI. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 7:15:37 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from zmamail04.zma.compaq.com (zmamail04.zma.compaq.com [161.114.64.104]) by hub.freebsd.org (Postfix) with ESMTP id 70BFE37B401 for ; Tue, 6 Feb 2001 07:15:20 -0800 (PST) Received: by zmamail04.zma.compaq.com (Postfix, from userid 12345) id 05A2D4ADE; Tue, 6 Feb 2001 10:15:20 -0500 (EST) Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254]) by zmamail04.zma.compaq.com (Postfix) with ESMTP id ABF8F4858 for ; Tue, 6 Feb 2001 10:15:19 -0500 (EST) Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21) id <11V0S7S2>; Tue, 6 Feb 2001 15:15:18 -0000 Message-ID: <73540AF2BA65D211AEF40000F83072A10348B244@DMOEXC1> From: "Blichfeldt, Bjarne" To: "'freebsd-isdn@freebsd.org'" Subject: ASUScom 128K Date: Tue, 6 Feb 2001 15:14:57 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have, on FreeBSD 4.2-stable, installed the latest i4b, .96-beta, and cannot get it to find my ISDN card. The card is a ASUScom 128K, HN100-ST-D, and as far as I can see, the vendor id is 0x360b630e. I found this by printing out the vendor id during boot. But the card aslo report itselv as ASU1688. I have so far tried to set it up as : option ASUSCOM_IPAC device isic0 Since the card report itselv as ASU1688, I also tried option DYNALINK, but that is not supported. Are there any way I can get this to work ? Regards, Bjarne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 7:54:56 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from leka.almamedia.fi (leka.yhteys.mtv3.fi [62.236.224.129]) by hub.freebsd.org (Postfix) with SMTP id 7B74A37B4EC for ; Tue, 6 Feb 2001 07:54:38 -0800 (PST) Received: (qmail 5591 invoked from network); 6 Feb 2001 15:54:34 -0000 Received: from dyn-c-166.yhteys.mtv3.fi (HELO snafu.intra.net) (62.236.227.166) by leka.yhteys.mtv3.fi with SMTP; 6 Feb 2001 15:54:34 -0000 Received: from cubical.fi (junkyard.intra.net [192.168.2.2]) by snafu.intra.net (8.11.1/8.11.1) with ESMTP id f16Fs1e03552; Tue, 6 Feb 2001 17:54:02 +0200 (EET) (envelope-from jml@cubical.fi) Message-ID: <3A801E13.869AB4F2@cubical.fi> Date: Tue, 06 Feb 2001 17:53:55 +0200 From: Juha-Matti Liukkonen X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Blichfeldt, Bjarne" Cc: "'freebsd-isdn@freebsd.org'" Subject: Re: ASUScom 128K References: <73540AF2BA65D211AEF40000F83072A10348B244@DMOEXC1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, just as a reminder for Asuscom PCI card owners: the iwic driver in i4b 0.96 supports the Winbond-based Asuscom PCI cards (chip ip 0x06751043). However, it's a 50/50 chance if your PCI Asuscom is a Winbond model, or a HFC-S -- Asus has the nasty habit of producing batches of the same card using these different chipsets which are completely incompatible with each other (assumably depending on which they happen to get cheaper at the moment). Argh. Technically, the ihfc driver supports ISA cards based on the HFC-S chipset, and might be relatively easily adapted to work with PCI cards based on the same. Any takers? - Juha "Blichfeldt, Bjarne" wrote: > > I have, on FreeBSD 4.2-stable, installed the latest i4b, .96-beta, and > cannot get it to find my ISDN card. > > The card is a ASUScom 128K, HN100-ST-D, and as far as I can see, the vendor > id > is 0x360b630e. I found this by printing out the vendor id during boot. > But the card aslo report itselv as ASU1688. > > I have so far tried to set it up as : > > option ASUSCOM_IPAC > device isic0 > > Since the card report itselv as ASU1688, I also tried option DYNALINK, but > that is > not supported. > > Are there any way I can get this to work ? > > Regards, > Bjarne > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message -- Juha-Matti Liukkonen, Cubical Solutions Ltd Phone: +358(0)405280142 Email: jml@cubical.fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 8:36:16 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 2310837B401 for ; Tue, 6 Feb 2001 08:36:00 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 0C95C5D23; Tue, 6 Feb 2001 17:34:50 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id 5632851F; Tue, 6 Feb 2001 17:45:55 +0100 (MET) Subject: Re: ASUScom 128K In-Reply-To: <3A801E13.869AB4F2@cubical.fi> "from Juha-Matti Liukkonen at Feb 6, 2001 05:53:55 pm" To: Juha-Matti Liukkonen Date: Tue, 6 Feb 2001 17:45:55 +0100 (MET) Cc: "Blichfeldt, Bjarne" , "'freebsd-isdn@freebsd.org'" Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010206164555.5632851F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Juha-Matti Liukkonen: > Technically, the ihfc driver supports ISA cards based on the HFC-S > chipset, and might be relatively easily adapted to work with PCI cards > based on the same. Any takers? FYI, i am working - slowly - to get the PCI HFC chip supported and have sent what i have to Martin Husemann who obviously wants to get a driver ready for this card for NetBSD. So it looks like we get this chip supported in the near future. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 12:17:42 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id C7D9637B401 for ; Tue, 6 Feb 2001 12:17:24 -0800 (PST) Received: (qmail 19711 invoked by uid 0); 6 Feb 2001 20:17:22 -0000 Received: from pd950887a.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.122) by mail.gmx.net (mail04) with SMTP; 6 Feb 2001 20:17:22 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id UAA28727 for freebsd-isdn@freebsd.org; Tue, 6 Feb 2001 20:57:27 +0100 Date: Tue, 6 Feb 2001 20:57:27 +0100 From: Gerhard Sittig To: freebsd-isdn@freebsd.org Subject: Re: ELSA Quickstep 3000 supported by i4bsd? Message-ID: <20010206205726.D26500@speedy.gsinet> Mail-Followup-To: freebsd-isdn@freebsd.org References: <3A7D975A.5ABF9CDB@gmx.net> <20010206132717.A429738F@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010206132717.A429738F@hcswork.hcs.de>; from hm@hcs.de on Tue, Feb 06, 2001 at 02:27:17PM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 06, 2001 at 14:27 +0100, Hellmuth Michaelis wrote: > > The ELSA Quickstep 3000 ISA seems to be compatible to the ELSA > Quickstep 1000 ISA but there seems to be a minor difference > between the 3000 PCI and the 1000 PCI. The ELSA Quickstep 3000 model basically _is_ a QS1000, with having some analog part added in hardware (IIRC it's called "arcofi" or something). Those who are interested might want to go to Deja and search in de.alt.comm.isdn4linux (although it's in the de hierarchy it's bilingual). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 13:56: 1 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from jello276.jellocom.de (jello276.jellocom.de [217.17.194.146]) by hub.freebsd.org (Postfix) with ESMTP id 2A01437B401 for ; Tue, 6 Feb 2001 13:55:44 -0800 (PST) Received: from local.net (ppp015.jellonet.de [217.17.194.15]) by jello276.jellocom.de (8.11.2/8.10.1) with ESMTP id f16Ltgo20807 for ; Tue, 6 Feb 2001 22:55:42 +0100 Received: (from ingolf@localhost) by local.net (8.11.0/8.11.0) id f16Lt0829367 for freebsd-isdn@freebsd.org; Tue, 6 Feb 2001 22:55:00 +0100 (MET) Date: Tue, 6 Feb 2001 22:54:59 +0100 From: Ingolf Steinbach To: freebsd-isdn@freebsd.org Subject: isp0: ipcp illegal up in state req-sent Message-ID: <20010206225459.A29361@maus.local.net> Mail-Followup-To: Ingolf Steinbach , freebsd-isdn@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Faith: Jesus Christ Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, with my i4b updated to 0.96.00, I get the following messages each time I dial out: Feb 6 22:49:18 isdn /netbsd: isp0: ipcp illegal up in state req-sent Feb 6 22:49:18 isdn /netbsd: isp0: ipv6cp illegal up in state req-sent Feb 6 22:49:18 isdn /netbsd: isp0: lcp: RXJ+ (proto-rej) for proto 0x8057 (ipv6cp/req-sent) Feb 6 22:49:18 isdn /netbsd: isp0: lcp: RXJ+ (proto-rej) for proto 0x8057 (ipv6cp/closing) What do they mean? Can I switch them off? Should I ignore them? Does my provider probably see error messages caused by this? Ingolf -- Ingolf Steinbach Balin@IRCnet ICQ#60829470 PGP: 0x7B3B5661 213C 828E 0C92 16B5 05D0 4D5B A324 EC04 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 6 14:50:59 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id 5814B37B69B for ; Tue, 6 Feb 2001 14:50:42 -0800 (PST) Received: from fwd06.sul.t-online.com by mailout05.sul.t-online.com with smtp id 14QGwb-0007ZZ-08; Tue, 06 Feb 2001 23:50:41 +0100 Received: from night-porter.duskware.de (520038743430-0001@[193.159.65.55]) by fmrl06.sul.t-online.com with esmtp id 14QGwY-1RCAZkC; Tue, 6 Feb 2001 23:50:38 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.2/8.11.0) id f16MoXJ00960; Tue, 6 Feb 2001 23:50:33 +0100 (MET) From: Martin Husemann Message-Id: <200102062250.f16MoXJ00960@night-porter.duskware.de> Subject: Re: isp0: ipcp illegal up in state req-sent In-Reply-To: <20010206225459.A29361@maus.local.net> "from Ingolf Steinbach at Feb 6, 2001 10:54:59 pm" To: Ingolf Steinbach Date: Tue, 6 Feb 2001 23:50:33 +0100 (MET) Cc: freebsd-isdn@freebsd.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > What do they mean? Can I switch them off? Should I ignore > them? Does my provider probably see error messages caused > by this? The "illegal up" ones are anoying (and to be fixed in NetBSD-current soon, don't think FreeBSD has them). The others are simply your provider not giving you IPv6 although your kernel could handle it. Just ignore them. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 7 1:44:44 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E8BB37B65D for ; Wed, 7 Feb 2001 01:44:27 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 4B0B55D06; Wed, 7 Feb 2001 10:43:17 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id BB0F838F; Wed, 7 Feb 2001 10:54:24 +0100 (MET) Subject: Re: ELSA Quickstep 3000 supported by i4bsd? In-Reply-To: <20010206205726.D26500@speedy.gsinet> "from Gerhard Sittig at Feb 6, 2001 08:57:27 pm" To: Gerhard Sittig Date: Wed, 7 Feb 2001 10:54:24 +0100 (MET) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010207095424.BB0F838F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Gerhard Sittig: > > The ELSA Quickstep 3000 ISA seems to be compatible to the ELSA > > Quickstep 1000 ISA but there seems to be a minor difference > > between the 3000 PCI and the 1000 PCI. > > The ELSA Quickstep 3000 model basically _is_ a QS1000 Which one, the PCI or ISA version ? hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 7 13:34:42 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from jello276.jellocom.de (jello276.jellocom.de [217.17.194.146]) by hub.freebsd.org (Postfix) with ESMTP id 4EC1637B69D for ; Wed, 7 Feb 2001 13:34:24 -0800 (PST) Received: from local.net (ppp091.jellonet.de [217.17.194.91]) by jello276.jellocom.de (8.11.2/8.10.1) with ESMTP id f17LYMg22080 for ; Wed, 7 Feb 2001 22:34:22 +0100 Received: (from ingolf@localhost) by local.net (8.11.0/8.11.0) id f17LXaI01278 for freebsd-isdn@freebsd.org; Wed, 7 Feb 2001 22:33:36 +0100 (MET) Date: Wed, 7 Feb 2001 22:33:36 +0100 From: Ingolf Steinbach To: freebsd-isdn@freebsd.org Subject: isdnd.rc: ppp-send-* not working correctly Message-ID: <20010207223336.A1255@maus.local.net> Mail-Followup-To: Ingolf Steinbach , freebsd-isdn@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Faith: Jesus Christ Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, in my isdnd.rc file I have the following entries ppp-auth-paranoid = no ppp-send-auth = chap ppp-send-name = "MYNAME" ppp-send-password = "MYSECRET" (of course with real -name and -password). If I start isdnd without any ispppcontrol command before, these values are taken as those expected by my ISP, i.e.: isp0: phase=dead hisauthproto=chap hisauthname="MYNAME" lcp timeout: 1.000 s This happens on NetBSD-1.5/i386 with i4b-00.96.0. Has anyone else seen this? Ingolf -- Ingolf Steinbach Balin@IRCnet ICQ#60829470 PGP: 0x7B3B5661 213C 828E 0C92 16B5 05D0 4D5B A324 EC04 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 7 13:57: 4 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 25D6237B6B2 for ; Wed, 7 Feb 2001 13:56:44 -0800 (PST) Received: from fwd05.sul.t-online.com by mailout00.sul.t-online.com with smtp id 14QcZu-0005iO-06; Wed, 07 Feb 2001 22:56:42 +0100 Received: from night-porter.duskware.de (520038743430-0001@[62.158.126.118]) by fmrl05.sul.t-online.com with esmtp id 14QcZi-0ZsKbwC; Wed, 7 Feb 2001 22:56:30 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.2/8.11.0) id f17LuRq01190; Wed, 7 Feb 2001 22:56:27 +0100 (MET) From: Martin Husemann Message-Id: <200102072156.f17LuRq01190@night-porter.duskware.de> Subject: Re: isdnd.rc: ppp-send-* not working correctly In-Reply-To: <20010207223336.A1255@maus.local.net> "from Ingolf Steinbach at Feb 7, 2001 10:33:36 pm" To: Ingolf Steinbach Date: Wed, 7 Feb 2001 22:56:27 +0100 (MET) Cc: freebsd-isdn@freebsd.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM981582987-660-0_ Content-Transfer-Encoding: 7bit X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM981582987-660-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII > This happens on NetBSD-1.5/i386 with i4b-00.96.0. Has > anyone else seen this? This has been fixed in the version inside NetBSD (hope I did send Helmuth a copy, but guess I did so). You can either go to -current (duck, run for cover) or apply the appended patch. Martin --ELM981582987-660-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=patch Content-Description: rc_config.c.diff Index: rc_config.c =================================================================== RCS file: /cvsroot/basesrc/usr.sbin/isdn/isdnd/rc_config.c,v retrieving revision 1.1 retrieving revision 1.2 diff -c -u -r1.1 -r1.2 --- rc_config.c 2001/01/06 13:00:26 1.1 +++ rc_config.c 2001/01/07 09:00:49 1.2 @@ -27,7 +27,7 @@ * i4b daemon - config file processing * ----------------------------------- * - * $Id: rc_config.c,v 1.1 2001/01/06 13:00:26 martin Exp $ + * $Id: rc_config.c,v 1.2 2001/01/07 09:00:49 martin Exp $ * * $FreeBSD$ * @@ -305,32 +305,32 @@ { if(cep->ppp_expect_auth == AUTH_NONE) { - spr.defs.myauth.proto = 0; + spr.defs.hisauth.proto = 0; } else if ((cep->ppp_expect_auth == AUTH_CHAP || cep->ppp_expect_auth == AUTH_PAP) && cep->ppp_expect_name[0] != 0 && cep->ppp_expect_password[0] != 0) { - spr.defs.myauth.proto = cep->ppp_expect_auth == AUTH_PAP ? PPP_PAP : PPP_CHAP; - strncpy(spr.defs.myauth.name, cep->ppp_expect_name, AUTHNAMELEN); - strncpy(spr.defs.myauth.secret, cep->ppp_expect_password, AUTHKEYLEN); + spr.defs.hisauth.proto = cep->ppp_expect_auth == AUTH_PAP ? PPP_PAP : PPP_CHAP; + strncpy(spr.defs.hisauth.name, cep->ppp_expect_name, AUTHNAMELEN); + strncpy(spr.defs.hisauth.secret, cep->ppp_expect_password, AUTHKEYLEN); } } if (cep->ppp_send_auth != AUTH_UNDEF) { if(cep->ppp_send_auth == AUTH_NONE) { - spr.defs.hisauth.proto = 0; + spr.defs.myauth.proto = 0; } else if ((cep->ppp_send_auth == AUTH_CHAP || cep->ppp_send_auth == AUTH_PAP) && cep->ppp_send_name[0] != 0 && cep->ppp_send_password[0] != 0) { - spr.defs.hisauth.proto = cep->ppp_send_auth == AUTH_PAP ? PPP_PAP : PPP_CHAP; - strncpy(spr.defs.hisauth.name, cep->ppp_send_name, AUTHNAMELEN); - strncpy(spr.defs.hisauth.secret, cep->ppp_send_password, AUTHKEYLEN); + spr.defs.myauth.proto = cep->ppp_send_auth == AUTH_PAP ? PPP_PAP : PPP_CHAP; + strncpy(spr.defs.myauth.name, cep->ppp_send_name, AUTHNAMELEN); + strncpy(spr.defs.myauth.secret, cep->ppp_send_password, AUTHKEYLEN); if(cep->ppp_auth_flags & AUTH_REQUIRED) spr.defs.hisauth.flags &= ~AUTHFLAG_NOCALLOUT; --ELM981582987-660-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 7 19:15:37 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (pop.gmx.de [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 56BF437B69C for ; Wed, 7 Feb 2001 19:15:19 -0800 (PST) Received: (qmail 5883 invoked by uid 0); 8 Feb 2001 03:15:17 -0000 Received: from pd9508845.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.69) by mail.gmx.net (mp002-rz3) with SMTP; 8 Feb 2001 03:15:17 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id XAA31620 for freebsd-isdn@freebsd.org; Wed, 7 Feb 2001 23:39:20 +0100 Date: Wed, 7 Feb 2001 23:39:20 +0100 From: Gerhard Sittig To: freebsd-isdn@freebsd.org Subject: Re: ELSA Quickstep 3000 supported by i4bsd? Message-ID: <20010207233920.E26500@speedy.gsinet> Mail-Followup-To: freebsd-isdn@freebsd.org References: <20010206205726.D26500@speedy.gsinet> <20010207095424.BB0F838F@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010207095424.BB0F838F@hcswork.hcs.de>; from hm@hcs.de on Wed, Feb 07, 2001 at 10:54:24AM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 07, 2001 at 10:54 +0100, Hellmuth Michaelis wrote: > >From the keyboard of Gerhard Sittig: > > > > The ELSA Quickstep 3000 ISA seems to be compatible to the > > > ELSA Quickstep 1000 ISA but there seems to be a minor > > > difference between the 3000 PCI and the 1000 PCI. > > > > The ELSA Quickstep 3000 model basically _is_ a QS1000 > > Which one, the PCI or ISA version ? Uh? Are they different (besides at the computer bus interface side)? If so, I have to admit I'm completely ignorant in this respect. :( Just like renaming them to some "MicroLink" series wouldn't be enough to confuse people ... I don't have any of Elsa's cards. But it's what was constantly recommended when I ran Linux (quite some years ago:) -- the company was known to cooperate well with the I4L developers, didn't change hardware every two weeks, and the cards Just Worked(TM) and did so in a solid way. And yes, I understood that the QS3000 was nothing more than a QS1000 plus the analog chip. And that the "plus" bundle was of no additional value for UNIX users since it only had Windows software nobody could make use of. And in passing I noticed the non obvious and unnecessary move to sell the same(!) hardware as some "MicroLink" thingy -- the name they've been selling modems under for the years before. To return to the thread's topic: I had the impression (from reading isdn related mailing lists) that you could choose any QS1000 driver to drive a QS3000 card without expecting any problems. It's just that the analog part of the card isn't supported then. But shoveling data via ISDN (and maybe voice AMs) is no problem at all. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 7 21:52:23 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id B6F6437B401 for ; Wed, 7 Feb 2001 21:52:05 -0800 (PST) Received: from fwd04.sul.t-online.com by mailout06.sul.t-online.com with smtp id 14Qjzt-00056C-02; Thu, 08 Feb 2001 06:52:01 +0100 Received: from night-porter.duskware.de (520038743430-0001@[62.158.126.118]) by fmrl04.sul.t-online.com with esmtp id 14Qjzn-0XsabQC; Thu, 8 Feb 2001 06:51:55 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.2/8.11.0) id f185psx02486; Thu, 8 Feb 2001 06:51:54 +0100 (MET) From: Martin Husemann Message-Id: <200102080551.f185psx02486@night-porter.duskware.de> Subject: Re: ELSA Quickstep 3000 supported by i4bsd? In-Reply-To: <20010207233920.E26500@speedy.gsinet> "from Gerhard Sittig at Feb 7, 2001 11:39:20 pm" To: Gerhard Sittig Date: Thu, 8 Feb 2001 06:51:54 +0100 (MET) Cc: freebsd-isdn@freebsd.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Which one, the PCI or ISA version ? > > Uh? Are they different (besides at the computer bus interface > side)? Yes, they are fundamentally different. But that's not the problem. The QS3000 obviously has a different "name", both human (sales) wise as (either) isapnp or pci wise. We need to add that different name to the appropriate driver to make it accept that card, then, as you say, it should just work. So someone having that card should just post his verbose boot message or pnpinfo output and we will be set. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 0:12:52 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BCE637B401 for ; Thu, 8 Feb 2001 00:12:35 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id JAA31510 for freebsd-isdn@freebsd.org; Thu, 8 Feb 2001 09:12:33 +0100 (CET) (envelope-from kuku) Date: Thu, 8 Feb 2001 09:12:33 +0100 (CET) From: Christoph Kukulies Message-Id: <200102080812.JAA31510@gilberto.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: BUSY! Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just curious about the meaning of an exclamation sign in a message. Is it something unusual when this message occurs during connection establishing: Feb 8 09:07:43 isdn-kukulies isdnd[91]: DBG set_channel_busy: controller [0] ch annel B2 set to BUSY! I stumbled this morning over this message while I normally don't take much notice about messages appearing in xconsole. At this time another channel (B1 probably) was already busy with an NT dialup connection. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 2:25:52 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from grieg.transfer.nl (mail.transfer.nl [195.193.231.177]) by hub.freebsd.org (Postfix) with ESMTP id 2B9B737B401 for ; Thu, 8 Feb 2001 02:25:35 -0800 (PST) Received: from cs.pdx.edu (ease5.transfer.nl [192.87.53.84]) by grieg.transfer.nl (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id LAA08211 for ; Thu, 8 Feb 2001 11:25:34 +0100 X-Authentication-Warning: grieg.transfer.nl: Host ease5.transfer.nl [192.87.53.84] claimed to be cs.pdx.edu Message-ID: <3A8273B2.6090008@cs.pdx.edu> Date: Thu, 08 Feb 2001 11:23:46 +0100 From: rtg User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; 0.7) Gecko/20010109 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.org Subject: ppp link over isdn Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there a *preferred* way to run ppp over isdn, pppij, pppd, or synchronous ppp, using isp0? Tnx, rotan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 3:13:39 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from jump.tangro.de (cray-ymp.tangro.de [193.155.17.164]) by hub.freebsd.org (Postfix) with ESMTP id 49F7337B491 for ; Thu, 8 Feb 2001 03:13:21 -0800 (PST) Received: from janus.tangro.de (janus.tangro.de [193.155.17.163]) by jump.tangro.de (8.9.3/8.9.3) with ESMTP id MAA24570; Thu, 8 Feb 2001 12:13:13 +0100 (CET) Message-Id: <4.3.2.7.2.20010208110748.00bcde60@mail.tangro.de> X-Sender: hf@mail.tangro.de (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 08 Feb 2001 11:13:23 +0100 To: Martin Husemann From: Hauke Fath Subject: Re: isdnd.rc: ppp-send-* not working correctly Cc: freebsd-isdn@FreeBSD.ORG In-Reply-To: <200102072156.f17LuRq01190@night-porter.duskware.de> References: <20010207223336.A1255@maus.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 22:56 07.02.01 +0100, Martin Husemann wrote: > > This happens on NetBSD-1.5/i386 with i4b-00.96.0. Has > > anyone else seen this? > >This has been fixed in the version inside NetBSD (hope I did send Helmuth >a copy, but guess I did so). > >You can either go to -current (duck, run for cover) >or apply the appended patch. Martin, what exactly of the i4b distribution is integrated into NetBSD? The kernel parts (like, say, with Netatalk support), or also the userland tools? I am thinking about moving a 1.4.1 dialup server that has an annoying tendency to reboot when the second client dials in. By going directly to a -current snapshot, I'd get around the merge work. hauke -- Hauke Fath Tangro Software Components GmbH D-69115 Heidelberg hf@Tangro.DE Ruf +49-6221-13336-0, Fax -21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 6:15:38 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from highland.isltd.insignia.com (highland.isltd.insignia.com [195.217.222.20]) by hub.freebsd.org (Postfix) with ESMTP id AC85B37B401 for ; Thu, 8 Feb 2001 06:15:20 -0800 (PST) Received: from wolf.isltd.insignia.com (wolf-c1.isltd.insignia.com [193.112.16.10]) by highland.isltd.insignia.com (8.11.2/8.11.2/check_local4.2) with ESMTP id f18EFHI11196 for ; Thu, 8 Feb 2001 14:15:18 GMT Received: (from news@localhost) by wolf.isltd.insignia.com (8.9.3/8.9.3) id OAA04988 for freebsd-isdn@freebsd.org; Thu, 8 Feb 2001 14:15:17 GMT From: freebsd-isdn-local@insignia.com X-Authentication-Warning: wolf.isltd.insignia.com: news set sender to freebsd-isdn-local@insignia.com using -f To: freebsd-isdn@freebsd.org Subject: Callback support with i4b and userland PPP? Date: Thu, 8 Feb 2001 14:11:10 -0000 Message-ID: <95u9lk$4ro$1@wolf.isltd.insignia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have been playing with i4b, first with kernel PPP then with userland PPP, and have had no problems connecting to a local ISP. However, connecting to a RAS server in my office has proved troublesome. It's fine unless I configure the server to require callback (which is the norm). The outgoing call gets dropped, and the incoming call is logged but never gets picked up. I'm wondering if callback is currently supported? Jim Hatfield To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 11:26:13 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 34EBA37B401 for ; Thu, 8 Feb 2001 11:25:56 -0800 (PST) Received: from fwd00.sul.t-online.com by mailout00.sul.t-online.com with smtp id 14QwhW-0001BL-0B; Thu, 08 Feb 2001 20:25:54 +0100 Received: from night-porter.duskware.de (520038743430-0001@[62.158.126.109]) by fmrl00.sul.t-online.com with esmtp id 14QwhH-1v4S12C; Thu, 8 Feb 2001 20:25:39 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.2/8.11.0) id f18JPNU00880; Thu, 8 Feb 2001 20:25:23 +0100 (MET) From: Martin Husemann Message-Id: <200102081925.f18JPNU00880@night-porter.duskware.de> Subject: Re: isdnd.rc: ppp-send-* not working correctly In-Reply-To: <4.3.2.7.2.20010208110748.00bcde60@mail.tangro.de> "from Hauke Fath at Feb 8, 2001 11:13:23 am" To: Hauke Fath Date: Thu, 8 Feb 2001 20:25:23 +0100 (MET) Cc: Martin Husemann , freebsd-isdn@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > what exactly of the i4b distribution is integrated into NetBSD? The kernel > parts (like, say, with Netatalk support), or also the userland tools? You want a real answer: everything I needed to connect to my ISP ;-) We have all kernel stuff that NetBSD 0.96 supported integrated in NetBSD-current. From the userland stuff we have [/usr/src/usr.sbin/isdn] martin@night-porter > ls CVS/ daicctl/ isdnd/ isdntelctl/ Makefile dtmfdecode/ isdnmonitor/ isdntrace/ Makefile.inc g711conv/ isdntel/ ispppcontrol/ > I am thinking about moving a 1.4.1 dialup server that has an annoying > tendency to reboot when the second client dials in. By going directly to a > -current snapshot, I'd get around the merge work. I'm not sure I'd recommend using current on any type of server. It's working well for me, but I don't have moved the machines at work to this version yet (they all run 1.5 plus NetBSD 0.96). If schedules hold, we will branch for NetBSD 1.6 sometime in the not so distant future. This will have all the isdn stuff in there currently... Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 12:40:12 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 0738337B6C9 for ; Thu, 8 Feb 2001 12:39:54 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f18KdmG15920 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 8 Feb 2001 21:39:50 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f18Ke7P80315 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Thu, 8 Feb 2001 21:40:16 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f18Ke7Q81329; Thu, 8 Feb 2001 21:40:07 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Feb 2001 21:40:07 +0100 From: Bernd Walter To: freebsd-isdn-local@insignia.com Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Callback support with i4b and userland PPP? Message-ID: <20010208214007.C81067@cicely5.cicely.de> References: <95u9lk$4ro$1@wolf.isltd.insignia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <95u9lk$4ro$1@wolf.isltd.insignia.com>; from freebsd-isdn-local@insignia.com on Thu, Feb 08, 2001 at 02:11:10PM -0000 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 08, 2001 at 02:11:10PM -0000, freebsd-isdn-local@insignia.com wrote: > Hi, > > I have been playing with i4b, first with kernel PPP then with userland PPP, > and > have had no problems connecting to a local ISP. > > However, connecting to a RAS server in my office has proved troublesome. > It's fine > unless I configure the server to require callback (which is the norm). > > The outgoing call gets dropped, and the incoming call is logged but never > gets picked up. > > I'm wondering if callback is currently supported? The callback in isdnd is not available for userland ppp. I'm using the following in isdnd.rc together with a reject for the number: regexpr = "incoming call from providernumber to localnumber" regprog = "pingscript" While pingscript is nothing more than: #!/bin/sh ( ping -c 1 anyip ) > /dev/null 2>&1 -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 8 15:26:32 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 41B0937C188 for ; Thu, 8 Feb 2001 15:26:14 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f18NQ7R00582; Thu, 8 Feb 2001 23:26:07 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f18NSRA05957; Thu, 8 Feb 2001 23:28:27 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102082328.f18NSRA05957@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-isdn-local@insignia.com Cc: freebsd-isdn@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: Callback support with i4b and userland PPP? In-Reply-To: Message from freebsd-isdn-local@insignia.com of "Thu, 08 Feb 2001 14:11:10 GMT." <95u9lk$4ro$1@wolf.isltd.insignia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Feb 2001 23:28:27 +0000 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I have been playing with i4b, first with kernel PPP then with userland PPP, > and > have had no problems connecting to a local ISP. > > However, connecting to a RAS server in my office has proved troublesome. > It's fine > unless I configure the server to require callback (which is the norm). > > The outgoing call gets dropped, and the incoming call is logged but never > gets picked up. > > I'm wondering if callback is currently supported? It should work ok, but the client ppp doesn't wait for the return call - you have to arrange for that to be answered separately. > Jim Hatfield -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 9 3:28: 0 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from jump.tangro.de (cray-ymp.tangro.de [193.155.17.164]) by hub.freebsd.org (Postfix) with ESMTP id A80F737B65D for ; Fri, 9 Feb 2001 03:27:42 -0800 (PST) Received: from janus.tangro.de (janus.tangro.de [193.155.17.163]) by jump.tangro.de (8.9.3/8.9.3) with ESMTP id MAA14260; Fri, 9 Feb 2001 12:27:38 +0100 (CET) Message-Id: <4.3.2.7.2.20010209112239.00bebef0@mail.tangro.de> X-Sender: hf@mail.tangro.de (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 09 Feb 2001 11:27:48 +0100 To: Martin Husemann From: Hauke Fath Subject: Re: isdnd.rc: ppp-send-* not working correctly Cc: freebsd-isdn@FreeBSD.ORG In-Reply-To: <200102081925.f18JPNU00880@night-porter.duskware.de> References: <4.3.2.7.2.20010208110748.00bcde60@mail.tangro.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 20:25 08.02.01 +0100, Martin Husemann wrote: > > what exactly of the i4b distribution is integrated into NetBSD? The kernel > > parts (like, say, with Netatalk support), or also the userland tools? > > [/usr/src/usr.sbin/isdn] martin@night-porter > ls > CVS/ daicctl/ isdnd/ isdntelctl/ > Makefile dtmfdecode/ isdnmonitor/ isdntrace/ > Makefile.inc g711conv/ isdntel/ ispppcontrol/ OK, that should do. ;) >I'm not sure I'd recommend using current on any type of server. >It's working well for me, but I don't have moved the machines at work to >this version yet (they all run 1.5 plus NetBSD 0.96). Well - I've seen -current snapshots that were rock-stable, and I've seen release kernels that were unusable, at least on Lesser Platforms (mac68k here). Still, UBC problems seem an issue with -current at the moment. >If schedules hold, we will branch for NetBSD 1.6 sometime in the not so >distant >future. Ah, well, that's what they always say. I'd expect 1.6 by the end of the year, and I have to do _something_ about the kernel panics before then. hauke -- Hauke Fath Tangro Software Components GmbH D-69115 Heidelberg hf@Tangro.DE Ruf +49-6221-13336-0, Fax -21 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 9 8:19: 9 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BEAD37B8CC for ; Fri, 9 Feb 2001 07:18:13 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id QAA40079 for freebsd-isdn@freebsd.org; Fri, 9 Feb 2001 16:18:12 +0100 (CET) (envelope-from kuku) Date: Fri, 9 Feb 2001 16:18:12 +0100 (CET) From: Christoph Kukulies Message-Id: <200102091518.QAA40079@gilberto.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: fax solution? Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does i4b provide anything WRT faxing? I'm dreaming of a soultion allowing me to send a fax from an Office 97 or Office 2000 Windows box (Word 97 or whatever Word program you are using) and send that fax through a FreeBSD gateway machine. At the moment I'm using mgetty+sendfax and a modem but wouldn't using ISDN be smarter? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 9 11:35:10 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from alice.turbocat.de (gate.turbocat.de [212.41.163.6]) by hub.freebsd.org (Postfix) with ESMTP id 9003737B4EC for ; Fri, 9 Feb 2001 11:34:51 -0800 (PST) Received: from luigi.turbocat.de (luigi.turbocat.de [212.41.163.197]) by alice.turbocat.de (8.10.1/8.10.1/08082000/dw/1) with ESMTP id f19JYi207558; Fri, 9 Feb 2001 20:34:48 +0100 (CET) Received: (from dave@localhost) by luigi.turbocat.de (8.8.5/8.7.3) id UAA00311; Fri, 9 Feb 2001 20:34:41 +0100 (MET) Message-Id: <200102091934.UAA00311@luigi.turbocat.de> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) Received: by NeXT.Mailer (1.148) From: David Wetzel Date: Fri, 9 Feb 2001 20:34:37 +0100 To: Christoph Kukulies Subject: Re: fax solution? Cc: freebsd-isdn@FreeBSD.ORG References: <200102091518.QAA40079@gilberto.physik.rwth-aachen.de> Organisation: Turbocat's Development http://www.turbocat.de/ Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Christoph Kukulies > Does i4b provide anything WRT faxing? No. > I'm dreaming of a soultion allowing me to send a fax from an > Office 97 or Office 2000 Windows box (Word 97 or whatever Word program > you are using) and send that fax through a FreeBSD gateway > machine. > > At the moment I'm using mgetty+sendfax and a modem but wouldn't using > ISDN be smarter? No. Even if you look at all the "professional" ISDN solutions, a decent modem will always be better. I got faxes from AVM, Ferrai Fax and other software but no one is as good as some modem based solution. If you want to use ISDN, just send the file as PDF ,-) BTW: Back in the old NeXT days we made TurboFax that uses the NeXT Window Server to convert the print output to g3 and send it with sendfax. That gave us a PostScript Level 2 Fax. --- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 NeXTmail dave@turbocat.de (______) http://www.turbocat.de/ DEVELOPMENT * CONSULTING * ADMINISTRATION To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 10 11: 0:40 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 7436137B4EC for ; Sat, 10 Feb 2001 11:00:21 -0800 (PST) Received: from localhost (1919 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Sat, 10 Feb 2001 20:00:18 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #18 built 2000-Oct-9) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 66D1652A87; Sat, 10 Feb 2001 19:58:25 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id C97069B20; Sat, 10 Feb 2001 19:58:33 +0100 (CET) Subject: Re: ELSA Quickstep 3000 supported by i4bsd? In-Reply-To: <200102080551.f185psx02486@night-porter.duskware.de> from Martin Husemann at "Feb 8, 2001 6:51:54 am" To: martin@duskware.de (Martin Husemann) Date: Sat, 10 Feb 2001 19:58:33 +0100 (CET) Cc: Gerhard.Sittig@gmx.net, freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 889 Message-Id: <20010210185833.C97069B20@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Husemann wrote: > > > Which one, the PCI or ISA version ? > > > > Uh? Are they different (besides at the computer bus interface > > side)? > > Yes, they are fundamentally different. But that's not the problem. > The QS3000 obviously has a different "name", both human (sales) wise > as (either) isapnp or pci wise. We need to add that different name to > the appropriate driver to make it accept that card, then, as you say, it > should just work. > > So someone having that card should just post his verbose boot message or > pnpinfo output and we will be set. Glancing thru the Linux driver shows that the ISA PnP cards seem to be similar while the PCI cards need some different (interrupt ?) handling. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 10 11: 0:39 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 11B7237B401 for ; Sat, 10 Feb 2001 11:00:20 -0800 (PST) Received: from localhost (1634 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Sat, 10 Feb 2001 20:00:18 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #18 built 2000-Oct-9) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id A330152A87; Sat, 10 Feb 2001 19:53:42 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id EEF749B1F; Sat, 10 Feb 2001 19:53:50 +0100 (CET) Subject: Re: BUSY! In-Reply-To: <200102080812.JAA31510@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Feb 8, 2001 9:12:33 am" To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Sat, 10 Feb 2001 19:53:50 +0100 (CET) Cc: freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 644 Message-Id: <20010210185350.EEF749B1F@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christoph Kukulies wrote: > Just curious about the meaning of an exclamation sign in a message. > Is it something unusual when this message occurs during connection establishing: > > Feb 8 09:07:43 isdn-kukulies isdnd[91]: DBG set_channel_busy: controller [0] ch > annel B2 set to BUSY! This is just an isdnd-internal debug message saying that a channel which is about to be used for data transfer is marked as busy and as a result it is unavailable for someone else. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 10 11:11:20 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 1E3B937B401 for ; Sat, 10 Feb 2001 11:11:03 -0800 (PST) Received: from localhost (1737 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Sat, 10 Feb 2001 20:10:15 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #18 built 2000-Oct-9) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 4250652A87; Sat, 10 Feb 2001 20:05:45 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id A092D9B24; Sat, 10 Feb 2001 20:05:53 +0100 (CET) Subject: Re: ppp link over isdn In-Reply-To: <3A8273B2.6090008@cs.pdx.edu> from rtg at "Feb 8, 2001 11:23:46 am" To: rotan@cs.pdx.edu (rtg) Date: Sat, 10 Feb 2001 20:05:53 +0100 (CET) Cc: freebsd-isdn@FreeBSD.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 827 Message-Id: <20010210190553.A092D9B24@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org rtg wrote: > Is there a *preferred* way to run ppp over isdn, pppij, pppd, or > synchronous ppp, using isp0? The supported methods are either userland ppp(8) and/or kernel PPP using isppp/sppp/isp. Others such as pppij and pppd will not work. Userland ppp(8) has all the bells and whistles you expect from a PPP package whereas kernel ppp is relatively small and without the overhead of moving packets from and to userspace and having a daemon run in userland but it supports only a very limited amount of features of what PPP can do. Both have their pros and cons and you have to choose the one which fits your needs. There is no preferred way ... hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 10 11:45:26 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from liliput.tmp.com.br (liliput.tmp.com.br [200.244.62.12]) by hub.freebsd.org (Postfix) with ESMTP id 3613037B65D for ; Sat, 10 Feb 2001 11:44:53 -0800 (PST) Received: (from prallon@localhost) by liliput.tmp.com.br (8.8.8/8.8.8) id RAA26152; Sat, 10 Feb 2001 17:44:31 -0200 Date: Sat, 10 Feb 2001 17:44:31 -0200 From: Sergio de Souza Prallon To: Igor Prystay Cc: freebsd-isdn@freebsd.org Subject: Re: Teles/PCI card Message-ID: <20010210174431.A26048@tmp.com.br> References: <3A81C486.3A764FA6@inobject.com> <20010207232601.A8398@tmp.com.br> <000901c093d9$4a0c24b0$5100a8c0@iptest> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000901c093d9$4a0c24b0$5100a8c0@iptest>; from igorp@inobject.com on Sat, Feb 10, 2001 at 07:16:20PM -0800 X-URL: http://www.tmp.com.br Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Feb 10, 2001 at 07:16:20PM -0800, Igor Prystay wrote: > > Hi Sergio ! > Thank You for answer > You're right - it was my provider problems, next day no probems with access > to your site, I compiled the driver without any problem > But now I have a problems with configuration - if this is posible could you > give me some recomendation ? > I spent a lot of time tryeing figured out why it doesn't work but without > success ... Under NT it works fine. > > Igor > I had a look at your trace output and I believe I've found the `nature' of your problems. I am not an expert in L2 or L3 so I'm relaying to the list (freebsd-isdn@freebsd.org -- if you're not subscribed you should consider doing so) in the hope to get a more precise diagnostic. Scroll down to the isdntrace output below. > from my dmesg.log : > > Feb 10 17:30:15 test /kernel: itjc0: port 0xd800-0xd8ff mem > 0xfeaff000-0xfeafffff irq 9 at device 10.0 on pci2 > Feb 10 17:30:15 test /kernel: itjc0: ISAC 2186 Version 1.1 (IOM-2) > Feb 10 17:30:15 test /kernel: itjc0: passive stack unit 0 > Feb 10 17:30:15 test /kernel: rl0: port > 0xd400-0xd4ff mem 0xfeafec00-0xfeafecff irq 9 at device 12.0 on pci2 > Feb 10 17:30:15 test /kernel: rl0: Ethernet address: 00:00:21:03:76:8f > Feb 10 17:30:15 test /kernel: miibus0: on rl0 > Feb 10 17:30:15 test /kernel: rlphy0: on > miibus0 > Feb 10 17:30:15 test /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, > 100baseTX-FDX, auto > Feb 10 17:30:15 test /kernel: isab0: > at device 31.0 on pci0 > Feb 10 17:30:15 test /kernel: isa0: on isab0 > Feb 10 17:30:15 test /kernel: atapci0: port > 0xffa0-0xffaf at device 31.1 on pci0 > Feb 10 17:30:15 test /kernel: ata0: at 0x1f0 irq 14 on atapci0 > Feb 10 17:30:15 test /kernel: ata1: at 0x170 irq 15 on atapci0 > Feb 10 17:30:15 test /kernel: pci0: at > 31.2 irq 10 > Feb 10 17:30:15 test /kernel: pci0: (vendor=0x8086, > dev=0x2413) at 31.3 irq 11 > Feb 10 17:30:15 test /kernel: fdc0: direction bit not set > Feb 10 17:30:15 test /kernel: fdc0: cmd 3 failed at out byte 1 of 3 > Feb 10 17:30:15 test /kernel: atkbdc0: at port > 0x60,0x64 on isa0 > Feb 10 17:30:15 test /kernel: vga0: at port 0x3c0-0x3df > iomem 0xa0000-0xbffff on isa0 > Feb 10 17:30:15 test /kernel: sc0: at flags 0x100 on isa0 > Feb 10 17:30:15 test /kernel: sc0: VGA <16 virtual consoles, flags=0x300> > Feb 10 17:30:15 test /kernel: sio0: configured irq 4 not in bitmap of probed > irqs 0 > Feb 10 17:30:15 test /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on > isa0 > Feb 10 17:30:15 test /kernel: sio0: type 8250 > Feb 10 17:30:15 test /kernel: sio1: configured irq 3 not in bitmap of probed > irqs 0 > Feb 10 17:30:15 test /kernel: ppc0: parallel port not found. > Feb 10 17:30:15 test /kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) > attached (VJ header compression) > Feb 10 17:30:15 test /kernel: i4bctl: ISDN system control port attached > Feb 10 17:30:15 test /kernel: IP packet filtering initialized, divert > disabled, rule-based forwarding disabled, default to deny, logging limited > to 100 packets/entry by default > Feb 10 17:30:15 test /kernel: i4brbch: 4 raw B channel access device(s) > attached > Feb 10 17:30:15 test /kernel: i4b: ISDN call control device attached > Feb 10 17:30:15 test /kernel: i4btrc: 4 ISDN trace device(s) attached > Feb 10 17:30:15 test /kernel: ad0: 8063MB [16383/16/63] > at ata0-master UDMA66 > Feb 10 17:30:15 test /kernel: ad1: 19458MB [39535/16/63] at > ata1-master UDMA33 > Feb 10 17:30:15 test /kernel: Mounting root from ufs:/dev/ad0s1a > Feb 10 17:30:20 test su: igorp to root on /dev/ttyp0 > Feb 10 17:30:36 test isdnd[88]: DMN monitor opened from > localhost.inobject.com (127.0.0.1) rights 0x1 > Feb 10 17:30:47 test su: igorp to root on /dev/ttyp1 > Feb 10 17:31:56 test su: igorp to root on /dev/ttyp2 > Feb 10 17:33:16 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:16 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_DL > Feb 10 17:33:16 test /kernel: i4b: unit 0, assigned TEI = 96 = 0x60 > Feb 10 17:33:16 test /kernel: ESTRQ! > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXRR! > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_rxd_i_frame: ERROR, state != (MF || > TR)! > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_T200EXP! > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXRR! > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXRR! > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXRR! > Feb 10 17:33:22 test /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = > 2 > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_dl_data_req: unit 0 ERROR in state > [ST_EST_AW_TEI], freeing mbuf > Feb 10 17:33:22 test /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = > 47 > Feb 10 17:33:22 test /kernel: i4b-L3 next_l3state: FSM illegal state, state > = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:22 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:22 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:25 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:25 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:25 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:25 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:31 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:31 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:31 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:31 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:31 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:31 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:33:31 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > Feb 10 17:33:31 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > state = ST_EST_AW_TEI, event = EV_RXSABME! > Feb 10 17:41:53 test isdnd[88]: DMN monitor closed from > localhost.inobject.com (127.0.0.1) > Feb 10 17:41:54 test isdnd[88]: DMN monitor opened from > localhost.inobject.com (127.0.0.1) rights 0x1 > Feb 10 17:41:58 test isdnd[88]: DMN monitor closed from > localhost.inobject.com (127.0.0.1) > > su-2.04# uname -a > FreeBSD test.inobject.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Feb 10 > 16:18:57 GMT 2001 > root@test.inobject.com:/usr/src/sys/compile/IOBJ_ISDN_IPR i386 > > from log of my isdntrace : > > -- TE->NT - unit:0 - frame:000003 - time:10.02 17:33:16.400080 - > length:8 ------ > Dump:000 fc ff 03 0f a9 34 01 ff .....4.. > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x34a9, IdRequest, Ai=127 > > -- NT->TE - unit:0 - frame:000004 - time:10.02 17:33:16.410081 - > length:8 ------ > Dump:000 fe ff 03 0f a9 34 02 c1 .....4.. > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x34a9, IdAssign, Ai=96 > > -- TE->NT - unit:0 - frame:000005 - time:10.02 17:33:16.410081 - > length:3 ------ > Dump:000 00 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000006 - time:10.02 17:33:16.420079 - > length:3 ------ > Dump:000 00 c1 73 ..s > Q921: SAP=0 (Call Control), R, TEI=96, U-Frame: UA PF 1 > > -- TE->NT - unit:0 - frame:000007 - time:10.02 17:33:16.420079 - > length:39 ----- > Dump:000 00 c1 00 00 .... > Q921: SAP=0 (Call Control), C, TEI=96, I-Frame: N(S) 0 N(R) 0 P 0 > Dump:004 08 01 02 05 a1 04 02 88 90 18 01 83 6c 07 81 39 > ............l..9 > Dump:020 37 30 34 33 32 70 0c 81 38 37 30 37 35 30 30 33 > 70432p..87075003 > Dump:036 33 33 33 333 > Q931: pd=Q.931/I.451, cr=0x02 (from origination), message=SETUP: > [sending complete] > [bearer capability: > cap=unrestricted digital information > std=CCITT > rate=64 kbit/s > mode=circuit] > [channel id: channel=any channel (preferred)] > [calling party number: 970432 (type=unknown, plan=ISDN)] > [called party number: 87075003333 (type=unknown, plan=ISDN)] > > -- NT->TE - unit:0 - frame:000008 - time:10.02 17:33:16.450079 - > length:4 ------ > Dump:000 00 c1 01 02 .... > Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 1 PF 0 > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Until here everything looks just fine. I have even compared the isdntrace of a successful connection attempt I've made with yours, and despite the phone numbers, they are almost identical. > -- NT->TE - unit:0 - frame:000009 - time:10.02 17:33:16.610080 - > length:15 ----- > Dump:000 02 c1 00 02 .... > Q921: SAP=0 (Call Control), C, TEI=96, I-Frame: N(S) 0 N(R) 1 P 0 > Dump:004 08 01 82 7d 08 02 82 e4 14 01 01 ...}....... > Q931: pd=Q.931/I.451, cr=0x02 (from destination), message=STATUS: > [cause: 100: Invalid information element contents (Q.850) > (location=public network serving local user, std=CCITT)] > [call state: Std=CCITT, State=Call initiated] > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< This is (I think) an exchange generated message saying it disliked something on the previous `SETUP' frame. My guess are the phone numbers since the other bytes on the hex dump are the same of my own `SETUP'. Double check them (both originating and destination). Another possibility is the bearer capability: perhaps it wants a more `strict' one, stating it is a `DATA' call. This message apparently didn't get well on the L2/L3 FSMs because it remained unacknoledged as we can see from the 3 frames below. > -- NT->TE - unit:0 - frame:000010 - time:10.02 17:33:17.760092 - > length:4 ------ > Dump:000 02 c1 01 03 .... > Q921: SAP=0 (Call Control), C, TEI=96, S-Frame: RR N(R) 1 PF 1 > > -- NT->TE - unit:0 - frame:000011 - time:10.02 17:33:18.960104 - > length:4 ------ > Dump:000 02 c1 01 03 .... > Q921: SAP=0 (Call Control), C, TEI=96, S-Frame: RR N(R) 1 PF 1 > > -- NT->TE - unit:0 - frame:000012 - time:10.02 17:33:20.160117 - > length:4 ------ > Dump:000 02 c1 01 03 .... > Q921: SAP=0 (Call Control), C, TEI=96, S-Frame: RR N(R) 1 PF 1 > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< I don't know if the following ones are allowed by the specs: apparently the exchange is trying to re-establish the connection (L2). I4B doesn't seems to like it. > -- NT->TE - unit:0 - frame:000013 - time:10.02 17:33:21.360130 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000014 - time:10.02 17:33:22.560143 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000015 - time:10.02 17:33:23.760155 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000016 - time:10.02 17:33:24.960168 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Concluding that something wrong occurred at the TE, the exchange trys to restart the connection by reassuring the TEI of the caller (your machine). > -- NT->TE - unit:0 - frame:000017 - time:10.02 17:33:26.160180 - > length:8 ------ > Dump:000 fe ff 03 0f 00 00 04 c1 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=96 > > -- TE->NT - unit:0 - frame:000018 - time:10.02 17:33:26.160180 - > length:8 ------ > Dump:000 fc ff 03 0f 1b fe 05 c1 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0xfe1b, IdCheckResp, Ai=96 > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Then, it trys again to get the L2 connection back. I think the L2 FSM, once in the error state, does not allow the receive of a `SABME' frame. Again, I don't know if what the exchange is trying to do is even correct, since it is not the originator. I'm still digging thru L1 specs (thanks Hellmuth for the pointers) in my ISDN learning curve... 8-) These are my conclusions made from the observation of your logs. They are by no means irrefutable. If someone on the list can give us any other clue, I'd be glad to hear. > -- NT->TE - unit:0 - frame:000019 - time:10.02 17:33:26.180181 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000020 - time:10.02 17:33:27.360193 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000021 - time:10.02 17:33:28.550205 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000022 - time:10.02 17:33:29.750218 - > length:3 ------ > Dump:000 02 c1 7f ... > Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: SABME PF 1 > > -- NT->TE - unit:0 - frame:000023 - time:10.02 17:33:30.960231 - > length:8 ------ > Dump:000 fe ff 03 0f 00 00 04 c1 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=96 > > -- TE->NT - unit:0 - frame:000024 - time:10.02 17:33:30.960231 - > length:8 ------ > Dump:000 fc ff 03 0f fc d0 05 c1 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0xd0fc, IdCheckResp, Ai=96 > > -- NT->TE - unit:0 - frame:000025 - time:10.02 17:33:41.160338 - > length:8 ------ > Dump:000 fe ff 03 0f 00 00 04 c1 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=96 > > -- TE->NT - unit:0 - frame:000026 - time:10.02 17:33:41.160338 - > length:8 ------ > Dump:000 fc ff 03 0f 00 53 05 c1 .....S.. > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x5300, IdCheckResp, Ai=96 > > -- NT->TE - unit:0 - frame:000027 - time:10.02 17:34:54.351110 - > length:8 ------ > Dump:000 fe ff 03 0f 00 00 04 c5 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=98 > > -- NT->TE - unit:0 - frame:000028 - time:10.02 17:35:43.141625 - > length:8 ------ > Dump:000 fe ff 03 0f 00 00 04 c1 ........ > Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=96 > > my isdnd.rc : > > system > > acctall = on > acctfile = /var/log/isdnd.acct > useacctfile = yes > isdntime = on > monitor-allowed = yes > monitor = "127.0.0.1" > monitor-access = fullcmd > beepconnect = on > > controller > protocol = dss1 > > entry > name = userppp0 > usrdevicename = rbch > usrdeviceunit = 0 > isdncontroller = 0 > isdnchannel = -1 > local-phone-dialout = 970432 > local-phone-incoming = 970432 > remote-phone-dialout = 87075003333 > remote-phone-incoming = * > b1protocol = hdlc > dialin-reaction = ignore > dialout-type = normal > direction = out > dialrandincr = on > dialretries = -1 > recoverytime = 1 > usedown = off > downtries = 10 > downtime = 30 > #idle-algorithm-outgoing = fix-unit-size > idle-algorithm-outgoing = var-unit-size > idletime-incoming = 900 > idletime-outgoing = 900 > unitlengthsrc = conf > unitlength = 0 > remdial-handling = first > > entry > name = userppp1 > usrdevicename = rbch > usrdeviceunit = 1 > isdncontroller = 0 > isdnchannel = -1 > local-phone-dialout = 970432 > local-phone-incoming = 970432 > remote-phone-dialout = 87075003333 > remote-phone-incoming = * > b1protocol = hdlc > dialin-reaction = ignore > dialout-type = normal > direction = out > dialrandincr = on > dialretries = -1 > recoverytime = 1 > usedown = off > downtries = 10 > downtime = 30 > #idle-algorithm-outgoing = fix-unit-size > idle-algorithm-outgoing = var-unit-size > idletime-incoming = 900 > idletime-outgoing = 900 > unitlengthsrc = conf > unitlength = 0 > remdial-handling = first > > my ppp.conf : > > default: > isdn: > set log phase chat lcp ipcp ccp command > set phone 87075003333 > set authname name > set authkey password > # set enddisc mac > enable lqr > set reconnect 3 5 > set redial 3 10 > set lqrperiod 45 > disable pred1 deflate mppe > deny pred1 deflate mppe > set timeout 60 300 > set dial > set login > set logout > set hangup > set device /dev/i4brbch0 /dev/i4brbch1 > set speed sync > enable dns > set ifaddr 212.113.40.176/0 10.3.1.20/0 > add! default hisaddr > set mrru 1500 > set mru 1504 > clone 1,2 > link deflink rm > link * set mode auto > set autoload 10 80 30 > set server /tmp/ppp-isdn "" 0177 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message