From owner-freebsd-isdn Wed Apr 14 9: 4:11 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id D46561548A for ; Wed, 14 Apr 1999 09:03:57 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id SAA28531; Wed, 14 Apr 1999 18:01:33 +0200 (CEST) Date: Wed, 14 Apr 1999 18:01:25 +0200 From: Stefan Bethke To: freebsd-isdn@FreeBSD.ORG Cc: hm@hcs.de Subject: Re: win 98 / fritz && isdn4bsd workaround? Message-ID: <100810.3133101685@d225.promo.de> In-Reply-To: <496818.3133090589@d225.promo.de> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stefan Bethke wrote: > This whole checking could be eliminated completely. Because we are > talking synchronous PPP here, the async map is completely irrelevant. > However, the PPP RFC mandates that all PPP implementations must accept > any async map, even if the link layer used for the connection has no > notion of > "characters." > > The reason we see a non-null async map in this case is that the remote = is > probably using an async-to-sync converter (as in an ISDN TA), and the = PPP > implementation believes is has to escape some characters (i. e. "+".) Quoting from RFC 1662, PPP in HDLC-like Framing: > 6. Asynchronous to Synchronous Conversion > > There may be some use of asynchronous-to-synchronous > converters (some built into modems and cellular interfaces), > resulting in an asynchronous PPP implementation on one end > of a link and a synchronous implementation on the other. It > is the responsibility of the converter to do all stuffing > conversions during operation. > > To enable this functionality, synchronous PPP implementations = MUST > always respond to the Async-Control-Character-Map Configuration > Option with the LCP Configure-Ack. However, acceptance of the > Configuration Option does not imply that the synchronous > implementation will do any ACCM mapping. Instead, all such octet > mapping will be performed by the asynchronous-to-synchronous > converter. -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message