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