Hi,
I was using the AWS-IOT example and all was working until it wasnt. In troubleshooting this, I loaded the modem shell example, to see if it was a network/connection issue and although it connects (I get an IP), I am unable to ping google.com (by name or IP).
I looked at nrfcloud.com and the sim appears to have enough data left, Used 2.79MB of the 10MB . Its iBasis sim that came with the board.
Details of the ping are below, I was wondering who to contact for this? Nordic or iBasis ?
Output:
*** Booting Zephyr OS build v2.6.0-rc1-ncs1 ***
MOSH version: v1.6.0
MOSH build id: custom
MOSH build variant: dev
Initializing modemlib...
mosh:~$ Initialized modemlib
Network registration status: searching
LTE cell changed: Cell ID: 136926477, Tracking area: 12306
Currently active system mode: LTE-M
RRC mode: Connected
PDN event: PDP context 0 activated
Network registration status: Connected - roaming
PSM parameter update: TAU: -1, Active time: -1 seconds
Modem config for system mode: LTE-M
Modem config for LTE preference: No preference, automatically selected by the modem
Currently active system mode: LTE-M
Modem FW version: mfw_nrf9160_1.2.3
Operator PLMN: "50501"
Current cell id: 136926477 (0x0829550D)
Current band: 28
Current rsrp: 40: -101dBm
Current snr: 31: 6dB
Mobile network time and date: 21/10/02,05:33:39+40
PDP context info 1:
CID: 0
PDN ID: 0
PDP context active: yes
PDP type: IP
APN: ibasis.iot
IPv4 MTU: 1430
IPv4 address: 10.155.149.218
IPv6 address: ::
IPv4 DNS address: 62.93.146.209, 216.168.184.184
IPv6 DNS address: ::, ::
ping -d www.google.com
Initiating ping to: www.google.com
RRC mode: Connected
getaddrinfo(dest) error: -11
Cannot resolve remote host
RRC mode: Idle
mosh:~$ ping 142.25
mosh:~$
mosh:~$ ping -d 142.250.66.228
Initiating ping to: 142.250.66.228
Source IP addr: 10.155.149.218
Destination IP addr: 142.250.66.228
RRC mode: Connected
Pinging 142.250.66.228 results: no response in given timeout 3000 msec
Pinging 142.250.66.228 results: no response in given timeout 3000 msec
Pinging 142.250.66.228 results: no response in given timeout 3000 msec
Pinging 142.250.66.228 results: no response in given timeout 3000 msec
Ping statistics for 142.250.66.228:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Pinging DONE
regards
-brett