OpenThread
-
|
As shown in the figure below, we found during testing that OTBR's SRP service was registered with an additional IPv6 address, and it is unclear where the IPv6 address came from It seems that this IPv6 address appeared suddenly and was set to WPAN0 Can you help us investigate the reason for this? The SRP service encountered two IPv6 addresses, which was unexpected for us The following is the complete log |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
This is where FD45 first appeared, but I can't see why it appeared |
Beta Was this translation helpful? Give feedback.
-
|
This is an SLAAC address, added because an on-mesh prefix entry was added to the Thread Network Data (with the SLAAC flag enabled). The logs show There's nothing unexpected or out of the ordinary here. If you think this prefix should not appear, you may want to investigate which Border Router on your network added this prefix. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your replay! |
Beta Was this translation helpful? Give feedback.
This is an SLAAC address, added because an on-mesh prefix entry was added to the Thread Network Data (with the SLAAC flag enabled).
The logs show
NetworkData---: Received ServerDataand"State Changed [Netdata]"indicating a Network Data change, which then triggered the SLAAC module to add address based on any new on-mesh prefixes in the Network Data.There's nothing unexpected or out of the ordinary here.
If you think this prefix should not appear, you may want to investigate which Border Router on your network added this prefix.