From owner-freebsd-net  Mon Mar 15 16:41:30 1999
Delivered-To: freebsd-net@freebsd.org
Received: from tango.anu.edu.au (tango.anu.edu.au [150.203.164.89])
	by hub.freebsd.org (Postfix) with ESMTP id A447C14C3F
	for <freebsd-net@freebsd.org>; Mon, 15 Mar 1999 16:41:23 -0800 (PST)
	(envelope-from paulus@tango.anu.edu.au)
Received: (from paulus@localhost)
	by tango.anu.edu.au (8.8.8/8.8.8) id LAA16633;
	Tue, 16 Mar 1999 11:39:58 +1100
Date: Tue, 16 Mar 1999 11:39:58 +1100
Message-Id: <199903160039.LAA16633@tango.anu.edu.au>
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: lars@odin-corporation.com
Cc: freebsd-net@freebsd.org
In-reply-to: <36ED8FBE.D2BD78DC@odin-corporation.com> (message from Lars
	Fredriksen on Mon, 15 Mar 1999 16:54:54 -0600)
Subject: Re: pppd in current
Reply-To: Paul.Mackerras@cs.anu.edu.au
References:  <36ED8FBE.D2BD78DC@odin-corporation.com>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Lars Fredriksen <lars@odin-corporation.com> wrote:

>     3/22/98 version 1.8 of lcp.c changed the async map for the receiving
> side from defaulting to 0 to all Fs.

That's correct according to the RFC.

> This seems to cause problems with a few ppp servers as far as I can
> tell. The symptom is that one get
> connected ok, but no packets seems to flow. If you turn on debugging for
> the ppp driver you will find the
> following message:
> 
> ppp0: missing UI (0x3), got 0x21

That debug message doesn't seem to relate to the asyncmap.  I would
have to see a log of the negotiation to know more exactly what's going
on.

There are some buggy PPP implementations out there that assume that if
the asyncmap isn't negotiated they can assume it is 0.  I guess that's
what you're probably encountering.

Paul.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message