Symbols ![]()
loading...
Files ![]()
loading...
SourceVu![]()
ESP-IDF Framework and Examples![]()
ESP-IDF![]()
ot::NetworkData::Leader::GetPreferredNat64Prefix() const
ot::NetworkData::Leader::GetPreferredNat64Prefix() const method
Gets the preferred NAT64 prefix from network data. The returned prefix is the highest preference external route entry in Network Data with NAT64 flag set. If there are multiple such entries the first one is returned.
Syntax
Implemented in ![]()
network_data_leader.cpp:96
Return value
kErrorNone Found the NAT64 prefix and updated @p aConfig. kErrorNotFound Could not find any NAT64 entry.
Related Functions
Found 5 other functions taking a ![]()
ExternalRouteConfig
argument:
Function
Description
Provides the next external route in the Thread Network Data.
Replaces a previously published external route. Only stable entries can be published (i.e.,`aConfig.mStable` MUST be `true`). If there is no previously published external route matching @p aPrefix, this method behaves similarly to `PublishExternalRoute()`, i.e., it will start the process of publishing @a aConfig as an external route in the Thread Network Data. If there is a previously published route entry matching @p aPrefix, it will be replaced with the new prefix from @p aConfig. - If the @p aPrefix was already added in the Network Data, the change to the new prefix in @p aConfig is immediately reflected in the Network Data. This ensures that route entries in the Network Data are not abruptly removed and the transition from aPrefix to the new prefix is smooth. - If the old published @p aPrefix was not added in the Network Data, it will be replaced with the new @p aConfig prefix but it will not be immediately added. Instead, it will start the process of publishing it in the Network Data (monitoring the Network Data to determine when/if to add the prefix, depending on the number of similar prefixes present in the Network Data).
Indicates whether or not the Thread Network Data contains a given external route entry.
Requests an external route prefix to be published in the Thread Network Data. Only stable entries can be published (i.e.,`aConfig.mStable` MUST be `true`). A subsequent call to this method will replace a previous request for the same prefix. In particular if the new call only changes the flags (e.g., preference level) and the prefix is already added in the Network Data, the change to flags is immediately reflected in the Network Data. This ensures that existing entries in the Network Data are not abruptly removed. Note that a change in the preference level can potentially later cause the entry to be removed from the Network Data after determining there are other nodes that are publishing the same prefix with the same or higher preference.
Adds a Has Route entry to the Thread Network data.