Stelios Pa

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • in reply to: IP 67 Conduit – corrupted /etc/init.d/ file #26881
    Stelios Pa
    Participant

    Try hold the reset button for >30 seconds and then try again. This will reset the device to factory defaults.

    in reply to: 417 – Expectation Failed – OpenVPN tunnel #26849
    Stelios Pa
    Participant

    Thanks for the answer, I will try it.

    in reply to: 417 – Expectation Failed – OpenVPN tunnel #26761
    Stelios Pa
    Participant

    Any thoughts?

    in reply to: "PPP Link is down" and stays down forever #26610
    Stelios Pa
    Participant

    Thanks Jeff!

    in reply to: "PPP Link is down" and stays down forever #26606
    Stelios Pa
    Participant

    Update:

    Even after I take out the SIM card, obviously the connection is lost, the pppd and chat seems to ignore it and reconnects ?

    
    2018-10-22T15:37:50.499389+03:00 mtcdt pppcheck: KeepAlive: 4 consecutive ping failures.  Hanging up and redialing ...
    2018-10-22T15:37:50.572863+03:00 mtcdt pppd[1852]: Hangup (SIGHUP)
    2018-10-22T15:37:50.580653+03:00 mtcdt pppd[1852]: Connect time 5.7 minutes.
    2018-10-22T15:37:50.581741+03:00 mtcdt pppd[1852]: Sent 480 bytes, received 240 bytes.
    2018-10-22T15:37:53.289125+03:00 mtcdt pppd[1852]: Connection terminated.
    2018-10-22T15:37:53.352800+03:00 mtcdt pppd[1852]: Hangup (SIGHUP)
    2018-10-22T15:37:54.674415+03:00 mtcdt chat[4784]: info: Attempting Basic Radio Communication
    2018-10-22T15:37:54.675655+03:00 mtcdt chat[4784]: send (AT^M)
    2018-10-22T15:37:54.710316+03:00 mtcdt chat[4784]: expect (OK)
    2018-10-22T15:37:54.714105+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:54.714438+03:00 mtcdt chat[4784]: OK
    2018-10-22T15:37:54.714659+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:54.714910+03:00 mtcdt chat[4784]: info: Checking if SIM is inserted
    2018-10-22T15:37:54.715139+03:00 mtcdt chat[4784]: send (AT#SIMDET?^M)
    2018-10-22T15:37:54.828411+03:00 mtcdt chat[4784]: expect (#SIMDET: 2,1)
    2018-10-22T15:37:54.828740+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:54.832907+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:54.845968+03:00 mtcdt chat[4784]: #SIMDET: 2,1
    2018-10-22T15:37:54.850328+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:54.856521+03:00 mtcdt chat[4784]: info: Checking if SIM is locked
    <strong>2018-10-22T15:37:54.857832+03:00 mtcdt chat[4784]: send (AT+CPIN?^M)
    2018-10-22T15:37:54.951258+03:00 mtcdt chat[4784]: expect (READY)
    2018-10-22T15:37:54.951594+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:54.951858+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:54.952131+03:00 mtcdt chat[4784]: OK^M
    2018-10-22T15:37:54.955405+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:54.955777+03:00 mtcdt chat[4784]: +CPIN: READY</strong>
    2018-10-22T15:37:54.955992+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:54.956233+03:00 mtcdt chat[4784]: info: SIM was unlocked
    2018-10-22T15:37:54.956455+03:00 mtcdt chat[4784]: info: Waiting for minimum signal strength
    2018-10-22T15:37:54.956678+03:00 mtcdt chat[4784]: send (AT+CSQ^M)
    2018-10-22T15:37:55.031694+03:00 mtcdt chat[4784]: expect (+CSQ: )
    2018-10-22T15:37:55.032016+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:55.032279+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:55.032557+03:00 mtcdt chat[4784]: OK^M
    2018-10-22T15:37:55.036386+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:55.036693+03:00 mtcdt chat[4784]: +CSQ:
    2018-10-22T15:37:55.036908+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:55.037146+03:00 mtcdt chat[4784]: expect (99,99)
    2018-10-22T15:37:55.037479+03:00 mtcdt chat[4784]: 20,99^M
    2018-10-22T15:37:55.037736+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:55.038005+03:00 mtcdt chat[4784]: OK^M
    2018-10-22T15:37:56.040735+03:00 mtcdt chat[4784]: alarm
    2018-10-22T15:37:56.041476+03:00 mtcdt chat[4784]: send (AT^M)
    2018-10-22T15:37:56.072660+03:00 mtcdt chat[4784]: expect (OK)
    2018-10-22T15:37:56.076639+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.076946+03:00 mtcdt chat[4784]: OK
    2018-10-22T15:37:56.077164+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:56.077425+03:00 mtcdt chat[4784]: send (AT^M)
    2018-10-22T15:37:56.108551+03:00 mtcdt chat[4784]: abort on (NO CARRIER)
    2018-10-22T15:37:56.108829+03:00 mtcdt chat[4784]: abort on (BUSY)
    2018-10-22T15:37:56.109077+03:00 mtcdt chat[4784]: abort on (ERROR)
    2018-10-22T15:37:56.109319+03:00 mtcdt chat[4784]: expect (OK)
    2018-10-22T15:37:56.109616+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.112705+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.113011+03:00 mtcdt chat[4784]: OK
    2018-10-22T15:37:56.123677+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:56.127214+03:00 mtcdt chat[4784]: send (AT+CSQ^M)
    2018-10-22T15:37:56.203873+03:00 mtcdt chat[4784]: expect (OK)
    2018-10-22T15:37:56.204212+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.208027+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.208428+03:00 mtcdt chat[4784]: +CSQ: 20,99^M
    2018-10-22T15:37:56.208698+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.208970+03:00 mtcdt chat[4784]: OK
    2018-10-22T15:37:56.209183+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:56.209450+03:00 mtcdt chat[4784]: send (AT+CGDCONT=1,\"IP\",\"XX.XX.XX.XX\"^M)
    2018-10-22T15:37:56.652476+03:00 mtcdt chat[4784]: expect (OK)
    2018-10-22T15:37:56.652807+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.670669+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.670963+03:00 mtcdt chat[4784]: OK
    2018-10-22T15:37:56.671177+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:56.671426+03:00 mtcdt chat[4784]: send (ATDT*99***1#^M)
    2018-10-22T15:37:56.806693+03:00 mtcdt chat[4784]: expect (CONNECT)
    2018-10-22T15:37:56.807016+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.813824+03:00 mtcdt chat[4784]: ^M
    2018-10-22T15:37:56.814159+03:00 mtcdt chat[4784]: CONNECT
    2018-10-22T15:37:56.814363+03:00 mtcdt chat[4784]:  -- got it
    2018-10-22T15:37:56.814605+03:00 mtcdt chat[4784]: send (^M)
    2018-10-22T15:37:56.827046+03:00 mtcdt pppd[1852]: Serial connection established.
    2018-10-22T15:37:56.832807+03:00 mtcdt pppd[1852]: Using interface ppp0
    2018-10-22T15:37:56.864767+03:00 mtcdt pppd[1852]: Connect: ppp0 <--> /dev/modem_at0
    2018-10-22T15:37:57.914887+03:00 mtcdt pppd[1852]: CHAP authentication succeeded
    2018-10-22T15:37:57.915203+03:00 mtcdt pppd[1852]: CHAP authentication succeeded
    2018-10-22T15:37:57.945277+03:00 mtcdt pppd[1852]: Could not determine remote IP address: defaulting to 10.64.64.64
    2018-10-22T15:37:57.972709+03:00 mtcdt pppd[1852]: local  IP address 100.XX.XX.XX
    2018-10-22T15:37:57.973684+03:00 mtcdt pppd[1852]: remote IP address 10.64.64.64
    2018-10-22T15:37:57.974341+03:00 mtcdt pppd[1852]: primary   DNS address 213.XX.XX.XX
    2018-10-22T15:37:57.975004+03:00 mtcdt pppd[1852]: secondary DNS address 213.XX.XX.XX
    2018-10-22T15:37:59.816623+03:00 mtcdt ppp-rx-monitor: Started Monitoring
    
    in reply to: Change root password & disable administration panel #26525
    Stelios Pa
    Participant

    Thank you both, Jeff your answer solved the problem.

    NEW_PASS='MY_NEW_AWESOME_PASS'
    PASS_TOKEN=$(curl -k -X POST -H "Content-Type: application/json" -d '{"username":"admin","password":"admin"}' https://127.0.0.1/api/login | grep token | awk -F '"' '{print $4}')
    curl -k -X PUT -H "Content-Type: application/json" -d '{"name": "admin", "password": "admin", "newPassword": "'"${NEW_PASS}"'"}' https://127.0.0.1/api/users&token=${PASS_TOKEN}
    • This reply was modified 6 years, 1 month ago by Stelios Pa.
    • This reply was modified 6 years, 1 month ago by Stelios Pa.
    • This reply was modified 6 years, 1 month ago by Stelios Pa.
    • This reply was modified 6 years, 1 month ago by Stelios Pa. Reason: It seems to work now
    in reply to: AEP vs mLinux: Does it really matters? #25919
    Stelios Pa
    Participant

    Thanks for your answers, you were very helpful

    in reply to: AEP vs mLinux: Does it really matters? #25902
    Stelios Pa
    Participant

    Hi Jeff, thanks for answering.

    Configuring services from command line is not an issue in my case and device HQ is great but 4 hours interval is too much for me, my solution provides me live management/monitoring.

    But can you explain a bit more about the Cellular ? I can understand monitoring but it provides tools for maintaining the connection too ? even if it goes down and mLinux is missing such features ?

    That would be a problem in my case because cellular is the only WAN interface in my case and it should not go down in any case.

    Also, if i order the mLinux models, is there any chance to upgrade them to AEP latter flashing the appropriate firmware ?

    thanks

    in reply to: Upgrade Python 2.7.3 to >=2.7.9 #23961
    Stelios Pa
    Participant

    Hello Jeff,

    thats great news, I’m happy to hear it because i’m stuck with Paho MQTT client, it requires SSLContext in order to make a secure connection. Python provides SSLContext from version >=2.7.9

    Let me correct myself, my mLinux version is 3.3.22!

    So till next month, are there any temporary, alternative, solutions?

    Generally speaking, are the below solutions possible?

    * build a python2.7.*.ipk using bitbake based on a Yocto (>=Fido) recipe, transfer the .ipk and install it through opkg? (or it’s not possible till mLinux 3.3.22 is based on Daisy?)

    * Creating a custom mLinux image following the instructions here with the desired upgrade and flash the device with it?

    * Is there a beta/nightly version of AEP 1.6 available?

    Is any of the above options possible?

    I’m asking because I don’t know where i should be oriented to in order to solve the problem, even temporary until the new firmware.

    thanks!

    • This reply was modified 6 years, 5 months ago by Stelios Pa. Reason: changed mlinux version
    • This reply was modified 6 years, 5 months ago by Stelios Pa. Reason: changed link
    in reply to: Upgrade Python 2.7.3 to >=2.7.9 #23918
    Stelios Pa
    Participant

    Is there any other recommended way to upgrade python version?

    thanks for you answer !

Viewing 10 posts - 1 through 10 (of 10 total)