This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

problem with cli example in thred sdk... i cannot ping the same ip addresse continously it keeps on chaging for device which is in the router role

I have programmed two boards(pca10056) with the cli example in thread sdk.I have set the first one as the leader and the second as the child but after pinging the kit the ip addresse of the child changes along with the state (the state changes to router form child) and i cannot ping on the same ip i need to select another ip addresse, why does this happen?does the board change its ip address after few seconds

Parents
  • Hi,

    Is your child promoting itself to a router after some time? In which case you use bad address (RLOC) which indicates the role in the network

    You should use ML-EID address. There was also one small bug in Thread stack which is fixed on master. The side affect of the bug is that when the node changes its role (for examples promotes itself to a router) then the RLOC address will be updated and the older one is not valid anymore. So the first ping to target ML-EID address would not do anything on CLI (internally it will update the cache with the new RLOC address), but the second ping should work fine.

Reply
  • Hi,

    Is your child promoting itself to a router after some time? In which case you use bad address (RLOC) which indicates the role in the network

    You should use ML-EID address. There was also one small bug in Thread stack which is fixed on master. The side affect of the bug is that when the node changes its role (for examples promotes itself to a router) then the RLOC address will be updated and the older one is not valid anymore. So the first ping to target ML-EID address would not do anything on CLI (internally it will update the cache with the new RLOC address), but the second ping should work fine.

Children
No Data
Related