MQTTS connection speed that does not require any certificate is very slow.

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Wed, 28 Apr 2021 11:20:26 GMT

Thanks for the trace.

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Wed, 28 Apr 2021 02:29:59 GMT

I think this is a SDK bug, not a modem firmware problem. I reacquired the modem trace.devzone.nordicsemi.com/.../trace_2D00_2021_2D00_04_2D00_28T02_2D00_21_2D00_08.402Z.bin

This is a demo.devzone.nordicsemi.com/.../6661.mqtt_5F00_simple_5F00_test.rar

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Tue, 27 Apr 2021 11:04:38 GMT

[quote user="xinjiang"]What is the reason for errno = -45?[/quote]

It is usually a certificate issue. The best to know for sure is to do a proper modem trace to get the details from the TLS handshake.

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Tue, 20 Apr 2021 09:05:24 GMT

int mqtt_client_tls_connect(struct mqtt_client *client)
{
	const struct sockaddr *broker = client->broker;
	struct mqtt_sec_config *tls_config = &client->transport.tls.config;
	int ret;

	client->transport.tls.sock = zsock_socket(broker->sa_family,
						  SOCK_STREAM, IPPROTO_TLS_1_2);
	if (client->transport.tls.sock < 0) {
		return -errno;
	}

	MQTT_TRC("Created socket %d", client->transport.tls.sock);

#if defined(CONFIG_SOCKS)
	if (client->transport.proxy.addrlen != 0) {
		ret = setsockopt(client->transport.tls.sock,
				 SOL_SOCKET, SO_SOCKS5,
				 &client->transport.proxy.addr,
				 client->transport.proxy.addrlen);
		if (ret < 0) {
			return -errno;
		}
	}
#endif
	/* Set secure socket options. */
	ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS, TLS_PEER_VERIFY,
			       &tls_config->peer_verify,
			       sizeof(tls_config->peer_verify));
	if (ret < 0) {
		goto error;
	}

	if (tls_config->cipher_list != NULL && tls_config->cipher_count > 0) {
		ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS,
				       TLS_CIPHERSUITE_LIST, tls_config->cipher_list,
				       sizeof(int) * tls_config->cipher_count);
		if (ret < 0) {
			goto error;
		}
	}

	if (tls_config->sec_tag_list != NULL && tls_config->sec_tag_count > 0) {
		ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS,
				       TLS_SEC_TAG_LIST, tls_config->sec_tag_list,
				       sizeof(sec_tag_t) * tls_config->sec_tag_count);
		if (ret < 0) {
			goto error;
		}
	}

	if (tls_config->hostname) {
		ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS,
				       TLS_HOSTNAME, tls_config->hostname,
				       strlen(tls_config->hostname));
		if (ret < 0) {
			goto error;
		}
	}

	if (tls_config->session_cache == TLS_SESSION_CACHE_ENABLED) {
		ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS,
				       TLS_SESSION_CACHE,
				       &tls_config->session_cache,
				       sizeof(tls_config->session_cache));
		if (ret < 0) {
			goto error;
		}
	}

	size_t peer_addr_size = sizeof(struct sockaddr_in6);

	if (broker->sa_family == AF_INET) {
		peer_addr_size = sizeof(struct sockaddr_in);
	}

	ret = zsock_connect(client->transport.tls.sock, client->broker,
			    peer_addr_size);
	if (ret < 0) {
		goto error;
	}

	MQTT_TRC("Connect completed");
	return 0;

error:
	(void) zsock_close(client->transport.tls.sock);
	return -errno;
}

The problem lies in the zsock_connect() function on line 77.

Finally, through breakpoint debugging, it is found that the nrf_modem_os_errno_set() function in the nrf_modem_os.c file will set errno = EOPNOTSUPP

What is the reason for errno = -45?

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Mon, 19 Apr 2021 10:07:21 GMT

Hi again,

the modem trace you provide does not contain the necessary information about the connection attempt.

"Modem trace is only 15 seconds long and contains 2 DNS queries sent by application. Not a sign for TLS connection establishment. Signal level seems to be in good level."

It would be nice if you could take a new trace and get all the details from the connection attempt.

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Wed, 14 Apr 2021 10:51:52 GMT

modem 1.2.3

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Wed, 14 Apr 2021 10:50:38 GMT

Thank you. What modem firmware was this tested on?

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Tue, 13 Apr 2021 02:07:35 GMT

