PK Chan 9f9e00a62d net: mqtt: Added event for MQTT ping response. ... There are scenarios where there is a NAT firewall in between MQTT client and server. In such case, the NAT TCP timeout may be shorter than MQTT keepalive timeout and TCP timeout. The the MQTT ping request message is dropped by the NAT firewall, so that it cannot be received by the server, resulting in void MQTT ping response message. There is no TCP FIN or RST at all. The application looks hang-up until TCP timeout happens on the client side, which may take too long. Therefore, the event MQTT_EVT_PINGRESP is added to inform the application that the route between client and server is still valid. Signed-off-by: PK Chan <pak.kee.chan@nordicsemi.no>		2020-03-12 11:07:14 +02:00
..
ip	net: shell: Handle ENETUNREACH for IPv4 ping	2020-03-11 13:25:55 -05:00
l2	net: wifi: shell: drop explicit length parameter	2020-03-10 14:37:57 +02:00
lib	net: mqtt: Added event for MQTT ping response.	2020-03-12 11:07:14 +02:00
buf.c	net: buf: Switch from net buf assert to system assert	2020-01-13 13:59:55 +01:00
CMakeLists.txt
hostname.c
Kconfig
Kconfig.hostname
Kconfig.template.log_config.default.net
Kconfig.template.log_config.net