ZB ZCL Tunneling - no data send

RE: ZB ZCL Tunneling - no data send

Edvin — Fri, 22 May 2020 09:09:59 GMT

Hello,

Can you please try the following:

Can you do these changes in sdk_config.h:

#define ZIGBEE_TRACE_LEVEL 4
#define ZIGBEE_TRACE_MASK 0x0148

And check the log output. It will look quite cryptic (because it is). Can you copy the logs and attach them here?

Best regards,

Edvin

RE: ZB ZCL Tunneling - no data send

karolpro — Wed, 06 May 2020 07:28:51 GMT

This is a temporary workaround, but good enough for proof of concept. I still want to use tunneling and I'd prefer using "official" API functions rather then manually constructed frames.

RE: ZB ZCL Tunneling - no data send

Edvin — Wed, 06 May 2020 06:56:53 GMT

Does this mean that you will not use the tunnelling, or is this a temporary workaround_

RE: ZB ZCL Tunneling - no data send

karolpro — Tue, 05 May 2020 16:25:51 GMT

PS. I've implemented sending transfer data command manually (without using zb_zcl_tunneling_client_send_transfer_data & zb_zcl_tunneling_server_send_transfer_data functions) and I'm able to achieve expected flow in the network.

I'm attaching logs showing requesting tunnel, sending data to server, and back to client, then closing tunnel).

devzone.nordicsemi.com/.../log_5F00_ok.pcapng

RE: ZB ZCL Tunneling - no data send

karolpro — Tue, 05 May 2020 14:31:36 GMT

Ok, thank you very much.

RE: ZB ZCL Tunneling - no data send

Edvin — Tue, 05 May 2020 14:25:06 GMT

Hello,

Yes. I received them. I have forwarded the questions to our Zigbee team. I will let you know whenever I hear something from them.

RE: ZB ZCL Tunneling - no data send

karolpro — Tue, 05 May 2020 08:25:12 GMT

Hi, I sent you projects yesterday in a private message. Did you get them?

RE: ZB ZCL Tunneling - no data send

Edvin — Thu, 30 Apr 2020 14:36:12 GMT

Is it possible to send the project as well for reproduction of the issue?

RE: ZB ZCL Tunneling - no data send

karolpro — Thu, 30 Apr 2020 14:04:24 GMT

Here goes logs in .pcapng format:
devzone.nordicsemi.com/.../logs_5F00_ret_5F00_code_5F00_error.pcapng devzone.nordicsemi.com/.../logs_5F00_ret_5F00_code_5F00_ok.pcapng

I'm using two DK boards for that + dongle for sniffing. It's tunneling between two Zigbee devices to send some proprietary number (in that example just sending 'O' & 'K' from client to server and back).

RE: ZB ZCL Tunneling - no data send

Edvin — Thu, 30 Apr 2020 13:49:43 GMT

Do you use the Nordic 802.15.4 sniffer? If so, can you save the sniffer trace as the default file type (.pcapng) and upload it?

Is this issue something I can reproduce using a couple of DKs? Or does it require some external HW? I didn't quite understand if this tunnel was through an internet server or not.

BR,

Edvin

RE: ZB ZCL Tunneling - no data send

karolpro — Thu, 30 Apr 2020 13:22:47 GMT

Hi, thanks for quick response. Here goes two log files from Wireshark.

The first is when zb_zcl_tunneling_client_send_transfer_data returns -1 (server sends only one tunnel request response with success before transfer data request):

		case ZB_ZCL_TUNNELING_CLI_CMD_REQUEST_TUNNEL:
		{
			zb_zcl_tunneling_request_tunnel_t tunnel_req;
			zb_zcl_parse_status_t status;
			zb_bufid_t buf_resp = zb_buf_get_out();

			ZB_ZCL_TUNNELING_GET_REQUEST_TUNNEL(&tunnel_req, bufid, status);

			(void)status;

			if(ZB_TRUE == tunnel_opened)
			{
				ZB_ZCL_TUNNELING_SEND_REQUEST_TUNNEL_RESPONSE(buf_resp, header->addr_data.common_data.source.u, header->addr_data.common_data.source.addr_type == ZB_ZCL_ADDR_TYPE_SHORT ? ZB_APS_ADDR_MODE_16_ENDP_PRESENT : ZB_APS_ADDR_MODE_64_ENDP_PRESENT, TUNNEL_SRV_ENDPOINT, TUNNEL_SRV_ENDPOINT, ZB_AF_HA_PROFILE_ID, ZB_ZCL_DISABLE_DEFAULT_RESPONSE, ZB_ZCL_GET_SEQ_NUM(), NULL, 0x0, ZB_ZCL_TUNNELING_STATUS_NO_MORE_IDS, tunnel_req.max_incoming_transfer_size );
			}
			else
			{
				tunnel_opened = ZB_TRUE;
				ZB_ZCL_TUNNELING_SEND_REQUEST_TUNNEL_RESPONSE(buf_resp, header->addr_data.common_data.source.u, header->addr_data.common_data.source.addr_type == ZB_ZCL_ADDR_TYPE_SHORT ? ZB_APS_ADDR_MODE_16_ENDP_PRESENT : ZB_APS_ADDR_MODE_64_ENDP_PRESENT, TUNNEL_SRV_ENDPOINT, TUNNEL_SRV_ENDPOINT, ZB_AF_HA_PROFILE_ID, ZB_ZCL_DISABLE_DEFAULT_RESPONSE, ZB_ZCL_GET_SEQ_NUM(), NULL, tunnel_id, ZB_ZCL_TUNNELING_STATUS_SUCCESS, tunnel_req.max_incoming_transfer_size );
			}

		    return ZB_TRUE;
		}

