From owner-freebsd-isdn Sun Nov 1 12:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01017 for freebsd-isdn-outgoing; Sun, 1 Nov 1998 12:27:02 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from harvey.aball.de (harvey.aball.de [194.77.82.26]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA01010 for ; Sun, 1 Nov 1998 12:26:59 -0800 (PST) (envelope-from alice.turbocat.de!dave@harvey.aball.de) Received: by harvey.aball.de (Smail3.1.28.1 #11) id m0za45D-000IvgC; Sun, 1 Nov 98 21:26 MET Received: from cat.turbocat.de (cat.turbocat.de [194.77.82.49]) by alice.turbocat.de (8.8.8/8.7.3) with ESMTP id UAA03844; Sun, 1 Nov 1998 20:09:28 +0100 (CET) Received: (from dave@localhost) by cat.turbocat.de (8.8.5/8.7.3) id UAA00276; Sun, 1 Nov 1998 20:09:28 +0100 (MET) Message-Id: <199811011909.UAA00276@cat.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: Sun, 1 Nov 98 20:09:27 +0100 To: Jan-Hinrich Fessel Subject: Re: new mainboard - new fun :-( cc: ISDN-List References: <199810311443.PAA27354@zippo.unna.ping.de> Organisation: Turbocat's Development http://www.turbocat.de Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Jan-Hinrich Fessel (...) > You did tell BIOS that the card uses IRQ and mem? I did it with the IRQ but have no Idea how to do it with the mem. I will review the manual of my Gigabyte GA6BXS Board. I would be happe if somone could give me a hint. --- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 NeXTmail dave@turbocat.de (______) http://www.turbocat.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Nov 2 23:04:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27500 for freebsd-isdn-outgoing; Mon, 2 Nov 1998 23:00:43 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27102 for ; Mon, 2 Nov 1998 22:55:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA09221; Mon, 2 Nov 1998 22:55:42 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma009215; Mon Nov 2 22:55:21 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA03973; Mon, 2 Nov 1998 22:55:20 -0800 (PST) From: Archie Cobbs Message-Id: <199811030655.WAA03973@bubba.whistle.com> Subject: Re: Sheesh - now what... In-Reply-To: <199810311233.XAA08994@mail.aussie.org> from Hallam Oaks at "Oct 31, 98 11:31:44 pm" To: mlnn4@oaks.com.au Date: Mon, 2 Nov 1998 22:55:20 -0800 (PST) Cc: FreeBSD-ISDN@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Hallam Oaks writes: > On Fri, 30 Oct 1998 10:53:55 -0600, William McVey wrote: > > >their own way and ignored the rest of the world. So we need docs that > >allow us to identify how the US standards differ from the ISTEC stuff > >so that we can put in support for them. > > I can't answer the docs question, but can say that I have been told that > there are something like three to five different implementations of ISDN in > the USA. Which one you get depends on where you live. Sheesh indeed ;( Just supporting NI-1 would probably cover "most" ISDN switches. Bellcore publishes the NI-1 spec(s). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Nov 3 11:23:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25041 for freebsd-isdn-outgoing; Tue, 3 Nov 1998 11:23:40 -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.8/8.8.8) with ESMTP id LAA25032 for ; Tue, 3 Nov 1998 11:23:37 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id UAA13313 for ; Tue, 3 Nov 1998 20:19:06 +0100 (CET) Message-Id: <199811031919.UAA13313@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-isdn@FreeBSD.ORG Subject: Re: Sheesh - now what... Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 02 Nov 1998 22:55:20 PST." <199811030655.WAA03973@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 20:19:06 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Archie Cobbs writes: >Hallam Oaks writes: >> On Fri, 30 Oct 1998 10:53:55 -0600, William McVey wrote: >> >> >their own way and ignored the rest of the world. So we need docs that >> >allow us to identify how the US standards differ from the ISTEC stuff >> >so that we can put in support for them. >> >> I can't answer the docs question, but can say that I have been told that >> there are something like three to five different implementations of ISDN in >> the USA. Which one you get depends on where you live. Sheesh indeed ;( > >Just supporting NI-1 would probably cover "most" ISDN switches. >Bellcore publishes the NI-1 spec(s). > and how do we poor Europeans get our mitts on it ? Does Bellcore have a webpage with pointers to documentation ? --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Nov 3 23:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11686 for freebsd-isdn-outgoing; Tue, 3 Nov 1998 23:48:34 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11663 for ; Tue, 3 Nov 1998 23:48:19 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id IAA20079 for freebsd-isdn@FreeBSD.ORG; Wed, 4 Nov 1998 08:45:32 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id IAA03177 for freebsd-isdn@FreeBSD.ORG; Wed, 4 Nov 1998 08:37:16 +0100 (CET) (envelope-from andreas) Message-ID: <19981104083715.A462@klemm.gtn.com> Date: Wed, 4 Nov 1998 08:37:15 +0100 From: Andreas Klemm To: freebsd-isdn@FreeBSD.ORG Subject: am upgrading from 2.2.7-STABLE to -current, any trouble to expect ? Reply-To: freebsd-isdn@FreeBSD.ORG, andreas.klemm.ak@bayer-ag.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! I want to install i4b on a -current of today ... The aout -> elf build process is just running ... Do you think it's doable, to fire up the install target, to move to -current ? About one-two months ago I was running -current. Then I had a system crash and installed 2.2.7, so I'm a bit out of date regarding i4b+-current+SMP ... Thanks Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Nov 4 12:58:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03563 for freebsd-isdn-outgoing; Wed, 4 Nov 1998 12:58:31 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03558 for ; Wed, 4 Nov 1998 12:58:30 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA29918; Wed, 4 Nov 1998 12:58:15 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma029916; Wed Nov 4 12:57:48 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA00706; Wed, 4 Nov 1998 12:57:47 -0800 (PST) From: Archie Cobbs Message-Id: <199811042057.MAA00706@bubba.whistle.com> Subject: Re: Sheesh - now what... In-Reply-To: <199811031919.UAA13313@peedub.muc.de> from Gary Jennejohn at "Nov 3, 98 08:19:06 pm" To: garyj@muc.de Date: Wed, 4 Nov 1998 12:57:47 -0800 (PST) Cc: freebsd-isdn@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Gary Jennejohn writes: > Archie Cobbs writes: > >Hallam Oaks writes: > >> On Fri, 30 Oct 1998 10:53:55 -0600, William McVey wrote: > >> > >> >their own way and ignored the rest of the world. So we need docs that > >> >allow us to identify how the US standards differ from the ISTEC stuff > >> >so that we can put in support for them. > >> > >> I can't answer the docs question, but can say that I have been told that > >> there are something like three to five different implementations of ISDN > >> the USA. Which one you get depends on where you live. Sheesh indeed ;( > > > >Just supporting NI-1 would probably cover "most" ISDN switches. > >Bellcore publishes the NI-1 spec(s). > > > > and how do we poor Europeans get our mitts on it ? Does Bellcore have a > webpage with pointers to documentation ? http://telecom-info.bellcore.com/site-cgi/ido/index.html ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Nov 4 13:56:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13184 for freebsd-isdn-outgoing; Wed, 4 Nov 1998 13:53:52 -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.8/8.8.8) with ESMTP id NAA13166 for ; Wed, 4 Nov 1998 13:53:41 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id WAA15202 for ; Wed, 4 Nov 1998 22:50:29 +0100 (CET) Message-Id: <199811042150.WAA15202@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-isdn@freebsd.org Subject: Re: am upgrading from 2.2.7-STABLE to -current, any trouble to expect ? Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 04 Nov 1998 08:37:15 +0100." <19981104083715.A462@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Nov 1998 22:50:29 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@freebsd.org Precedence: bulk X-Loop: FreeBSD.org Andreas Klemm writes: >Hi ! > >I want to install i4b on a -current of today ... >The aout -> elf build process is just running ... >Do you think it's doable, to fire up the install >target, to move to -current ? > >About one-two months ago I was running -current. Then I had >a system crash and installed 2.2.7, so I'm a bit out of date >regarding i4b+-current+SMP ... > I'm running on a -current elf-ized system, but not SMP. Be aware that you have to modify i4b_isic.c (I already sent a patch to the list) to register the interrupt handler. Oh yeah, and delete the "vector isicintr" from your kernel config file. There was also a problem with compiling isdnd because no y.tab.h is generated under -current. A patch for this was also sent to the list. That's all I can think of att. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Nov 5 05:06:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07702 for freebsd-isdn-outgoing; Thu, 5 Nov 1998 05:06:51 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from www.labcontrol.com (www.labcontrol.com [194.163.70.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA07697 for ; Thu, 5 Nov 1998 05:06:48 -0800 (PST) (envelope-from Marc_van_Woerkom@notes.labcontrol.com) From: Marc_van_Woerkom@notes.labcontrol.com Received: from www.labcontrol.com [194.163.70.129] by mail.labcontrol.com with smtp id JSJLYYSI; Thu, 05 Nov 98 13:06:32 GMT (PowerWeb version 4.07r4) Received: by notes.labcontrol.com(Lotus SMTP MTA v1.06 (346.4 3-18-1997)) id C12566B3.0048059F ; Thu, 5 Nov 1998 14:06:40 +0200 X-Lotus-FromDomain: LABCONTROL GMBH To: garyj@muc.de cc: freebsd-isdn@FreeBSD.ORG, de-bsd-questions@de.freebsd.org Message-ID: Date: Thu, 5 Nov 1998 14:06:38 +0200 Subject: Re: am upgrading from 2.2.7-STABLE to -current, any trouble to expect ? Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc van Woerkom 05.11.98 14.06 Two days ago, I cvsuped -current, coming from a freshly built 2.2.7 with i4b driving a Teles ISDN card. Yesterday I reported my troubles - buildworld ran fine, installworld & kernel build processes hanged at various stages - to the de-bsd-questions list. In the meantime I succeded to build a working 3.0-current, alas with dysfunctional i4b (see your remark below): A) Running a decent 3.0 (aout) Main cause of my problems seems to be the "chicken and egg" type of problem that the 3.0 build process (as of 2/3th November) needs certain tools (and maybe even kernel calls) in 3.0 flavour ideally all these critical targets would be build and installed first, to have a working set of tools. At least in my case, the build process did not work this way. So I took a -current kernel from September, when I last attempted to upgrade, and used the boot loader from a 3.0 boot floppy to fire up my system (older -current kernel, up to date -current sources and a mix of -current and -stable tools and libraries). This worked out, and I was able to track down tools that had to be ugraded to 3.0 (e.g. cd ../kbdcontrol; make; make install) by hand. Some makefiles in the /modules section had to be modified too, they produced *.ko results but tried to install without this suffix (e.g. 'linux' instead of 'linux.ko'): After lots of iterations, make installworld finally ran smooth, and I was able to produce an up to date GENERIC kernel, that worked fine after reboot. B) Running X11 on top of it To make X11, windowmaker and wdm working again, I had to move /usr/X11R6/lib/lib* to /usr/X11R6/lib/aout, the same for /usr/local/lib. Gimp, Emacs, xcdplayer etc. work fine, Netscape Communicator 4.5 is the only X11 app so far that seems not to work. I'll try a reinstall of the package later, followed by a recompilation of X11 (btw 3.3.3 is expected this month) C) Building a customized kernel with i4b When rebuilding -stable, all I had to do was running i4b's uninstall.sh and install.sh again, eventually rebuilding i4b and so it was easy to build the kernel. Now there is a little problem, in that i4b modifies 5 files and stores -BACKUP versions of them. These backups were 2.2.7 versions, and the the uninstall.sh script is not able to figure out, that it should not replace those 3.0 files (flooded in via cvsup) with the outdated backups. Removed the backups and removed some lines at the end of options.i386 that were already present from the prior 2.2.7 installation. By comparison with -current GENERIC and -current LINT, I was able to upgrade my old CUSTOM config to -current. > Oh yeah, and delete the "vector isicintr" from your kernel config file. This is one of the things I infered from comparison. Where I was unsure was: I put a sppp device into the config file, but no ppp and no tun devices - is this OK? The so won kernel compiled and booted properly, but i4b did not work properly, it hung after the "dialing 0123.." message. It's likely I ran into this: > Be aware that you have to modify i4b_isic.c (I already sent a > patch to the list) to register the interrupt handler. Alas I had no trouble here: > There was also a problem with compiling isdnd because no y.tab.h is > generated under -current. A patch for this was also sent to the > list. Compiling isdnd was no problem. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Nov 5 05:10:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08149 for freebsd-isdn-outgoing; Thu, 5 Nov 1998 05:10:21 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from slarti.muc.de (slarti.muc.de [193.174.4.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA08138 for ; Thu, 5 Nov 1998 05:10:14 -0800 (PST) (envelope-from ag@ncolin.muc.de) Received: (qmail 19991 invoked from network); 5 Nov 1998 13:09:19 -0000 Received: from ncolin.muc.de (193.174.4.11) by slarti.muc.de with SMTP; 5 Nov 1998 13:09:19 -0000 Received: (from ag@localhost) by ncolin.muc.de (8.8.8/8.8.8) id OAA29707; Thu, 5 Nov 1998 14:12:25 +0100 (CET) (envelope-from ag) Message-ID: <19981105141225.A29699@muc.de> Date: Thu, 5 Nov 1998 14:12:25 +0100 From: Armin Gruner To: freebsd-isdn@FreeBSD.ORG Subject: Win95 and connection to isdn4bsd on FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Summary: i4b 0.63 @ FreeBSD, dialup with Windows95 Keywords: LCP, async map Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am trying to connect with a WIN95 machine and the dialup network to a FreeBSD box, running 22.7 and i4b 0.63. It looks like WIN95 PPP is insisting on an async-map, and thus the negotiation fails: isppp0: lcp up(starting) isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic proto-comp [rej] addr-comp [rej] 0xd [rej] send conf-rej isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a send conf-nak isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a max_failure (10) exceeded, send conf-rej isppp0: lcp output isppp0: lcp TO(req-sent) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp input(ack-rcvd): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a max_failure (10) exceeded, send conf-rej isppp0: lcp output isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp input(ack-rcvd): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a max_failure (10) exceeded, send conf-rej isppp0: lcp output isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp input(ack-rcvd): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a max_failure (10) exceeded, send conf-rej isppp0: lcp output isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp input(ack-rcvd): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a max_failure (10) exceeded, send conf-rej isppp0: lcp output isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp input(ack-rcvd): isppp0: lcp parse opts: async-map magic isppp0: lcp parse opt values: async-map [non-empty] magic 0x7900a max_failure (10) exceeded, send conf-rej isppp0: lcp output isppp0: lcp TO(ack-rcvd) rst_counter = 10 isppp0: lcp output isppp0: lcp input(req-sent): isppp0: lcp input(ack-rcvd): isppp0: lcp send terminate-ack isppp0: lcp output isppp0: lcp down(req-sent) isppp0: Down event (carrier loss), taking interface down. isppp0: lcp close(starting) isppp0: phase dead Anything which can done be about it? When I connect to dialup equipment with debugging set on (Netblazer), I see what Win95 is requesting: PPP PPP/Lcp Ack Rcvd; Processing Config Req, id: 2 lcp_request() checking ACCM: 0x000a0000 LCP REQ: result Config Ack, option 2 making ACCM: 0x000a0000 checking Magic Number: 0x004cfc72 LCP REQ: result Config Ack, option 5 making Magic Number: 0x004cfc72 checking Protocol compression LCP REQ: result Config Ack, option 7 making Protocol compression checking Addr/Ctl compression LCP REQ: result Config Ack, option 8 making Addr/Ctl compression LCP REQ: result Config Reject, option 13 making unimplemented type 13 PPP PPP/Lcp Ack Rcvd; Sending Config Reject, id: 2 fsm_timer(Lcp) PPP PPP/Lcp Ack Rcvd; Processing Config Req, id: 3 lcp_request() checking ACCM: 0x000a0000 LCP REQ: result Config Ack, option 2 making ACCM: 0x000a0000 checking Magic Number: 0x004cfc72 LCP REQ: result Config Ack, option 5 making Magic Number: 0x004cfc72 checking Protocol compression LCP REQ: result Config Ack, option 7 making Protocol compression checking Addr/Ctl compression LCP REQ: result Config Ack, option 8 making Addr/Ctl compression PPP PPP/Lcp Ack Rcvd; Sending Config Ack, id: 3 PPP PPP/Lcp Ack Rcvd; Opened lcp_opening() pap_local() Received PAP: Pap id: 1 len: 20 pap_request() It looks like WIN95 is request an async-map of 0x000a0000 ? Now the question is: Did anyone succeed in connecting to a i4b server with Win95? Or, can Win95 be told that it should not use an async map over a sync HDLC connection. Or, can I simply change the isppp.c-code to not send a REJ? Thanks! Armin -- Armin Gruner ____ mailto:ag@muc.de ``Nur wer sich aendert, bleibt \ / http://www.leo.org/~gruner/ sich treu'' - Wolf Biermann \/ PGP Public Key: finger -l ag@muc.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Nov 5 13:24:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03527 for freebsd-isdn-outgoing; Thu, 5 Nov 1998 13:24:03 -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.8/8.8.8) with ESMTP id NAA03476 for ; Thu, 5 Nov 1998 13:23:58 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id WAA16768 for ; Thu, 5 Nov 1998 22:12:32 +0100 (CET) Message-Id: <199811052112.WAA16768@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-isdn@FreeBSD.ORG Subject: Re: am upgrading from 2.2.7-STABLE to -current, any trouble to expect ? Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 05 Nov 1998 14:06:38 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 22:12:31 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc_van_Woerkom@notes.labcontrol.com writes: [lots of stuff deleted] >Where I was unsure was: > >I put a sppp device into the config file, but no ppp and no tun >devices - is this OK? > [more stuff deleted] yes, i4b doesn't use ppp or tun. Of course, if you want to use ijppp with a modem at some time then you need tun. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Nov 5 13:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06871 for freebsd-isdn-outgoing; Thu, 5 Nov 1998 13:47:38 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06866 for ; Thu, 5 Nov 1998 13:47:36 -0800 (PST) (envelope-from marc@netcologne.de) Received: from oranje.my.domain (dial10-50.netcologne.de [195.14.235.50]) by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id WAA01257; Thu, 5 Nov 1998 22:47:18 +0100 (MET) X-Ncc-Regid: de.netcologne Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.1) id WAA01658; Thu, 5 Nov 1998 22:46:50 +0100 (CET) (envelope-from marc) Date: Thu, 5 Nov 1998 22:46:50 +0100 (CET) Message-Id: <199811052146.WAA01658@oranje.my.domain> From: Marc van Woerkom To: garyj@muc.de CC: freebsd-isdn@FreeBSD.ORG In-reply-to: <199811042150.WAA15202@peedub.muc.de> (message from Gary Jennejohn on Wed, 04 Nov 1998 22:50:29 +0100) Subject: Re: am upgrading from 2.2.7-STABLE to -current, any trouble to expect ? Reply-to: van.woerkom@netcologne.de Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Be aware that you have to modify i4b_isic.c (I already sent > a patch to the list) to register the interrupt handler. That was the missing piece - thanks a lot! It's wooorking agaiiin... Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Nov 6 02:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13709 for freebsd-isdn-outgoing; Fri, 6 Nov 1998 02:39:53 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13703 for ; Fri, 6 Nov 1998 02:39:49 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (root@rumolt.teuto.de [194.77.23.161]) by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id LAA23652; Fri, 6 Nov 1998 11:39:33 +0100 Received: from hwart (hwart.teuto.de [194.77.23.163]) by rumolt.teuto.de (8.8.8/8.8.7) with SMTP id LAA05295; Fri, 6 Nov 1998 11:38:54 +0100 (MET) From: "Martin Husemann" To: "Armin Gruner" , Subject: RE: Win95 and connection to isdn4bsd on FreeBSD Date: Fri, 6 Nov 1998 11:38:55 +0100 Keywords: LCP, async map Message-ID: <001301be0971$a766a8f0$a3174dc2@hwart.teuto.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <19981105141225.A29699@muc.de> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It looks like WIN95 is request an async-map of 0x000a0000 ? > > Now the question is: Did anyone succeed in connecting > to a i4b server with Win95? Sorry, didn't try it. > Or, can Win95 be told that it should not use an async > map over a sync HDLC connection. The only relevant entries in the Microsoft Knowledgebase show that NT's RAS doesn't use an asyncmap. Noone ever should use an asyncmap for sync connections! But: how did you configure the Windows 95 dial up connection? There are at least two ways to do it: (1) you can use the infamous capi-to-modem converter driver (the name of which I always forget, was it IModem?) or (2) you can use the network driver delivered with you ISDN card. I've seen this drivers at with AVM cards and USR cards. If you do (1) the system thinks the connection is async, so the observed behaviour is not that brain-dead. If you use (2) it knows about the sync connection and should handle PPP options accordingly (the network card driver talking to the ISDN card has to specify async/sync and bearer capabilities to the PPP session API, so it will probably do the right thing). I always used (2) and never ran into a problem - but I didn't test it against i4b, as I always replaced the Windows 95 ISDN access completely by a router system running i4b ;-) > Or, can I simply change the isppp.c-code to not send > a REJ? No. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Nov 6 05:06:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27572 for freebsd-isdn-outgoing; Fri, 6 Nov 1998 05:06:53 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from devsoft.devsoft.com (devsoft.devsoft.com [194.97.121.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27567 for ; Fri, 6 Nov 1998 05:06:47 -0800 (PST) (envelope-from ag@devsoft.devsoft.com) Received: (from ag@localhost) by devsoft.devsoft.com (8.8.5/8.8.5) id OAA19069; Fri, 6 Nov 1998 14:06:21 +0100 (CET) Message-ID: <19981106140621.C18896@devsoft.com> Date: Fri, 6 Nov 1998 14:06:21 +0100 From: Armin Gruner To: Martin Husemann , freebsd-isdn@FreeBSD.ORG Subject: Re: Win95 and connection to isdn4bsd on FreeBSD References: <19981105141225.A29699@muc.de> <001301be0971$a766a8f0$a3174dc2@hwart.teuto.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <001301be0971$a766a8f0$a3174dc2@hwart.teuto.de>; from Martin Husemann on Fri, Nov 06, 1998 at 11:38:55AM +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 06, 1998 at 11:38:55AM +0100, Martin Husemann wrote: > Noone ever should use an asyncmap for sync connections! Well, sure :) > But: how did you configure the Windows 95 dial up connection? There are at > least two ways to do it: (1) you can use the infamous capi-to-modem > converter driver (the name of which I always forget, was it IModem?) or (2) > you can use the network driver delivered with you ISDN card. I've seen this > drivers at with AVM cards and USR cards. I've installed the NDISWAN drivers that came with the card. I upgraded to Dialup-Network 1.3, which includes also the ISDN accelerator pack 1.1. Now it is questionable if they are really NDISWAN drivers or just modem stubs for the CAPI, not sure about that. The card is a USR ISDN Sportster. Perhaps it won't happen with other software like the online power pack with a Teles card. I will try that, we have one in the company. > If you do (1) the system thinks the connection is async, so the observed > behaviour is not that brain-dead. Sure. If you use (2) it knows about the sync > connection and should handle PPP options accordingly (the network card > driver talking to the ISDN card has to specify async/sync and bearer > capabilities to the PPP session API, so it will probably do the right > thing). Well, I thought the same. But even when I use the setup to connect to a providers PriMUX with sync PPP, it looks like it sends an async map (see my debug outputs for the netblazer connect) > I always used (2) and never ran into a problem - but I didn't test it > against i4b, as I always replaced the Windows 95 ISDN access completely by a > router system running i4b ;-) Well, I am happy with that setup, too. But my boss wants to connect to our FreeBSD route from home, with Windows95 for document (sigh!) exchange.. Armin -- Armin Gruner Forschung und Entwicklung -- Armin Gruner, /dev Software GmbH Fon +49-89-286 598 43 Gabelsberger Str. 51 mailto:ag@devsoft.com D-80333 Muenchen http://www.devsoft.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message