I reproduced this phenomenon on another DK board. Attached is the captured modem info.devzone.nordicsemi.com/.../trace_2D00_2021_2D00_04_2D00_13T01_2D00_58_2D00_55.612Z.bin

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Mon, 12 Apr 2021 12:59:25 GMT

You can try reproducing the connection issue while having modem trace enabled. Then hopefully we can see from the trace why the connection is failing.

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Mon, 12 Apr 2021 11:30:16 GMT

Kconfig defines CONFIG_MQTT_TLS_SEC_TAG as 24

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Mon, 12 Apr 2021 11:24:14 GMT

[quote user="xinjiang"]Where do I need to write the certificate to ensure normal connection?[/quote]

It probably needs to match CONFIG_MQTT_TLS_SEC_TAG. Have you checked the value of this parameter?

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Mon, 12 Apr 2021 02:23:08 GMT

I randomly wrote a CA certificate at sec_tag 24.

The problem is still not solved,Error log:

Where do I need to write the certificate to ensure normal connection?

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Fri, 09 Apr 2021 14:35:46 GMT

As far as I know you should not attempt to use TLS without a CA certificate on the device, even though you are not using it.

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Thu, 08 Apr 2021 10:53:07 GMT

Hi,

I changed to another 91 chip and burned the same program. -45 error occurred in mqtt connection : Operation not supported on socket. Here is my log:

[00:00:00.243,316] [0m<inf> main: Connecting to LTE network.[0m
[00:00:00.243,316] [0m<inf> main: This may take several minutes.[0m
[00:00:00.243,377] [0m<inf> flash_control: No apn found, use default apn[0m
[00:00:00.249,908] [0m<inf> main: Set to the default APN CMNBIOT2.[0m
[00:00:00.258,087] [0m<inf> lte_lc: Using legacy LTE PCO mode...[0m

[18:48:48.897]收←◆[00:00:01.725,158] [0m<inf> mai
[18:48:48.919]收←◆n: LTE ERROR[0m
[00:00:02.258,117] [0m<inf> main: CSCON : 1[0m

[18:48:50.833]收←◆[00:00:04.283,386] [0m<inf> main: Connected to LTE network.[0m
[00:00:04.283,477] [0m<inf> main: LTE SUCCESS[0m
[00:00:04.286,163] [0m<inf> mqtt_engine: IPv4 Address found 47.106.164.80[0m
[00:00:04.286,193] [0m<inf> mqtt_engine: TLS enabled[0m
[00:00:04.286,468] [0m<dbg> net_mqtt_sock_tls.mqtt_client_tls_connect: (0x20015220): Created socket 1[0m
[00:00:04.660,552] [1;31m<err> mqtt_engine: mqtt_connect -45[0m
[00:00:04.660,583] [1;31m<err> mqtt_engine: ERROR: mqtt_disconnect -57[0m

-45 is EOPNOTSUPP, and typically indicates that you have written wrong certificates to the device. But I had peer_verify set to 0.

RE: MQTTS connection speed that does not require any certificate is very slow.

xinjiang — Tue, 23 Mar 2021 06:49:25 GMT

I replaced a 0.9.0 DK for testing and found that the connection speed is normal.

log:

[14:38:54.742]收←◆*** Booting Zephyr OS build v2.4.99-ncs1  ***

[14:38:55.752]收←◆[00:00:00.211,486] [0m<inf> mqtt_simple: The MQTT simple sample started[0m
[00:00:00.211,486] [0m<inf> mqtt_simple: Provisioning certificates[0m
[00:00:00.211,486] [0m<inf> mqtt_simple: Disabling PSM and eDRX[0m
[00:00:00.225,280] [0m<inf> mqtt_simple: LTE Link Connecting...[0m
[00:00:00.235,137] [0m<inf> lte_lc: Using legacy LTE PCO mode...[0m

[14:38:58.079]收←◆+CEREG: 2,"1D2C","0D61D950",9,0,0,"11100000","11100000"

[14:38:58.646]收←◆+CSCON: 1

[14:38:59.826]收←◆+CEREG: 1,"1D2C","0D61D950",9,,,"11100000","11100000"

[14:39:00.832]收←◆[00:00:05.290,588] [0m<inf> mqtt_simple: LTE Link Connected![0m
[00:00:05.291,015] [0m<inf> mqtt_simple: IPv4 Address found 47.106.164.80[0m
[00:00:05.291,015] [0m<inf> mqtt_simple: TLS enabled[0m
[00:00:05.291,412] [0m<dbg> net_mqtt_sock_tls.mqtt_client_tls_connect: (0x20014ae8): Created socket 1[0m

[14:39:04.680]收←◆[00:00:10
[14:39:04.710]收←◆.138,397] [0m<dbg> net_mqtt_sock_tls.mqtt_client_tls_connect: (0x20014ae8): Connect completed[0m
[00:00:10.138,427] [0m<dbg> net_mqtt_enc.connect_request_encode: (0x20014ae8): Encoding Protocol Description. Str:MQTT Size:00000004.[0m
[00:00:10.138,427] [0m<dbg> net_mqtt_enc.pack_utf8_str: (0x20014ae8): >> str_size:00000006 cur:0x20015e0f,
[14:39:04.733]收←◆ end:0x20015e8a[0m
[00:00:10.138,458] [0m<dbg> net_mqtt_enc.pack_uint16: (0x20014ae8): >> val:0004 cur:0x20015e0f, end:0x20015e8a[0m
[00:00:10.138,458] [0m<dbg> net_mqtt_enc.connect_request_encode: (0x20014ae8): Encoding Protocol Version 04.[0m
[00:00:10.138,458] [0m<dbg> net_mqtt_enc.pack_uint8: (0x20014ae8): >> val:04 cur:0x20015e15, end:0x20015e8a[0m
[00:00:10.138,488] [0m<dbg> net_mqtt_enc.pack_uint8: (0x20014ae8): >> val:00 cur:0x20015e16, end:0x20015e8a[0m
[00:00:10.138,488] [0m<dbg> net_mqtt_enc.connect_request_encode: (0x20014ae8): Encoding Keep Alive Time 003c.[0m
[00:00:10.138,488] [0m<dbg> net_mqtt_enc.pack_uint16: (0x20014ae8): >> val:003c cur:0x20015e17, end:0x20015e8a[0m
[00:00:10.138,488] [0m<dbg> net_mqtt_enc.connect_request_encode: (0x20014ae8): Encoding Client Id. Str:my/test/id Size:0000000a.[0m
[00:00:10.138,519] [0m<dbg> net_mqtt_enc.pack_utf8_str: (0x20014ae8): >> str_size:0000000c cur:0x20015e19, end:0x20015e8a[0m
[00:00:10.138,519] [0m<dbg> net_mqtt_enc.pack_uint16: (0x20014ae8): >> val:000a cur:0x20015e19, end:0x20015e8a[0m
[00:00:10.138,549] [0m<dbg> net_mqtt_enc.mqtt_encode_fixed_header: (0x20014ae8): << msg type:0x10 length:0x00000016[0m
[00:00:10.138,549] [0m<dbg> net_mqtt_enc.packet_length_encode: (0x20014ae8): >> length:0x00000016 cur:(nil), end:(nil)[0m
[00:00:10.138,549] [0m<dbg> net_mqtt_enc.mqtt_encode_fixed_header: (0x20014ae8): Fixed header length = 02[0m
[00:00:10.138,580] [0m<dbg> net_mqtt_enc.pack_uint8: (0x20014ae8): >> val:10 cur:0x20015e0d, end:0x20015e8a[0m
[00:00:10.138,580] [0m<dbg> net_mqtt_enc.packet_length_encode: (0x20014ae8): >> length:0x00000016 cur:0x20015e0e, end:0x20015e8a[0m
[00:00:10.139,343] [0m<dbg> net_mqtt.client_connect: (0x20014ae8): Connect completed[0m
[00:00:10.327,514] [0m<dbg> net_mqtt_dec.unpack_uint8: (0x20014ae8): << val:00[0m
[1;31m--- 7 messages dropped ---
[0m[00:00:10.327,514] [0m<dbg> net_mqtt_dec.unpack_uint8: (0x20014ae8): << val:00[0m
[00:00:10.327,545] [0m<dbg> net_mqtt_dec.connect_ack_decode: (0x20014ae8): [CID 0x20014c98]: session_present_flag: 0[0m
[00:00:10.327,545] [0m<dbg> net_mqtt_rx.mqtt_handle_packet: (0x20014ae8): [CID 0x20014c98]: return_code: 0[0m
[00:00:10.327,575] [0m<inf> mqtt_simple: MQTT client connected[0m
[00:00:10.327,575] [0m<inf> mqtt_simple: Subscribing to: my/subscribe/topic len 18[0m
[00:00:10.327,575] [0m<dbg> net_mqtt.mqtt_subscribe: (0x20014ae8): [CID 0x20014c98]:[State 0x06]: >> message id 0x04d2 topic count 0x0001[0m
[00:00:10.327,606] [0m<dbg> net_mqtt_enc.pack_uint16: (0x20014ae8): >> val:04d2 cur:0x20015e0f, end:0x20015e8a[0m
[00:00:10.327,606] [0m<dbg> net_mqtt_enc.pack_utf8_str: (0x20014ae8): >> str_size:00000014 cur:0x20015e11, end:0x20015e8a[0m
[00:00:10.327,636] [0m<dbg> net_mqtt_enc.pack_uint16: (0x20014ae8): >> val:0012 cur:0x20015e11, end:0x20015e8a[0m
[00:00:10.327,636] [0m<dbg> net_mqtt_enc.pack_uint8: (0x20014ae8): >> val:01 cur:0x20015e25, end:0x20015e8a[0m
[00:00:10.327,636] [0m<dbg> net_mqtt_enc.mqtt_encode_fixed_header: (0x20014ae8): << msg type:0x82 length:0x00000017[0m
[00:00:10.327,667] [0m<dbg> net_mqtt_enc.packet_length_encode: (0x20014ae8): >> length:0x00000017 cur:(nil), end:(nil)[0m
[00:00:10.327,667] [0m<dbg> net_mqtt_enc.mqtt_encode_fixed_header: (0x20014ae8): Fixed header length = 02[0m
[00:00:10.327,697] [0m<dbg> net_mqtt_enc.pack_uint8: (0x20014ae8): >> val:82 cur:0x20015e0d, end:0x20015e8a[0m
[00:00:10.327,728] [0m<dbg> net_mqtt_enc.packet_length_encode: (0x20014ae8): >> length:0x00000017 cur:0x20015e0e, end:0x20015e8a[0m
[00:00:10.327,758] [0m<dbg> net_mqtt.client_write: (0x20014ae8): [0x20014c98]: Transport writing 25 bytes.[0m
[00:00:10.328,491] [0m<dbg> net_mqtt.client_write: (0x20014ae8): [0x20014c98]: Transport write complete.[0m
[00:00:10.328,521] [0m<dbg> net_mqtt.mqtt_subscribe: (0x20014ae8): [CID 0x20014c98]:[State 0x06]: << result 0x00000000[0m
[00:00:10.518,341] [0m<dbg> net_mqtt.mqtt_input: (0x20014ae8): state:0x00000006[0m
[00:00:10.518,402] [0m<dbg> net_mqtt_dec.unpack_uint8: (0x20014ae8): >> cur:0x20015d8a, end:0x20015d8c[0m
[00:00:10.518,402] [0m<dbg> net_mqtt_dec.unpack_uint8: (0x20014ae8): << val:90[0m
[00:00:10.518,402] [0m<dbg> net_mqtt_dec.packet_length_decode: (0x20014ae8): length:0x00000003[0m
[00:00:10.518,463] [0m<dbg> net_mqtt_rx.mqtt_handle_packet: (0x20014ae8): [CID 0x20014c98]: Received MQTT_PKT_TYPE_SUBACK![0m
[00:00:10.518,493] [0m<dbg> net_mqtt_dec.unpack_uint16: (0x20014ae8): >> cur:0x20015d8c, end:0x20015d8f[0m
[00:00:10.518,493] [0m<dbg> net_mqtt_dec.unpack_uint16: (0x20014ae8): << val:04d2[0m
[00:00:10.518,493] [0m<dbg> net_mqtt_dec.unpack_data: (0x20014ae8): >> cur:0x20015d8e, end:0x20015d8f[0m
[00:00:10.518,493] [0m<dbg> net_mqtt_dec.unpack_data: (0x20014ae8): << bin len:00000001[0m
[00:00:10.518,524] [0m<inf> mqtt_simple: SUBACK packet id: 1234[0m

I will report the problem to you after I catch it.

RE: MQTTS connection speed that does not require any certificate is very slow.

Hakon — Mon, 22 Mar 2021 12:47:39 GMT

Hello,

can you set

CONFIG_NET_LOG=y
CONFIG_MQTT_LOG_LEVEL_DBG=y

for more detailed log output?