devzone.nordicsemi.com/.../logs_5F00_ret_5F00_code_5F00_error.txt

The second is when zb_zcl_tunneling_client_send_transfer_data 0 (server sends two tunnel request response one after another, first with no more tunnels available, second with success before transfer data request):

		case ZB_ZCL_TUNNELING_CLI_CMD_REQUEST_TUNNEL:
		{
			zb_zcl_tunneling_request_tunnel_t tunnel_req;
			zb_zcl_parse_status_t status;
			zb_bufid_t buf_resp = zb_buf_get_out();
			zb_bufid_t buf_resp_dummy = zb_buf_get_out();

			ZB_ZCL_TUNNELING_GET_REQUEST_TUNNEL(&tunnel_req, bufid, status);

			(void)status;

			if(ZB_TRUE == tunnel_opened)
			{
				ZB_ZCL_TUNNELING_SEND_REQUEST_TUNNEL_RESPONSE(buf_resp, header->addr_data.common_data.source.u, header->addr_data.common_data.source.addr_type == ZB_ZCL_ADDR_TYPE_SHORT ? ZB_APS_ADDR_MODE_16_ENDP_PRESENT : ZB_APS_ADDR_MODE_64_ENDP_PRESENT, TUNNEL_SRV_ENDPOINT, TUNNEL_SRV_ENDPOINT, ZB_AF_HA_PROFILE_ID, ZB_ZCL_DISABLE_DEFAULT_RESPONSE, ZB_ZCL_GET_SEQ_NUM(), NULL, 0x0, ZB_ZCL_TUNNELING_STATUS_NO_MORE_IDS, tunnel_req.max_incoming_transfer_size );
			}
			else
			{
				tunnel_opened = ZB_TRUE;
				ZB_ZCL_TUNNELING_SEND_REQUEST_TUNNEL_RESPONSE(buf_resp_dummy, header->addr_data.common_data.source.u, header->addr_data.common_data.source.addr_type == ZB_ZCL_ADDR_TYPE_SHORT ? ZB_APS_ADDR_MODE_16_ENDP_PRESENT : ZB_APS_ADDR_MODE_64_ENDP_PRESENT, TUNNEL_SRV_ENDPOINT, TUNNEL_SRV_ENDPOINT, ZB_AF_HA_PROFILE_ID, ZB_ZCL_DISABLE_DEFAULT_RESPONSE, ZB_ZCL_GET_SEQ_NUM(), NULL, tunnel_id, ZB_ZCL_TUNNELING_STATUS_NO_MORE_IDS, tunnel_req.max_incoming_transfer_size );
				ZB_ZCL_TUNNELING_SEND_REQUEST_TUNNEL_RESPONSE(buf_resp, header->addr_data.common_data.source.u, header->addr_data.common_data.source.addr_type == ZB_ZCL_ADDR_TYPE_SHORT ? ZB_APS_ADDR_MODE_16_ENDP_PRESENT : ZB_APS_ADDR_MODE_64_ENDP_PRESENT, TUNNEL_SRV_ENDPOINT, TUNNEL_SRV_ENDPOINT, ZB_AF_HA_PROFILE_ID, ZB_ZCL_DISABLE_DEFAULT_RESPONSE, ZB_ZCL_GET_SEQ_NUM(), NULL, tunnel_id, ZB_ZCL_TUNNELING_STATUS_SUCCESS, tunnel_req.max_incoming_transfer_size );
			}

		    return ZB_TRUE;
		}

devzone.nordicsemi.com/.../logs_5F00_ret_5F00_code_5F00_ok.txt

When you try that workaround with two tunnel request responses both with success, then above mentioned trick doesn't do the job.

Thank you for taking care of it. Tunneling is new to me as well.

Cheers!

RE: ZB ZCL Tunneling - no data send

Edvin — Thu, 30 Apr 2020 12:54:15 GMT

Hello,

Can you please attach the sniffer trace when the zb_zcl_tunneling_client_send_transfer_data returns 1?

I have not heard of/used the ZCL tunneling before, so I am not sure how it is supposed to work. When I have the sniffer trace, I can forward this to our Zigbee team.

Best regards,

Edvin