
This report concerns a behavior seen using the "Zigbee_3_0_Linux_Gateway_1_0_1" package.

The log files are included:
  - These files can be opened all together in wireshark:
	- 20200701_JoinAgain2Incomplete.pcapng.gz - Zigbee capture;
	- zigbeegw_log.pcap - Zigbee gateway log converted to SYSLOG entries and slightly time shifted to match the capture.
	- zigbeeapp_log.pcap - Application log converted to SYSLOG entries and slightly shifted.
  - zigbeegw.log, zigbeeapp.log: Textual gateway log and application log, with timestamps.


Unexplained behavior.

At 20:05:56,559501, an association sequence "finishes"
  (filter: wpan.dst64==0xD6F0011618652||wpan.src64==0xD6F0011618652 || wpan.dst16 == 0x15e4 || wpan.src16==0x15e4 )

IMHO this association is not reported by the gateway - the device does not show up in the device list.  No further data is exchanged.
- 3106	20:05:56,559501	0x0000	0x15e4	ZigBee	73	Transport Key

The gateway reports are not mentioning anything about this either.

The device joined the network on an earlier occasion.  It notified that it was leaving the previous network and then "joined" the coordinator.  However, the behavior was the same.
- Log file: 20200701_JoinIncomplete.pcapng.gz .
  (The text logs were not properly time synced).


Any suggestion ?  Is this a misbehavior of the Zigbee device or should the gateway be improved?

Where can I find an "bin" file for the CC2530 to use the latest ZNP firmware for this device?


Further information:

This setup is Zigbee_3_0_Linux_Gateway_1_0_1 package, except for firmware on CC2530 for which no "bin" image seems to be available to do an upgrade using SBL.
The demo application has been adapted, the gateway servers are compiled from the original source code.

The following CC2530 firmware is used:
	  Transport Protocol Version: 2
	  Product ID: 0
	  Software Release: 2.7.1
	  Software Revision: 0
	  (Revision not specified)
