summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoerg Wunsch <joerg@FreeBSD.org>2001-12-26 22:00:13 +0000
committerJoerg Wunsch <joerg@FreeBSD.org>2001-12-26 22:00:13 +0000
commit248f19ee7b2daa9500fae68dbd47806a5b64c5c5 (patch)
treec928b9ead52e8c85c6cff939d28f4b9a66aa2f0e
parent676e98714db80b93e2c228352e2831feb07b6727 (diff)
Notes
-rw-r--r--sys/net/if_spppsubr.c26
1 files changed, 15 insertions, 11 deletions
diff --git a/sys/net/if_spppsubr.c b/sys/net/if_spppsubr.c
index 0fcb0e5a735e..440b32dafc83 100644
--- a/sys/net/if_spppsubr.c
+++ b/sys/net/if_spppsubr.c
@@ -2214,17 +2214,21 @@ sppp_lcp_RCR(struct sppp *sp, struct lcp_header *h, int len)
break;
case LCP_OPT_ASYNC_MAP:
- /* Async control character map -- check to be zero. */
- if (! p[2] && ! p[3] && ! p[4] && ! p[5]) {
- if (debug)
- log(-1, "[empty] ");
- continue;
- }
- if (debug)
- log(-1, "[non-empty] ");
- /* suggest a zero one */
- p[2] = p[3] = p[4] = p[5] = 0;
- break;
+ /*
+ * Async control character map -- just ignore it.
+ *
+ * Quote from RFC 1662, chapter 6:
+ * 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.
+ */
+ continue;
case LCP_OPT_MRU:
/*