From 9fddf73ad02abd42983850115f2ac3375ed5be6f Mon Sep 17 00:00:00 2001 From: Brian Somers Date: Sat, 31 Oct 1998 17:38:48 +0000 Subject: [PATCH] If the CBCP callee offsers no callback, send our configured response anyway. This is what Win95 does, despite it not being documented in the cbcp spec.... Reported by: Bill --- usr.sbin/ppp/cbcp.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/usr.sbin/ppp/cbcp.c b/usr.sbin/ppp/cbcp.c index 9d01ef5cc392..415e6e238b2e 100644 --- a/usr.sbin/ppp/cbcp.c +++ b/usr.sbin/ppp/cbcp.c @@ -23,7 +23,7 @@ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * - * $Id: cbcp.c,v 1.5 1998/10/17 12:28:11 brian Exp $ + * $Id: cbcp.c,v 1.6 1998/10/25 23:35:15 brian Exp $ */ #include @@ -354,10 +354,12 @@ cbcp_AdjustResponse(struct cbcp *cbcp, struct cbcp_data *data) switch (data->type) { case CBCP_NONUM: - if (cbcp->fsm.type == CBCP_NONUM) - return 1; - log_Printf(LogPHASE, "CBCP: server wants no callback !\n"); - return 0; + /* + * If the callee offers no callback, we send our desired response + * anyway. This is what Win95 does - although I can't find this + * behaviour documented in the spec.... + */ + return 1; case CBCP_CLIENTNUM: if (cbcp->fsm.type == CBCP_CLIENTNUM) {