nRF9160-DK , Modem_shell demo , ppp unable to access the Internet

[JackyChen]

Hello,guys

I build nrf9160-dk modem_shell demo as cmd '$ west build -b nrf9160dk_nrf9160ns ' and then '$ west flash ', after the system running up, I try to ping baidu website，it works as follow picture.

And then I rebuild the Modem_shell demo with cmd ' $ west build -p -b nrf9160dk_nrf9160_ns -d build -- -DOVERLAY_CONFIG=overlay-ppp.conf' for supporting ppp function. After the system running up, I try to ping baidu website again，it works as follow picture and it work failed.

I can capture any data from another serial, I guess VCOM0 serial is shell and VCOM2 serial is ppp channel.

To test my guess，I plugged nrf9160-DK board into my Ubuntu virtual machine and disable Ubuntu network. Use minicom tool to connect VCOM0 and open nrf9160-DK shell in A terminal, set the custom configuration for PPP uart with cmd 'ppp uartconf -b 115200' . New B terminal for ppp connection , type cmd ' $sudo pppd -detach /dev/ttyACM2 115200 DK-ip:Ubuntu-ip noauth nocrtscts local ' , then A terminal return "Dial up connection up" . New C terminal and type cmd ' ifconfig ' , I can see ppp0 and it's ip ,I try to ping baidu website,it work as follow picture.

it can't access the Internet ? why ? Did I operate wrong? Please point out my mistakes.

The version of modem_fw I use is 1.3.0 , ncs version is 1.7.0.

[Håkon Alseth]

Hi,

 

You are unfortunately running into a known issue with NCS v1.7.0:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/known_issues.html?v=v1-7-0#other-issues

 

Issue is described here:

https://github.com/zephyrproject-rtos/zephyr/issues/38516

 

While a fixed is posted in this PR:

https://github.com/zephyrproject-rtos/zephyr/pull/38517

 

Could you try applying the above PR and see if it works better on your end?

 

Kind regards,

Håkon

[JackyChen]

Hello Håkon, thanks for your technical support.

yep, I merge this commit

https://github.com/zephyrproject-rtos/zephyr/pull/38517/commits/4ecaebf2b04fd48a1def8f8adf7bd3cc1528c482

and do the experiment again. Unfortunately, my VM-Ubuntu unable to access the network, it still doesn't work.

Best wish.

Jackychen

[Håkon Alseth]

Hi,

 

JackyChen said:

Could you push your model_shell firmware and modem-firmware here, I can dowanload them for test on my side.

This will not help, as the issues you're seeing is network related, not firmware related.

 

JackyChen said:

I use China-Mobile SIM card which is dedicated for IOT,  their technical support said that IP and DNS are obtained at the same time.

I plug the SIM card into my phone , my phone can surf the Internet with this SIM card.

So, I'm not sure if there's a compatibility problem with the way to gets DNS?

Could you please try to run "at_client" sample on your nRF9160?

This should be used in combination with LTE Link Monitor (available inside nRF Connect for Desktop), which enables network related error codes.

 

What you should issue of commands in there to enable NB1 and start the network connection:

AT+CEREG=5
AT%XSYSTEMMODE=0,1,0,0
AT+CFUN=1
AT+CFUN?

 

Could you then let it log for some minutes and share the log with me?

 

Kind regards,

Håkon

[JackyChen]

Hi,

When I running  at_client demo, the LTE Link Monitor shows

and the log :

AT

OK

AT+CEREG=5

OK

AT%XSYSTEMMODE=0,1,0,0

OK

AT+CFUN=1

OK

AT+CFUN?

+CFUN: 1

OK

AT+CGSN=1

+CGSN: "3526xxxxxxx8363"

OK

AT+CGMI

Nordic Semiconductor ASA

OK

AT+CGMM

nRF9160-SICA

OK

AT+CGMR

mfw_nrf9160_1.2.3

OK

AT+CEMODE?

+CEMODE: 0

OK

AT%XCBAND=?

%XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)

OK

AT+CMEE?

+CMEE: 0

OK

AT+CMEE=1

OK

AT+CNEC?

+CNEC: 0

OK

AT+CNEC=24

OK

AT+CGEREP?

+CGEREP: 0,0

OK

AT+CGDCONT?

OK

AT+CGACT?

OK

AT+CGEREP=1

OK

AT+CIND=1,1,1

OK

AT+CEREG=5

OK

AT+CEREG?

+CEREG: 5,4,"FFFE","FFFFFFFF",9,0,0,"00000000","00000000"

OK

AT%CESQ=1

OK

AT+CESQ

+CESQ: 99,99,255,255,255,255

OK

AT%XSIM=1

OK

AT%XSIM?

%XSIM: 1

OK

AT+CPIN?

+CPIN: READY

OK

AT+CPINR="SIM PIN"

+CPINR: "SIM PIN",3

OK

AT+CIMI

460xxxxxxxx7655

OK

%CESQ: 55,2,20,2

+CEREG: 2,"1D26","02D06D3D",9,0,0,"11100000","11100000"

%CESQ: 56,2,27,3

+CGEV: ME PDN ACT 0,0

