Clifford Kite <[EMAIL PROTECTED]> wrote:
> On Thu, 1 Apr 1999, Paul Mackerras wrote:
>
> |
> |* The default asyncmap is now 0.
> |
>
> I'm curious as to why you choose to violate RFC 1662 which defines the
> default ACCM as ffffffff. Ppp-2.2.0 uses a default ACCM of 0 but
> ppp-2.3.5 complies with the RFC. Is there a newer RFC?
No, you misunderstand me. I just meant that if you don't give any
asyncmap option to pppd, it will assume you want an asyncmap of 0 and
try to negotiate that with the peer. If the asyncmap is not
negotiated, it is still taken to be 0xffffffff as before.
The receive-all option is the one which maybe violates the RFC. It
causes pppd to use a receive-side asyncmap of 0 if the peer doesn't
negotiate one. This is for talking to buggy peers like NT machines
doing callback which don't escape control characters during initial
LCP negotiation, or which don't negotiate an asyncmap and then send
unescaped control characters.
(The RFC says something to the effect that "if a control character is
received which is flagged in the receive asyncmap, it is silently
discarded". It doesn't say it MUST be discarded.)
Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
