This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2531: Coordinator not allow new connections after 10 attempts

Part Number: CC2531
Other Parts Discussed in Thread: Z-STACK

Hi,

I'm trying to connect a router to a coordinator using security.

Currently I'm failing because the authentication is not being done correctly. This leads me to another issue that I would like to solve.

When coordinator sends a LeaveReq (because auth failed), router will try to join the network again. After 10 tries, coordinator starts sending association flag as 0.

Even for other devices (other mac address) it replies association as 0. If I reset the coordinator, it allows again the association.

I believe that it exhausted its connection association.

So, my question is if It's possible to refresh or remove the associations limits?

I'm using Z-Stack 3.0.

  • Hi,

    Are you rebroadcasting mgmt permit join periodically? In z-stack 3.0, the maximum time that the network can be open for joining is 180 seconds, so if you would like to leave the network open longer you must periodically rebroadcast the mgmt permit join message. You can do this by simply calling the BDB commissioning API with network steering modes enabled, for routing devices already on a network calling this API will rebroadcast this message, i.e:

    bdb_StartCommissioning(BDB_COMMISSIONING_MODE_NWK_STEERING);
  • Hi,

    Thank you for the quick reply.
    No, I'm not rebroadcasting. I will try that.

    By the way, 180 seconds is the default value or the stack has other timeout value? Where can I check this? There is some variable with this value?
  • It is controlled by BDBC_MIN_COMMISSIONING_TIME in bdb_interface.h. Also, I misspoke before, the maximum time this can be is (uint8 max - 1) (254 seconds), part of the ZigBee 3.0 specification says you may no longer keep the network open indefinitely via a single mgmt permit join request, the mgmt permit join must be rebroadcast periodically if you want this behavior. This change was for security purposes, it is generally a bad idea to keep permit join open forever in a network.
  • Hi Jason,

    Rebroadcasting mgmt permit join solved the issue.
    Thank you very much.

    BR,
    Igor