On Sat, 3 Apr 1999, Paul Mackerras wrote:
|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.
Yes. I missed that important distinction - the default value for ACCM
negotiation rather than the default ACCM. Thanks.
---
Clifford Kite
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
