Red Hat Bugzilla – Bug 61628
pppd dialin problem to MS RAS server with CBCP
Last modified: 2005-10-31 17:00:50 EST
Description of Problem: pppd cannot connect as dialin only to MS RAS servers offering dialin and CBCP callback at the same time. Server requests disconnect. Version-Release number of selected component (if applicable): ppp-2.4.1-2 How Reproducible: Always, just dialin into server offering at the same time dialin and CBCP (and DO NOT use option 'callback', just try dialin) Actual Results: Received TermReq in LCP phase from the server Expected Results: Succesfull dialin ;-) Additional Information: The problem comes from the fact that: 1. CBCP protocol is disabled by default (unless 'callback' option specified) (in pppd/cbcp.c protent_cbcp) AND 2. CBCP negotiation is enabled by default (in pppd/lcp.c) which seems useless if no 'callback' option used (which enables both protocol and negotiation) See attached proposed patch and log excerpt from failed negotiation (basically local pppd acknowledged CBCP, then rejected CBCP packet. in response server requested termination ... )
Created attachment 49626 [details] log file from failed attempt
Created attachment 49627 [details] patch to disable CBCP negotiation by default
One thing more: Above problem most likely affects also ipppd from isdn4k-utils-3.1-46 (looking at the source code, exactly same thing happens there).
Hello Pity that before releasing ppp-2.4.1-3 update [RHBA-2002:037-04] you have not checked THIS bug report, instead of doing things like: * Wed Feb 27 2002 Nalin Dahyabhai <nalin@redhat.com> 2.4.1-3 - revert cbcp patch, it's wrong (#55367) you could fix it properly, using the patch I've attached .... (on 22 March !) Anyway I hope this WILL be fixed properly in the next update. (CBCP is really something some people HAVE to use ... because their access provider supports only this ...) To get the message through this time I've raised the priority and severity fields in the report ... Regards Jarek
Please verify this with a newer version of Red Hat Enterprise Linux or Fedora Core and reopen it against the new version if it still occurs. Closing as "not a bug" for now.