OpenThread IPv6 TTL

RE: OpenThread IPv6 TTL

Rouben — Sun, 12 Jul 2020 10:22:46 GMT

I'm sorry for the question. I opened an new case fot that: https://devzone.nordicsemi.com/f/nordic-q-a/63670/openthread-coap-multicast-message-id

RE: OpenThread IPv6 TTL

Rouben — Thu, 09 Jul 2020 09:09:01 GMT

Hi Jørgen,

that works perfectly with the otMessageInfo structure, thank you. I found an other mistake, I have made. I subscribed and sent the CoAP message to a Link-Local IPv6 address (ff02::4). I changed that and I can know read out the number of hops the message has taken.

I have another question to you. I read out the message ID from the CoAP message ( otCoapMessageGetMessageId(p_request) ). If I send the message to the Link-Local IPv6 (ff02::4) address the ID was valid. But if I send it to a Mesh-Local address (ff03::4) the ID is always 0. Is it possible to get the message ID with the Mesh-Local address?

Thank you very much.

Best regards,

Rouben

RE: OpenThread IPv6 TTL

Jørgen Holmefjord — Tue, 07 Jul 2020 14:03:11 GMT

Hi,

The otMessageInfo structure has a mHopLimit member. This is decremented by each router that forwards the message. By default, this is set to OPENTHREAD_CONFIG_IP6_HOP_LIMIT_DEFAULT.

Note that Thread has a maximum path cost of 16. The path cost for a single hos may be between 1 and 4 depending on the link quality. Thread uses proactive routing calculation, you can get the path cost to another router from otThreadGetRouterInfo::mPathCost (have a look at the CLI source code on how this is implemented).

If you search the Thread specifications for "hop count", you will find more details on how hop count works.

Best regards,
Jørgen