Trust Link Key in ZigBee pro

Zigbee pro

So you meant that if i change the secure link key array of 16 bytes in both coordinator and router(nodes)

And in compile option enable tc link key as true??

But I have a doubt on this
According to z stack developers guide

"""If it is set to TRUE, then the value of default key must be preconfigured on each device (to the exact same value). If it is set to FALSE, then the default key parameter needs to be set only on the coordinator device. Note that in the latter case, the key will be distributed to each joining device over-air. So there is a “moment of vulnerability” during the joining process during which an adversary can determine the key by listening to the on-air traffic and compromise the network security
"""

that's why i have kept is as true

and also in my case i have set up two coordinators and one node

each coordinator have different TCL_KEY and i have made two node code with key matching as per the firmware, in this case some times it is working  ( node getting announced only to matched key coordinator ) but some times it is not working and node is restarting itself 

what is your suggestion on this ?

So you meant to say that

I will disable the tclinkkey from compile option for both coordinator and nodes

And i can customize/change the key mentioned in the macro of nwk_globals.h for both coordinator and node

To establish a close network like one particular node gets announced only to matched macro value of coordinator(macro value used in coord'snwk_globals. h)?

No it was not resetting

I had connected led to view this

And yes no communication will happen that i have checked

But one more question come to my mind

When i used AF DATA REQUEST

It was not giving me fail response either like

0xE9

0xe1

0xCD

although no data got recieved through that unauthorized node

Here is the ubiqua Packet analyzer log

case

Coordintaor key

-DDEFAULT_KEY="{0x01, 0x03, 0x05, 0x07, 0x09, 0x0B, 0x0D, 0x0F, 0x00, 0x02, 0x04, 0x06, 0x08, 0x0A, 0x0E, 0x0F}"

Node Key

-DDEFAULT_KEY="{0x01, 0x03, 0x05, 0x07, 0x09, 0x0B, 0x0D, 0x0F, 0x00, 0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0D}"

SOC on ZNP means ?

How to attach the ubiqua packet analyzer log file as it is not uploading ( problem with file format )

I am using znp stack on cc2530 and for application  I am using Z tools

CC2530 is connected to MY PC using Serial To USB Converter

The problem when the node device is unauthenticated it should Restart or reboot ( watchdog reset )  or some thing similar it should start RE searching for new network ( correct me if I am missing some thing ) 

Key_mismatched_log.zip

In ZDApp_ProcessNetworkJoin, it will create a ZDO_DEVICE_RESET event by calling "ZDApp_ResetTimerStart( MAX_DEVICE_UNAUTH_TIMEOUT );". If the NWK is not delivered or TC_LINK_KEY isn't matched, it would go to the red part of the following code in ZDApp_event_loop and I suppose you can do your process there.

if ( events & ZDO_DEVICE_RESET )
{
#ifdef ZBA_FALLBACK_NWKKEY
if ( devState == DEV_END_DEVICE_UNAUTH )
{
ZDSecMgrFallbackNwkKey();
}
else
#endif
{
// Set the NV startup option to force a "new" join.
zgWriteStartupOptions( ZG_STARTUP_SET, ZCD_STARTOPT_DEFAULT_NETWORK_STATE );

// The device has been in the UNAUTH state, so reset
// Note: there will be no return from this call
SystemResetSoft();
}
}

I have checked by changing the default key value in the node
Although as expected Device announce has not happened in the coordinator
but the PC didn't reach in the event,
if ( events & ZDO_DEVICE_RESET )

are you saying that I have to use TC_LINK_KEY instead of default key

and try to this by changing the  tc_link_key value in "nwk_globals.h"  in node
and check

As right now TC_LINKKEY_JOIN preprocessor is disabled in my code 

Please correct me if i am wrong ?

Yes that i have verified