We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am using RL-ARM TCPnet in an attempt to set up a PPP connection to Windows XP. Sometimes it all works well; i can connect to my device and i can normally exchange tcp packets. Other times, ppp links does not go up; in these cases, it seems like PC sends LCP packets also after PAP authentication has been achieved: library refuses those packets. Windows says "Logging on", and after a while gives up. I have observed that if i setup my modem at 38400 baud (baudrate between my modem and my cpu), ppp often works well, only sometimes fails; but if i setup my modem at 9600 baud (the same baudrate that modems handkshake between them), ppp does never work (the modem goes normally on-line).
Thanks in advance to everyone can give me any suggest.
Here is the log i have obtained with debug library:
PPP: Initialize PPP interface
PPP: Initialize PPP-LCP
PPP: Initialize PPP-PAP
PPP: Initialize PPP-IPCP
PPP: Enabling listen mode...
PPP: Username: tw, Password: teamware
PPP: *** Processing PPP frame ***
PPP: Frame len: 24 bytes
PPP: Protocol: C021
PPP: *** Processing PPP-LCP frame ***
PPP: LCP Config Request received.
PPP: Sending PPP frame...
PPP: Frame len: 16
PPP: Frame len: 26
PPP: Sending LCP Configuration request.
PPP: Frame len: 30
PPP: Frame len: 28 bytes
PPP: LCP Config Acknowledge received.
PPP: Async Char MAP: 00,0A,00,00
PPP: Enabled PF Compression
PPP: Enabled ACF Compression
PPP: Magic Number: 406FEC4F
PPP: Enabled PAP Authentication Protocol
PPP: Frame len: 20 bytes
PPP: Protocol: C023
PPP: *** Processing PPP-PAP frame ***
PPP: PAP Authentication Request received.
PPP: Remote Client login success.
PPP: Frame len: 20
PPP: LCP up, ignoring Config request.
What is your RL-ARM version number?
I believe this problem has been corrected in RL-ARM v4.10.
Thanks for your prompt reply. My RL-ARM release is 3.21.
I am planning to buy the upgrade; i kindly ask if you can confirm that my problem is solved, or you only hope that. I can't understand why PPP does never go up at 9600 baud. Thanks again
Probably a timing issue - with 9600 baud, everything takes longer time.
Yes, I can confirm this, as I'm the one who was fixing the problem.
I bought the upgrade (waiting for delivery). As soon as possibile I will post my (hopefully correct) results. Regards
I have upgraded my project with MDK-ARM rel. 4.11 and RL-ARM rel. 4.11. I have again configured my modem at 9600 baud, and I have obtained the same PPP hanging. It seems that library refuses LCP configuration request received after successfully PAP authentication. If I am doing some mistake, please help me to find. I post the log obtained with debug library.
PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP Config Request received PPP: Sending PPP frame PPP: Frame len: 16 PPP: Protocol : C021 PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP Config Request received PPP: Sending PPP frame PPP: Frame len: 26 PPP: Protocol : C021 PPP: Sending LCP Configuration request PPP: Async Char MAP: 00,0A,00,00 PPP: Option: PF Compression PPP: Option: ACF Compression PPP: Magic Number: 2EB9EE48 PPP: Option: PAP Authentication PPP: Sending PPP frame PPP: Frame len: 30 PPP: Protocol : C021 PPP: Sending LCP Configuration request PPP: Async Char MAP: 00,0A,00,00 PPP: Option: PF Compression PPP: Option: ACF Compression PPP: Magic Number: 2EB9EE48 PPP: Option: PAP Authentication PPP: Sending PPP frame PPP: Frame len: 30 PPP: Protocol : C021 PPP: *** Processing PPP frame *** PPP: Frame len: 28 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP Config Acknowledge received PPP: Async Char MAP: 00,0A,00,00 PPP: Enabled PF Compression PPP: Enabled ACF Compression PPP: Magic Number: 2EB9EE48 PPP: Enabled PAP Authentication Protocol PPP: *** Processing PPP frame *** PPP: Frame len: 20 bytes PPP: Protocol : C023 PPP: *** Processing PPP-PAP frame *** PPP: PAP Authentication Request received PPP: Client login success PPP: Sending PPP frame PPP: Frame len: 20 PPP: Protocol : C023 PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 28 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP Config Acknowledge received PPP: Async Char MAP: 00,0A,00,00 PPP: Enabled PF Compression PPP: Enabled ACF Compression PPP: Magic Number: 2EB9EE48 PPP: Enabled PAP Authentication Protocol PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: *** Processing PPP frame *** PPP: Frame len: 24 bytes PPP: Protocol : C021 PPP: *** Processing PPP-LCP frame *** PPP: LCP up, ignoring Config request PPP: Initialize PPP-LCP PPP: Initialize PPP-PAP PPP: Initialize PPP-IPCP
Thanks for your support
Can you check a ready made example from RL-ARM installation. There is a HTTP_demo example for MCB2140 and MCBSTR7, configured for PPP.
I have checked both examples; I don't find anything that can help me. Please note that with modem at 38400 baud, my PPP goes up (almost) always; it hangs always with modem at 9600 baud, and always in the same way: LCP up, ignoring Config request.
I have used two serials on my board to trace with PPPMonitor all frames exchanged between GSM modem and CPU. I can send the log files by mail if you think they can be useful. From them I see that, when authentication hangs, the cpu (i.e. RL-ARM library) - after successfully PAP authentication - receives a number of retries of LCP Configure Request; cpu ignores those messages and does not send the acknowledge (because for cpu, LCP is already up). I think that RL_ARM should acknolwledge those messages also if for itself the LCP is already up; maybe the caller could lose some messages due to line disturb, and for itself LCP is not up yet.
Please send your logs in email to support.intl@keil.com addressed to me.
Logs sent. Thanks.
Problem solved in the new TCP library. Thanks to Franc Urbanc for his careful and professional support.