nRF9160 ping event with AWS IoT

[ksksue]

How does the device catch incoming ping events?

The device uses AWS IoT library, so it can't open a raw socket.

It looks like the ping events closed inside the modem binary.

So, this code does not run.

/opt/nordic/ncs/v2.0.2/zephyr/subsys/net/ip/icmpv4.c

Are there any ping event APIs? or sniffing raw packets?

nRF9160
mfw_nrf9160_1.3.2
nRF Connect SDK v.2.0.2

---------------------------------------
Update 2023-10-13

I use a diagram to explain what I want to achieve and what is actually difficult to achieve.

[Håkon Alseth]

Hi,

 

ICMP reply is handled in slm via a raw socket type:

https://github.com/nrfconnect/sdk-nrf/blob/v2.4.99-dev2/applications/serial_lte_modem/src/slm_at_icmp.c#L297-L345

 

It is polled similar to any other socket type.

 

The device uses AWS IoT library, so it can't open a raw socket.

Are you thinking of the keepalive for mqtt? This is configured via CONFIG_MQTT_KEEPALIVE

 

Kind regards,

Håkon

[ksksue]

If a raw socket is opened, AWS IoT's packet goes to the raw socket. And communication with AWS IoT is no longer possible.

A) 
application <--> AWS IoT(mqtt socket zephyr/subsys/net/lib/mqtt/mqtt_transport_socket_tls.c)
                  <--> ping (can't catch the events)

B) open a raw socket
application <-X-> AWS IoT(mqtt socket zephyr/subsys/net/lib/mqtt/mqtt_transport_socket_tls.c)
                   <--> raw socket send/recv (It can catch ping events)

If pattern B, unintentionally, raw socket receives AWS IoT's packet and AWS IoT's library stops working.

So, in the case of pattern A, I want to catch the ping events.

[Håkon Alseth]

Hi,

 

I'm uncertain about what you're asking about in this case.

Are you asking about ICMP in the generic LTE Network?

 

Or do you want to dump the IP trace?

If yes, then you can do this by enabling modem traces and using this tool (+ Wireshark): https://infocenter.nordicsemi.com/topic/ug_cellular_monitor/UG/cellular_monitor/intro.html?cp=11_3_1

 

Kind regards,

Håkon

[ksksue]

I think that the SDK can't use both AWS IoT library and raw socket.
Is this correct or incorrect?

If incorrect, I try this.

> ICMP reply is handled in slm via a raw socket type:
> https://github.com/nrfconnect/sdk-nrf/blob/v2.4.99-dev2/applications/serial_lte_modem/src/slm_at_icmp.c#L297-L345

I don't want to dump the IP trace.

[ksksue]

Thanks for the idea. 

I try this.

> ICMP reply is handled in slm via a raw socket type:

> https://github.com/nrfconnect/sdk-nrf/blob/v2.4.99-dev2/applications/serial_lte_modem/src/slm_at_icmp.c#L297-L345

But unfortunately, the results did not turn out as expected.
I try to rewrote the code from sample/aws_iot.
https://github.com/ksksue/aws_iot_raw_socket/blob/8872d0894aaa9e67ae22f1ac448ab30a6144d2ec/src/main.c#L479-L655

If raw socket open (call wan_socket_open), I can get ICMP packet. but, I cannot connect AWS IoT.

AWS_IOT_EVT_CONNECTING
...
D:     src xxx.xxx.xxx.xxx, dst xxx.xxx.xxx.xxx
D:   ICMP(8) type 8, code 0, csum 0x910f, id 51, seq 
...
(not AWS_IOT_EVT_CONNECTED)

If connecting AWS IoT (comment out wan_socket_open()), I can't get ICMP packet.

How  to catch incoming ping events with connecting AWS IoT?