mLinux cellular configuration, Connect script failed
Home › Forums › Conduit: mLinux Model › mLinux cellular configuration, Connect script failed
Tagged: cellular, conduit gateway, mlinux, ppp0 interface
- This topic has 3 replies, 2 voices, and was last updated 7 years, 3 months ago by Lonny Knudson.
-
AuthorPosts
-
August 18, 2017 at 4:11 am #20730lorawan2016Participant
Hello,
Though I have followed the cellular settings, are there any configuration I am missing?
I have new Conduit gateway mLinux version 3.3.6 model MTCDT-H5-210L with Cellular settings for APN but from the logs I can see the ppp0 interface is not created. It doesn’t matter if ppp started manually or on boot, the results are the same. The SIM card is tested on another AEP gateway with cellular configuration and it works just fine but using the same SIM card on another gateway with mLinux version it doesn’t work.
I noticed the /etc/sbin/pppd requires a provider file under peers folder so I created provider file but it’s empty, I don’t know which information is needed to be included in this file. No information on MultiTech site about the provider file though. See the link http://www.multitech.net/developer/software/mlinux/using-mlinux/mlinux-cellular-connection/The logs from messages file show terminated connection because of failed connect script.
root@mtcdt:~# tail -f /var/log/messages
Aug 18 09:55:12 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:12 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:12 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:13 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:13 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:14 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:14 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:14 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:14 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:14 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:15 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:15 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:15 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:15 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:15 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:16 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:16 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:16 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:17 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:17 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:18 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:18 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:18 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:18 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:18 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:19 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:19 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:19 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:19 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:19 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:20 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:20 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:20 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:21 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:21 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:22 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:22 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:22 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:22 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:22 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:23 mtcdt daemon.info pppd[1672]: Using interface ppp0
Aug 18 09:55:23 mtcdt daemon.notice pppd[1672]: Connect: ppp0 <–> /dev/modem_at0
Aug 18 09:55:23 mtcdt daemon.warn pppd[1672]: Warning – secret file /etc/ppp/pap-secrets has world and/or group access
Aug 18 09:55:23 mtcdt daemon.notice pppd[1672]: Serial line is looped back.
Aug 18 09:55:23 mtcdt daemon.notice pppd[1672]: Connection terminated.
Aug 18 09:55:24 mtcdt daemon.info pppd[1672]: Exit.*************************************************************
The logs from gsm_chat shows no carrier message.
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (NO DIAL TONE)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (NO DIALTONE)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (NO ANSWER)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (NO CARRIER)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (DELAYED)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (VOICE)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: abort on (BUSY)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: send (AT^M)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: expect (OK)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: AT^M^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: OK
Aug 18 09:43:11 mtcdt local2.info chat[1527]: — got it
Aug 18 09:43:11 mtcdt local2.info chat[1527]: send (ATZ^M)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: expect (OK)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: ^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: ATZ^M^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: OK
Aug 18 09:43:11 mtcdt local2.info chat[1527]: — got it
Aug 18 09:43:11 mtcdt local2.info chat[1527]: send (AT+CSQ^M)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: expect (OK)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: ^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: AT+CSQ^M^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: +CSQ: 13,0^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: ^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: OK
Aug 18 09:43:11 mtcdt local2.info chat[1527]: — got it
Aug 18 09:43:11 mtcdt local2.info chat[1527]: send (ATD#777^M)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: timeout set to 120 seconds
Aug 18 09:43:11 mtcdt local2.info chat[1527]: expect (CONNECT)
Aug 18 09:43:11 mtcdt local2.info chat[1527]: ^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: ATD#777^M^M
Aug 18 09:43:11 mtcdt local2.info chat[1527]: NO CARRIER
Aug 18 09:43:11 mtcdt local2.info chat[1527]: — failed
Aug 18 09:43:11 mtcdt local2.info chat[1527]: Failed (NO CARRIER)
Aug 18 09:43:11 mtcdt daemon.err pppd[1397]: Connect script failed***************************************************************
The gsm_chat file content
SAY “GSM chat\n”
ECHO OFF
ABORT ‘NO DIAL TONE’
ABORT ‘NO DIALTONE’
ABORT ‘NO ANSWER’
ABORT ‘NO CARRIER’
ABORT ‘DELAYED’
ABORT ‘VOICE’
ABORT ‘BUSY’
” ‘AT’
OK ‘ATZ’
OK ‘AT+CSQ’
# ———————————-
# Set the APN for your provider here
# ———————————-
mlinux-set-apn ‘three.co.uk’
#OK ‘AT+CGDCONT=1,”IP”,”proxy”‘
#OK ‘AT+CGDCONT=1,”IP”,”ISP.CINGULAR”‘
#OK ‘AT+CGDCONT=1,”IP”,”internet2.voicestream.com”‘
OK ‘AT+CGDCONT=1,”IP”,”three.co.uk”‘
SAY “Dialing…\n”
#OK ‘ATD*99#’
OK ‘ATD*99***1#’
SAY “Waiting for CONNECT…\n”
TIMEOUT 120
CONNECT ”
SAY “Connected\n”August 18, 2017 at 8:48 am #20732Lonny KnudsonBlockedHello,
The events in the chat log show a different chat script executing than the one you posted (the one you posted is the correct chat script to use for a -H5 modem). Check your peer file and make sure the ‘connect’ option points to the same chat file that you posted here.August 18, 2017 at 4:16 pm #20733lorawan2016ParticipantHello Lonny,
Yes you have right the msg_chat logs was for another test related to cdma.
The pointed chat in the script is the gsm but there’s no chat logs similar to the cdma since the shown logs are ended by connection terminated for ppp.I have noticed as well that the /etc/sbin/pppd requires a provider file in the located in the peers folder so I have created a provider file but it’s empty though the documentation doesn’t mention it’s required which’s indicating something either wrong or missing in the gateway.
Do you know what kind of information should be written in the provider file?August 21, 2017 at 9:42 am #20738Lonny KnudsonBlockedHello,
The factory image should contain a (working) example peer file (/etc/ppp/peers/gsm). If you already edited your chat script to set the correct APN you should be able to start a ppp link by issuing the following command:
pppd call gsm -
AuthorPosts
- You must be logged in to reply to this topic.