From owner-freebsd-isdn Mon Nov 9 11:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13184 for freebsd-isdn-outgoing; Mon, 9 Nov 1998 11:48:43 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from unidui.uni-duisburg.de (unidui.uni-duisburg.de [134.91.4.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13177 for ; Mon, 9 Nov 1998 11:48:39 -0800 (PST) (envelope-from kurek@unidui.uni-duisburg.de) Received: from uni-duisburg.de (ppp96.uni-duisburg.de [134.91.19.96]) by unidui.uni-duisburg.de (8.8.6/8.8.6) with ESMTP id UAA01092; Mon, 9 Nov 1998 20:47:42 +0100 (MET) Message-ID: <36434881.72BE2438@uni-duisburg.de> Date: Fri, 06 Nov 1998 20:05:37 +0100 From: Markus Kurek X-Mailer: Mozilla 4.5 [en] (X11; I; NetBSD 1.3.2 i386) X-Accept-Language: de,en MIME-Version: 1.0 To: Armin Gruner CC: freebsd-isdn@FreeBSD.ORG Subject: Re: Win95 and connection to isdn4bsd on FreeBSD References: <19981105141225.A29699@muc.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Armin Gruner wrote: > > 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. > Now the question is: Did anyone succeed in connecting > to a i4b server with Win95? Yes. I connected with two different isdn-cards (itk basic and avm fritz) to my netbsd-1.3.2 server. A friend tried to connect with his teles card but failed. I'm not sure if he used the NDISWAN driver. He did not know which driver he used :( Markus Kurek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Nov 10 14:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26018 for freebsd-isdn-outgoing; Tue, 10 Nov 1998 14:23:44 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mac1.hail.net (mac1.hail.net [209.137.84.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25980 for ; Tue, 10 Nov 1998 14:23:42 -0800 (PST) (envelope-from eric@macpublic.com) Received: from [192.168.100.10] (ericsan.dialisdn.com [209.4.68.250]) by mac1.hail.net (8.8.8/8.8.8/Hail/hg.1) with ESMTP id RAA08407 for ; Tue, 10 Nov 1998 17:24:31 -0500 (EST) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="============_-1301385891==_ma============" X-Sender: eric@mail.hail.net Message-Id: Date: Tue, 10 Nov 1998 17:22:27 -0500 To: freebsd-isdn@FreeBSD.ORG From: "Eric L. Santelices" Subject: new user question Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --============_-1301385891==_ma============ Content-Type: text/plain; charset="us-ascii" I have freebsd 2.27 setup and working as a gateway on my 56k modem. I now want to switch it over to my Motorola Bitsurfer Pro. I modified my ppp.conf and put in the init string that worked with my Mac. When I tried to ping a number outside my network I saw the DTE lite flash for a second then the modem did nothing. Here is my init string set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT\Q3%A2=95%A4=0@B0=2@M2=P OK-AT-OK\\dATD\\T TIMEOUT 40 CONNECT" any suggestions? /-------------------------------------------\ Eric L. Santelices macPublic, Inc. 305-232-8756 Voice * 305-259-7576 Fax EMail Pager : pageeric@hail.net http://www.macPublic.com \-------------------------------------------/ --============_-1301385891==_ma============ Content-Type: text/enriched; charset="us-ascii" I have freebsd 2.27 setup and working as a gateway on my 56k modem. I now want to switch it over to my Motorola Bitsurfer Pro. I modified my ppp.conf and put in the init string that worked with my Mac. When I tried to ping a number outside my network I saw the DTE lite flash for a second then the modem did nothing. Here is my init string set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT\Q3%A2=95%A4=0@B0=2@M2=P OK-AT-OK\\dATD\\T TIMEOUT 40 CONNECT" any suggestions? /-------------------------------------------\ Eric L. Santelices macPublic, Inc. 305-232-8756 Voice * 305-259-7576 Fax EMail Pager : pageeric@hail.net http://www.macPublic.com \-------------------------------------------/ --============_-1301385891==_ma============-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Nov 11 06:32:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20138 for freebsd-isdn-outgoing; Wed, 11 Nov 1998 06:32:21 -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 GAA20127 for ; Wed, 11 Nov 1998 06:32:16 -0800 (PST) (envelope-from ag@devsoft.devsoft.com) Received: (from ag@localhost) by devsoft.devsoft.com (8.8.5/8.8.5) id PAA29744; Wed, 11 Nov 1998 15:31:51 +0100 (CET) Message-ID: <19981111153150.A29738@devsoft.com> Date: Wed, 11 Nov 1998 15:31:50 +0100 From: Armin Gruner To: freebsd-isdn@FreeBSD.ORG Subject: SOLVED: Re: Win95 and connection to isdn4bsd on FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: /dev software gmbh Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19981105141225.A29699@muc.de>, Armin Gruner wrote: >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: > >Anything which can done be about it? When I connect to >dialup equipment with debugging set on (Netblazer), I see >what Win95 is requesting: [..] >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? Hi collegues, the problem is solved. It is indeed that Win95 is sending an ASYNCMAP request, even if the connection goes through an ISDN card and the NDISWAN driver. THe problem is, that isdn4bsd (00.63-alpha) is not sending the appropriate NAK/REJ packet (I have enabled the Windows95 PPP log:) 11-09-1998 13:26:32.33 - Remote access driver log opened. 11-09-1998 13:26:32.33 - Installable CP VxD SPAP is loaded 11-09-1998 13:26:32.35 - Server type is PPP (Point to Point Protocol). 11-09-1998 13:26:32.36 - FSA : Software compression disabled. 11-09-1998 13:26:32.36 - FSA : Protocol disabled by user - skipping control protocol 803f (NBFCP). 11-09-1998 13:26:32.36 - FSA : Adding Control Protocol 8021 (IPCP) to control protocol chain. 11-09-1998 13:26:32.36 - FSA : Protocol disabled by user - skipping control protocol 802b (IPXCP). 11-09-1998 13:26:32.36 - FSA : Adding Control Protocol c029 (CallbackCP) to control protocol chain. 11-09-1998 13:26:32.36 - FSA : Adding Control Protocol c027 (no description) to control protocol chain. 11-09-1998 13:26:32.36 - FSA : Adding Control Protocol c023 (PAP) to control protocol chain. 11-09-1998 13:26:32.36 - FSA : Adding Control Protocol c223 (CHAP) to control protocol chain. 11-09-1998 13:26:32.36 - FSA : Adding Control Protocol c021 (LCP) to control protocol chain. 11-09-1998 13:26:32.36 - LCP : Callback negotiation enabled. 11-09-1998 13:26:32.36 - LCP : Layer started. 11-09-1998 13:26:32.39 - LCP : Received configure reject for protocol field compression option. 11-09-1998 13:26:32.39 - LCP : Received configure reject for address field compression option. 11-09-1998 13:26:32.39 - LCP : Received configure reject for callback control protocol option. 11-09-1998 13:26:32.42 - LCP : Received corrupted configure reject for option 2. 11-09-1998 13:26:33.41 - LCP : Received and accepted magic number 365280c3. 11-09-1998 13:26:33.41 - LCP : Received and accepted authentication protocol c023 (PAP). 11-09-1998 13:26:34.44 - LCP : Received and accepted magic number 365280c3. 11-09-1998 13:26:34.44 - LCP : Received and accepted authentication protocol c023 (PAP). 11-09-1998 13:26:35.42 - LCP : Received corrupted configure reject for option 2. 11-09-1998 13:26:36.43 - LCP : Received and accepted magic number 365280c3. 11-09-1998 13:26:36.43 - LCP : Received and accepted authentication protocol c023 (PAP). 11-09-1998 13:26:37.46 - LCP : Received and accepted magic number 365280c3. 11-09-1998 13:26:37.46 - LCP : Received and accepted authentication protocol c023 (PAP). 11-09-1998 13:26:38.43 - LCP : Received corrupted configure reject for option 2. 11-09-1998 13:26:39.42 - LCP : Received and accepted magic number 365280c3. 11-09-1998 13:26:39.42 - LCP : Received and accepted authentication protocol c023 (PAP). 11-09-1998 13:26:40.45 - LCP : Received and accepted magic number 365280c3. 11-09-1998 13:26:40.45 - LCP : Received and accepted authentication protocol c023 (PAP). 11-09-1998 13:26:41.42 - LCP : Received corrupted configure reject for option 2. 11-09-1998 13:26:41.45 - Remote access driver is shutting down. 11-09-1998 13:26:41.45 - CRC Errors 0 11-09-1998 13:26:41.45 - Timeout Errors 0 11-09-1998 13:26:41.45 - Alignment Errors 0 11-09-1998 13:26:41.45 - Overrun Errors 0 11-09-1998 13:26:41.45 - Framing Errors 0 11-09-1998 13:26:41.45 - Buffer Overrun Errors 0 11-09-1998 13:26:41.45 - Incomplete Packets 0 11-09-1998 13:26:41.45 - Bytes Received 179 11-09-1998 13:26:41.45 - Bytes Transmittted 215 11-09-1998 13:26:41.45 - Frames Received 11 11-09-1998 13:26:41.45 - Frames Transmitted 11 11-09-1998 13:26:41.48 - LCP : Received terminate acknowledgement. 11-09-1998 13:26:41.48 - LCP : Layer finished. 11-09-1998 13:26:41.48 - Remote access driver log closed. By looking at the i4b sources, I see that the original sync PPP driver frome Serge has been modified; now it perhaps send a wrong NAK to the async map request. Moreover, it should perhaps send a REJ to the option, not a NAK. /* * pass 2: check for option values that are unacceptable and * thus require to be nak'ed. */ [...] case LCP_OPT_ASYNC_MAP: /* Async control character map -- check to be zero. */ if (! p[2] && ! p[3] && ! p[4] && ! p[5]) { if (debug) addlog("[empty] "); continue; } if (debug) addlog("[non-empty] "); /* suggest a zero one */ p[2] = p[3] = p[4] = p[5] = 0; break; Anyway, if I remove the "p[2] = p[3] = p[4] = p[5] = 0;", the driver sends back the original async map request with a NAK, and the errors in the Win95 ppp log go away. After 10 times, the i4b driver sends a REJ to the ASYNCMAP request, so it looks that basically any ASYNCMAP request should be rejected in ppp_lcp_RCR(), not NAK'ed. I will modify the sources and try it out. Now I successfully connect with a Teles card and a USR STI card. Thanks for all replies! 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 From owner-freebsd-isdn Wed Nov 11 07:17:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24920 for freebsd-isdn-outgoing; Wed, 11 Nov 1998 07:17:05 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24913 for ; Wed, 11 Nov 1998 07:17:02 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id QAA05710; Wed, 11 Nov 1998 16:15:13 +0100 (CET) To: Armin Gruner cc: freebsd-isdn@FreeBSD.ORG Subject: Re: SOLVED: Re: Win95 and connection to isdn4bsd on FreeBSD In-reply-to: Your message of "Wed, 11 Nov 1998 15:31:50 +0100." <19981111153150.A29738@devsoft.com> Date: Wed, 11 Nov 1998 16:15:12 +0100 Message-ID: <5708.910797312@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To be painfully correct, we may actually have to run with an asyncmap even in sync-ppp mode. The other end my be connected using an "Intelligent Network Terminal Adapter" using an async line. This is the kind of bogosity the ISDN standards allow for. I don't know of any hardware that would require it. Suggest you just REJ it. Poul-Henning >Anyway, if I remove the "p[2] = p[3] = p[4] = p[5] = 0;", >the driver sends back the original async map request with a >NAK, and the errors in the Win95 ppp log go away. >After 10 times, the i4b driver sends a REJ to the ASYNCMAP >request, so it looks that basically any ASYNCMAP request should be >rejected in ppp_lcp_RCR(), not NAK'ed. >I will modify the sources and try it out. > >Now I successfully connect with a Teles card and a USR STI card. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message