+CNEC_ESM: 50,0

AT+CGDCONT?

+CEREG: 1,"1D26","02D06D3D",9,,,"11100000","11100000"

+CIND: "service",1

+CGDCONT: 0,"IP","cmiot","10.67.30.208",0,0

OK

AT+CGACT?

+CGACT: 0,1

OK

AT+CFUN?

+CFUN: 1

OK

AT+CGSN=1

+CGSN: "352xxxxxxxx8363"

OK

AT+CGMI

Nordic Semiconductor ASA

OK

AT+CGMM

nRF9160-SICA

OK

AT+CGMR

mfw_nrf9160_1.2.3

OK

AT+CEMODE?

+CEMODE: 0

OK

AT%XCBAND=?

%XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)

OK

AT+CMEE?

+CMEE: 1

OK

AT+CNEC?

+CNEC: 24

OK

AT+CGEREP?

+CGEREP: 1,0

OK

AT+CIND=1,1,1

OK

AT+CEREG=5

OK

AT+CEREG?

+CEREG: 5,1,"1D26","02D06D3D",9,,,"11100000","11100000"

OK

AT+COPS=3,2

OK

AT+COPS?

+COPS: 0,2,"46000",9

OK

AT%XCBAND

%XCBAND: 8

OK

AT+CGDCONT?

+CGDCONT: 0,"IP","cmiot","10.67.30.208",0,0

OK

AT+CGACT?

+CGACT: 0,1

OK

AT%CESQ=1

OK

AT+CESQ

+CESQ: 99,99,255,255,28,54

OK

AT%XSIM=1

OK

AT%XSIM?

%XSIM: 1

OK

AT+CPIN?

+CPIN: READY

OK

AT+CPINR="SIM PIN"

+CPINR: "SIM PIN",3

OK

AT+CIMI

460xxxxxxxx7655

OK

%CESQ: 55,2,17,2

%CESQ: 54,2,27,3

%CESQ: 54,2,17,2


It shows that the network is working.

[Håkon Alseth]

Hi,

 

JackyChen said:

mfw_nrf9160_1.2.3

Not that it should matter, especially for DNS/IP connectivity, but can you try with a newer modem fw to see if this improves the scenario?

 

Kind regards,

Håkon

[JackyChen]

Hi, Håkon

Yep, I have tried modem fw with v1.3.0,  v1.3.1,  they get the same result on at_client demo and modem_shell demo.  I've tested all the firmware versions that can be replaced ,but nothing effective.

It makes me feel helpless.

Thanks~

JackyChen

[Håkon Alseth]

Hi,

 

JackyChen said:

Yep, I have tried modem fw with v1.3.0,  v1.3.1,  they get the same result on at_client demo and modem_shell demo.  I've tested all the firmware versions that can be replaced ,but nothing effective.

Could you take a modem trace when running for instance "mqtt_simple" sample?

Here's a guide on how to do that: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_trac_collector%2FUG%2Ftrace_collector%2Fintro.html

 

You could also try to resolve the mqtt-broker manually in the mqtt_simple project, and input this as the IP directly:

CONFIG_MQTT_BROKER_HOSTNAME="137.135.83.217"

 

That is the IP to "mqtt.eclipseprojects.io", which is the default mqtt broker that the sample connects to.

 

Kidn regards,

Håkon

[JackyChen]

Hi,Håkon

Sorry I was late in replying. Here are my mqtt_simple with using modem_fw_v1.3.1,take a look  at your spare time and see what's wrong with it.

Thanks~

JackyChen

trace-2021-11-01T09-53-06.830Z.bin

[Håkon Alseth]

Hi,

 

JackyChen said:

trace-2021-11-01T09-53-06.830Z.bin

Thank you for the trace, but unfortunately it shows that you're still trying to attach to a network on LTE-M.

Could you try setting "CONFIG_LTE_NETWORK_MODE_NBIOT=y" in prj.conf and also try my former suggestion to see if it connects properly then?

 

Kind regards,

Håkon

 

[JackyChen]

Hi,

I have modified "CONFIG_MQTT_BROKER_HOSTNAME="137.135.83.217"   CONFIG_LTE_NETWORK_MODE_NBIOT=y " in prj.conf, here is the  modem trace.Please check~

trace-2021-11-02T01-33-11.764Z.bin

Thanks~

JackyChen

[Håkon Alseth]

Hi,

 

JackyChen said:

I have modified "CONFIG_MQTT_BROKER_HOSTNAME="137.135.83.217"   CONFIG_LTE_NETWORK_MODE_NBIOT=y " in prj.conf, here is the  modem trace.Please check~

trace-2021-11-02T01-33-11.764Z.bin

This trace shows a working mqtt connection.

You can try to enable legacy PCO and see if this helps wrt. DNS:

AT%XEPCO=0

 

Kind regards,

Håkon

[JackyChen]

enable legacy PCO ? Do you mean programme the firmware "nrf9160dk_asset_tracker_v2_nbiot_legacy_pco_2021-06-25_7a076c22.hex"

and then type AT cmd  "AT%XEPCO=0" ?

Thanks~

JackyChen