ppp - no response to LCP ConfReq
Hello I have been having a terrible time fixing a PPP connection on my linux system. Everything was working fine till 2 days ago. Win95 can still connect so I looked at the ppplog.txt file there and comparing it to previous connects, it looks like the authentication procedure on the server has changed from PAP to CHAP. I have setup the chap-secrets file accordingly as well as set the name and remotename options. After the call comes up and chat hands over to pppd, I get these messages Aug 26 03:35:37 nsx pppd[9455]: Connect: ppp0 -- /dev/ttyS1 Aug 26 03:35:37 nsx pppd[9455]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x9001 pcomp accomp] Aug 26 03:36:07 nsx last message repeated 10 times Aug 26 03:36:07 nsx pppd[9455]: Hangup (SIGHUP) Aug 26 03:36:07 nsx pppd[9455]: Modem hangup Aug 26 03:36:07 nsx pppd[9455]: Connection terminated. Aug 26 03:36:08 nsx pppd[9455]: Exit. It looks like I send the LCP ConfReq for 30 secs then the modem hangs up. There appears to be no response from the server at all. I also noticed that the option lcp-max-configure has no effect on the number of requests I send, contrary to what is in the man page. What does work is the lcp-restart option. With this I can control the interval between the LCP requests but still after 30 secs LCP configure requests stop and the modem hangs up. Is there a setting for controlling the time for which LCP requests are sent. Right now I am lost. I have RTFM but if I have missed anything please point it out. I have kernel v2.0.34 on a hamm system with ppp 2.3.5. TIA jmb
Re: ppp - no response to LCP ConfReq
J == JonesMB [EMAIL PROTECTED] writes: J Everything was working fine till 2 days ago. Win95 can still J connect so I looked at the ppplog.txt file there and comparing it J to previous connects, it looks like the authentication procedure on J the server has changed from PAP to CHAP. I have setup the J chap-secrets file accordingly as well as set the name and J remotename options. After the call comes up and chat hands over to J pppd, I get these messages J Aug 26 03:35:37 nsx pppd[9455]: Connect: ppp0 -- /dev/ttyS1 J Aug 26 03:35:37 nsx pppd[9455]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x9001 pcomp accomp] J Aug 26 03:36:07 nsx last message repeated 10 times J Aug 26 03:36:07 nsx pppd[9455]: Hangup (SIGHUP) J Aug 26 03:36:07 nsx pppd[9455]: Modem hangup J Aug 26 03:36:07 nsx pppd[9455]: Connection terminated. J Aug 26 03:36:08 nsx pppd[9455]: Exit. What makes you think they have changed to CHAP? The logfile snipplet above doesn't indicate anything like this (as authentication is part of LCP). Ciao, Martin
Re: ppp - no response to LCP ConfReq
What makes you think they have changed to CHAP? The logfile snipplet above doesn't indicate anything like this (as authentication is part of LCP). Ciao, Martin *** apologies for the length of this message *** I think they changed to CHAP because of these 2 Win95 PPP log files start ppplog.txt from June 06-02-1998 19:38:58.82 - Remote access driver log opened. 06-02-1998 19:38:58.82 - Installable CP VxD SPAP is loaded 06-02-1998 19:38:58.82 - Server type is PPP (Point to Point Protocol). 06-02-1998 19:38:58.82 - FSA : Adding Control Protocol 80fd (CCP) to control protocol chain. 06-02-1998 19:38:58.82 - FSA : Protocol disabled by user - skipping control protocol 803f (NBFCP). 06-02-1998 19:38:58.82 - FSA : Protocol not bound - skipping control protocol 8021 (IPCP). 06-02-1998 19:38:58.82 - FSA : Protocol not bound - skipping control protocol 802b (IPXCP). 06-02-1998 19:38:58.82 - FSA : Adding Control Protocol c029 (CallbackCP) to control protocol chain. 06-02-1998 19:38:58.82 - FSA : Adding Control Protocol c027 (no description) to control protocol chain. 06-02-1998 19:38:58.82 - FSA : Adding Control Protocol c023 (PAP) to control protocol chain. 06-02-1998 19:38:58.82 - FSA : Adding Control Protocol c223 (CHAP) to control protocol chain. 06-02-1998 19:38:58.82 - FSA : Adding Control Protocol c021 (LCP) to control protocol chain. 06-02-1998 19:38:58.82 - LCP : Callback negotiation enabled. 06-02-1998 19:38:58.82 - LCP : Layer started. 06-02-1998 19:39:02.04 - LCP : Received and accepted MRU of 1500. 06-02-1998 19:39:02.04 - LCP : Received and accepted ACCM of 0. 06-02-1998 19:39:02.04 - LCP : Received and accepted magic number 4a79d0e9. 06-02-1998 19:39:02.04 - LCP : Received and accepted protocol field compression option. 06-02-1998 19:39:02.04 - LCP : Received and accepted address+control field compression option. 06-02-1998 19:39:02.04 - LCP : Received and accepted authentication protocol c023 (PAP). 06-02-1998 19:39:04.91 - LCP : Received configure reject for callback control protocol option. 06-02-1998 19:39:05.04 - LCP : Layer up. 06-02-1998 19:39:05.04 - PAP : Layer started. 06-02-1998 19:39:05.28 - PAP : Login was successful. 06-02-1998 19:39:05.28 - PAP : Layer up. 06-02-1998 19:39:05.28 - CCP : Layer started. 06-02-1998 19:39:05.33 - FSA : Sending protocol reject for control protocol 802b. 06-02-1998 19:39:05.49 - FSA : Sending protocol reject for control protocol 8021. 06-02-1998 19:39:10.08 - Remote access driver is shutting down. end ppplog.txt from June start ppplog.txt from yesterday 08-25-1998 02:51:08.19 - Microsoft Dial Up Agapter log opened. 08-25-1998 02:51:08.19 - Installable CP VxD SPAP is loaded 08-25-1998 02:51:08.19 - Installable CP VxD SPAP is loaded 08-25-1998 02:51:08.19 - Server type is PPP (Point to Point Protocol). 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol 80fd (CCP) to control protocol chain. 08-25-1998 02:51:08.19 - FSA : Protocol disabled by user - skipping control protocol 803f (NBFCP). 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol 8021 (IPCP) to control protocol chain. 08-25-1998 02:51:08.19 - FSA : Protocol not bound - skipping control protocol 802b (IPXCP). 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol c029 (CallbackCP) to control protocol chain. 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol c027 (no description) to control protocol chain. 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol c023 (PAP) to control protocol chain. 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol c223 (CHAP) to control protocol chain. 08-25-1998 02:51:08.19 - FSA : Adding Control Protocol c021 (LCP) to control protocol chain. 08-25-1998 02:51:08.19 - LCP : Callback negotiation enabled. 08-25-1998 02:51:08.19 - LCP : Layer started. 08-25-1998 02:51:11.34 - LCP : Received and accepted MRU of 1514. 08-25-1998 02:51:11.34 - LCP : Received and accepted ACCM of 0. 08-25-1998 02:51:11.34 - LCP : Received and accepted authentication protocol c223 (CHAP). 08-25-1998 02:51:11.34 - LCP : Received and accepted magic number 7745af2c. 08-25-1998 02:51:11.34 - LCP : Received and accepted protocol field compression option. 08-25-1998 02:51:11.34 - LCP : Received and accepted address+control field compression option. 08-25-1998 02:51:11.45 - LCP : Received and accepted MRU of 1514. 08-25-1998 02:51:11.45 - LCP : Received and accepted ACCM of 0. 08-25-1998 02:51:11.45 - LCP : Received and accepted authentication protocol c223 (CHAP). 08-25-1998 02:51:11.45 - LCP : Received and accepted magic number 7745af2c. 08-25-1998 02:51:11.45 - LCP : Received and accepted protocol field compression option. 08-25-1998 02:51:11.45 - LCP : Received and accepted address+control field compression option. 08-25-1998 02:51:14.30 - LCP : Received configure reject for callback control protocol option. 08-25-1998 02:51:14.40 - LCP : Layer up. 08-25-1998 02:51:14.40 - CHAP : Layer started. 08-25-1998 02:51:14.63 -
Re: ppp - no response to LCP ConfReq
J == JonesMB [EMAIL PROTECTED] writes: J 08-25-1998 02:51:11.34 - LCP : Received and accepted authentication J protocol c223 (CHAP). No problem. CHAP is always tried first, if it is available. I think PAP will work nevertheless. But the other box doesn't respond to any LCP request you send. As I said before: authentication is done during LCP negotiation. Does the router send *anything* back (monitor the RX LED on your modem)? I would contact your ISP. Send them the logfile, and ask them about the changes they made. Maybe they switched the dial-in routers or OS version of these. Send them your config and most importent the complete logfile. Emphesize the line LCP and no response for request line. Get through to one of the network guys. Let him monitor a dial-in attempt. Maybe they have one special number with a old router, so you can reassure it is the change on their routers which cause the problems. Because it works with M$, doesn't mean it is not broken. Ciao, Martin -- from a 1996 Microshit ad campaign: The less you know about computers the more you want Micro$oft! See! They do get some things right!
