Hello,
We are working with the nrf 9160 dk.
We need to use internet connectivity to send an http get and post to a remote server.
We want to utilize the NB-IoT modem on the board.
As it stands now, can get connected to the network but we cannot send a get or post to the remote server.
Kindly let us know if there is a configuration or a example code we can use to achieve this.
Thanks and regards
Hi,
There's a https sample in ncs that might be helpful:
https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/samples/nrf9160/https_client
Could you try this and see if this fits your needs?
Kind regards,
Håkon
Hello Hakon,
Thank you so much for the reply.
Please find below the results we get;
errno = 60
HTTPS client sample started Provisioning certificate Waiting for network.. OK Connecting to google.com connect() failed, err: 60
Please note that we are in siracusa Italy so we only have NB-IoT, we therefore added the config
CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y
to the prj.conf file.
Kindly help us know what we need to check
Hi,
smauelGIS said:Did you use CONFIG_LTE_NETWORK_MODE_NBIOT=y for the test with NB1?
Yes, I tested with this config entry.
smauelGIS said:It still hangs infact at getaddrinfo() procedure. we get an error code 60.
This indicates that the network you're connected to does not provide a DNS service (getaddrinfo cannot resolve the hostname), or that its currently unavailable.
You can manually resolve the hostname at your end, and input that as a string, like this "127.0.0.1".
Kind regards,
Håkon
Thanks for the response;
So when we do my the manual resolving as you suggested; for example for google.com ("216.58.208.174"), getaddinfo() is ok, but we still get stuck at connect(), with an error "connect() failed, err: 60".
As you may note, this was the first error I sent to you at the start of this thread! We did manual resolving of google's hostname.
Please is there another config we need to do? Or a hardware plug we need to push?
Kindly help
Regards.
Hi,
I tested setting the same IP in https_client sample, and had no problems connecting afterwards. However; I am on a completely different network than you.
smauelGIS said:Please is there another config we need to do? Or a hardware plug we need to push?
The behavior you see is highly likely inherited from the network that you are connecting to.
Have you tested if TCP works at all in your current network?
Did you try mqtt_simple, where you set the IP manually in prj.conf? mqtt.eclipse.org currently resolves to 137.135.83.217, so that would be:
CONFIG_MQTT_BROKER_HOSTNAME="137.135.83.217"
If that fails, try an UDP based sample, like this one (Change define NTP_HOST to 129.240.2.6):
https://github.com/Rallare/fw-nrfconnect-nrf/blob/nrf9160_samples/samples/nrf9160/ntp/src/main.c
Kind regards,
Håkon
Have you tested if TCP works at all in your current network?
could you provide may be an AT command to test a TCP connection? I tried to get an AT command for a ping, but i could not find one at the reference site.
the mqtt_sample even with the resolved IP does not work.
I will try the UDP sample you sent.
Thanks and Regards.
P.S kindly help with a tool to check if TCP works on a network.
Regards
Hi,
The AT commands do not include any IP related commands, unfortunately. UDP and TCP tests must be performed on a socket level.
Kind regards,
Håkon
Hi,
The AT commands do not include any IP related commands, unfortunately. UDP and TCP tests must be performed on a socket level.
Kind regards,
Håkon
Hello,
Thanks for the reponse again!
I tried the UDP sample you shared, below is the results;
*** Booting Zephyr OS build v2.1.99-ncs1 *** getaddrinfo err: 0 client_fd: 2 bind err: 0 sendto ret: 48
Do you think it may be the sim? We are using a sim from iBasis with ICCID
893108001907353225
Kindly let us know.
Regards
Hello,
We utlized the project below;
https://github.com/Rallare/fw-nrfconnect-nrf/tree/nrf9160_samples/samples/nrf9160/http
and its working with a resolved ip for google.
Thanks so much for your help
Regards
Hi,
smauelGIS said:and its working with a resolved ip for google.
That is great to hear!
Kind regards,
Håkon
