serial_lte_modem DNS resolution issues

RE: serial_lte_modem DNS resolution issues

Charlie — Mon, 31 Jan 2022 10:12:15 GMT

Ok, let's move our discussion to another ticket. Before this, I can answer some of your confusion.

1）The LTE-4G/5G used by mobile phone is different from LTE-M/NB-IoT(they are also different), one area may be covered by the mobile network, but not LTE-M/NB-IoT, so the signal strength cannot be used as a reference for each other.

2) MFW= Modem Firmware, the least is mfw_nrf9160_1.3.1 and can be downloaded from nRF9160 SiP modem firmware.

[quote user="Mr.Newlove"]is there any way to tell the modem it can use more power to get a stable connection?[/quote]

No, generally speaking, the cell station decides the power.

Best regards,

Charlie

RE: serial_lte_modem DNS resolution issues

Mr.Newlove — Sun, 30 Jan 2022 07:12:18 GMT

Maybe we should just continue the conversation on the other thread since this is just pointless now, my connection to the network is very good now and its just AT command problems now.

RE: serial_lte_modem DNS resolution issues

Mr.Newlove — Sat, 29 Jan 2022 09:13:19 GMT

1. I have been comparing my board and the nRF9160 DK and I am thinking maybe my problems are related to signal strength?

Both the DK and my board are getting: RSRQ: -12.50db RSRP: -109.00db

But my LTE phone right beside the modem is getting -108 dB 33 asu

Connection feel unstable sometimes, taking 3s-8s to get a network lock sometimes and sometimes sits there for longer than 120s and still returning +CEREG: 0,4

I bought a cell booster, now my cellphone is reading -78 dBm 62 asu

And the DK and my board reading: RSRQ: -10.50db RSRP: -63.00db

Its slightly more reliable but still not great.

2. I tried 3 completely different providers and the one I am using right now is by far the most reliable. I live in a city of ~200k in Canada and I don't really have coverage issues with my phone on the same network.

3. I am not sure what you mean by MFW, but I am compiling the serial_lte_modem example with 1 modification made to my overlay file to change serial port/output pins. Right now that is v1.8.0

But yea, is there any way to tell the modem it can use more power to get a stable connection?

RE: serial_lte_modem DNS resolution issues

Charlie — Fri, 28 Jan 2022 12:43:21 GMT

[quote user="Mr.Newlove"]Is there some way I can provide an example to test with but not be publicly visible?[/quote]

You can create a private ticket to share confidential content.

[quote user="Mr.Newlove"]Both of these issues started at the same time, everything was working fine in SDK 1.7.1, but even flashing back to that version no longer works.[/quote]

I have three suggestions to help you debug this issue:

1. You a different Hardware as a comparison. The official nRF9160DK can be a good choice. You should have at least 2 boards for comparison testing.

2. Try to use Cellular IoT service from a different opearer.

3. Check if your MFW is updated. It is always encouraged to develop with the latest MFW + NCS.

Best regards,

Charlie

RE: serial_lte_modem DNS resolution issues

Mr.Newlove — Fri, 28 Jan 2022 08:04:47 GMT

Guess it isn't the DNS server then, responds quickly with a nslookup with no errors ever. So maybe its on the nRF9160 things on going wrong.

So the specific error that ends up happening is "Failed to parse remote host" for ftp. I assume it is a similar issue going on with the HTTP lib though, because I can connect to most servers, but then I don't get any data back.

Is there some way I can provide an example to test with but not be publicly visible?

Mostly, the HTTP client can connect to almost any server no problem and I can request "/" just fine over 99% of the time. But if I request anything else, even "/test.txt" I don't get anything back, just a #XHTTPCCON: 1 and #XHTTPCRSP:0,1

Both of these issues started at the same time, everything was working fine in SDK 1.7.1, but even flashing back to that version no longer works.

RE: serial_lte_modem DNS resolution issues

Charlie — Thu, 27 Jan 2022 11:55:15 GMT

Hi Kyle,

The DNS server is normally assigned by the local network directly, and it is optimized by your network operator to get fast DNS resolution. We did not see similar complaints before, so the AT commands do not even provide the option for self-assigned DNS now.

There are three reasons that may cause the FTP connection error:

1. Please check your device has internet access after “AT+CFUN=1”, it may take time to connect with PDN even you have an LTE connection.

2. If your domain is newly set up, it may take time to let it be informed by root DNS servers.

3. You may be on the edge of the cellular network, the signal quality is poor, so the internet connection is bad.

With the following commands, your can get your PDN information including DNS address then you can test on your computer to see if they can resolve your target domain. Here is the result from my device:

+CFUN: 1
OK
AT+CGPADDR

+CGPADDR: 0,"10.160.225.xxx"
OK
AT+CGCONTRDP=0

+CGCONTRDP: 0,,"ibasis.iot","","","62.93.146.xxx","216.168.184.xxx",,,,,1430
OK

Best regards,

Charlie

RE: serial_lte_modem DNS resolution issues

Mr.Newlove — Thu, 27 Jan 2022 10:22:02 GMT

Another odd thing, that kinda confirms it being entirely a DNS problem. I didn't know this would work but I tried to convert the IP into a number and passed that instead of a domain and that worked, and oddly enough it seems to fix the DNS lookup for a short while as well?

ie:

AT#XFTP="open","******username********","*******password*****","****IP address as int****"

Edit: Spoke too soon, still fails for periods of time.