modem shell : connects but fails to send traffic

RE: modem shell : connects but fails to send traffic

Charlie — Mon, 04 Oct 2021 12:32:37 GMT

Hi Brett,

You can enable mode trace recording to get more details. nRF Connect for Desktop -> Trace Collector V2 Preview allows the developer to review the modem trace RCAP data directly with Wirehark.

Looking forward to seeing the result of your further experiments.

Best regard,

Charlie

RE: modem shell : connects but fails to send traffic

Brett — Mon, 04 Oct 2021 12:28:57 GMT

Hi Charlie,

Sorry for the spam :) dont know why I didnt think of this earlier....

I used the sim from my phone, and it all worked fine - so I gather its an issue with iBasis ?

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 - home network
PSM parameter update: TAU: -1, Active time: -1 seconds
PDN event: PDP context 0 IPv6 up
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.3.0
Operator full name:   "Telstra #LetsVaxx"
Operator short name: "Telstra@"
Operator PLMN:        "50501"
Current cell id:       136926477 (0x0829550D)
Current band:          28
Current rsrp:          44: -97dBm
Current snr:           29: 4dB
Mobile network time and date: 21/10/04,12:26:15+44
PDP context info 1:
CID:                    0
PDN ID:                 0
PDP context active:     yes
PDP type:               IPV4V6
APN:                    telstra.internet
IPv4 MTU:               1500
IPv4 address:           10.115.220.233
IPv6 address:           2001:8004:2748:f59:801a:b250:e5fa:8ad0
IPv4 DNS address:       101.168.244.100, 10.4.58.204
IPv6 DNS address:       2001:8004:2d43:900::, 2001:8004:0:100:7:e1c0:0:14
mosh:~$
mosh:~$ ping -d www.google.com
Initiating ping to: www.google.com
Source IP addr: 10.115.220.233
Destination IP addr: 142.250.70.164
Pinging www.google.com results: time=0.079secs, payload sent: 0, payload received 0
Pinging www.google.com results: time=0.092secs, payload sent: 0, payload received 0
Pinging www.google.com results: time=0.098secs, payload sent: 0, payload received 0
Pinging www.google.com results: time=0.098secs, payload sent: 0, payload received 0

Ping statistics for www.google.com:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
    Minimum = 79ms, Maximum = 98ms, Average = 91ms
Pinging DONE
RRC mode: Idle
mosh:~$

RE: modem shell : connects but fails to send traffic

Brett — Mon, 04 Oct 2021 12:16:21 GMT

Hi Charlie,

Modem Upgraded to 1.3.0, still same issue, and whats more strange, I cant even ping the DNS that was allocated.

Tried to:
* Ping google.com - failed
* ping Ip of google - failed
* ping DNS - failed
* increased timeout to 10 seconds, just in case.

I will install the 1.7.0 SDK and see how that goes. As mentioned earlier, I am more confused as to why all was working with the current environment, and all of the sudden it stopped working.

Q: If the SIM was expired, or something wrong with it, would you expect to still get connections and an IP ?

Ping:
ping -t 10000 -d 62.93.146.209
Initiating ping to: 62.93.146.209
Source IP addr: 10.155.196.172
Destination IP addr: 62.93.146.209
RRC mode: Connected
Pinging 62.93.146.209 results: no response in given timeout 10000 msec
RRC mode: Idle
RRC mode: Connected
Pinging 62.93.146.209 results: no response in given timeout 10000 msec
RRC mode: Idle
RRC mode: Connected
Pinging 62.93.146.209 results: no response in given timeout 10000 msec
Pinging 62.93.146.209 results: no response in given timeout 10000 msec

Ping statistics for 62.93.146.209:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

Pinging DONE
RRC mode: Idle

Boot Details:
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.3.0
Operator PLMN:        "50501"
Current cell id:       136926477 (0x0829550D)
Current band:          28
Current rsrp:          41: -100dBm
Current snr:           26: 1dB
Mobile network time and date: 21/10/04,11:57:39+44
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.196.172
IPv6 address:           ::
IPv4 DNS address:       62.93.146.209, 216.168.184.184
IPv6 DNS address:       ::, ::
RRC mode: Idle

cheers

-brett

RE: modem shell : connects but fails to send traffic

Brett — Mon, 04 Oct 2021 11:46:53 GMT

Hi Charlie,

This has been working fine for months, so I dont think its the local network.

I only have 1 x 9160DK - (I have a thingy 91 that I could try and swap the sim into), I also have a new sim coming from iBasis to replace the one from the thingy 91 (it expired).

I will upgrade the modem firmware to the latest and try that.

I was more curious how to troubleshoot where the problem might be and if there is any other way to identify if its, sim, network, board etc...

cheers

-brett

RE: modem shell : connects but fails to send traffic

Charlie — Mon, 04 Oct 2021 11:09:56 GMT

Hi Brett,

It looks everything is fine before you start to use ping commands.

I am not sure if this is an issue due to the local LTE network or just related to a specific sim card or hardware. Do you have several nRF9160DK boards to test with? Are you able to update Modem firmware to the latest and test with the latest NCS v1.7.0?

Best regards,

Charlie