Date: Wed, 11 Nov 1998 16:15:12 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Armin Gruner <ag@devsoft.com> Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: SOLVED: Re: Win95 and connection to isdn4bsd on FreeBSD Message-ID: <5708.910797312@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 11 Nov 1998 15:31:50 %2B0100." <19981111153150.A29738@devsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5708.910797312>