Lines Matching refs:node
188 local messages. When Friend feature is enabled and the node is
192 consumption of the Low Power node.
207 extended advertising set makes the Friend node send friendship
209 thus reducing the scanning time on the Low Power node.
221 This should be chosen based on the number of local messages that the node
434 Number of messages that are cached by the node to avoid acting on the
555 models the local node supports, i.e. what's the largest
556 message payload that the node needs to be able to receive.
577 models the local node supports, i.e. what's the largest
578 message payload that the node needs to be able to send.
731 Note that: To ensure sufficient space in CRPL for normal node
733 requirements, when subnet bridge functionality is enabled on a node,
925 is instantiated on a Low Power node, the pull request count will be
972 and the maximum SDU a node can receive.
1000 and the maximum SDU a node can receive.
1135 int "Maximum Target node count"
1158 communicates directly with the unprovisioned node.
1165 node, and allows provisioning of new devices through the mesh network
1302 advertising with Private Network Identity type of a node.
1322 protection list (SRPL) of a node that supports the Solicitation
1339 of the subnet bridge functionality of a node.
1357 node that can configure the subnet bridge functionality of another node.
1400 This option determines for how long the local node advertises
1418 node supports. This helps in reducing unwanted traffic getting sent to
1421 this proxy server node using the default accept list filter type.
1569 In order to fulfill the above requirement, even if the node might
1571 how many hours the node has been in the state. This doesn't
1574 ways that the node will be used and what kind of power source it
1580 duration that the node has been in the current state gets
1599 is that the node may miss out on messages intended for it
1601 node.
1617 Time in seconds from the last received message, that the node
1633 The contribution of the RSSI measured by the Friend node used
1651 the Friend node can store in its Friend Queue. As an example,
1655 int "Receive delay requested by the local node"
1660 The ReceiveDelay is the time between the Low Power node
1662 allows the Friend node time to prepare the response. The value
1673 consecutive requests sent by the Low Power node. If no
1674 requests are received by the Friend node before the
1734 Receive Window in milliseconds supported by the Friend node.
1750 Friend node for a Low Power node.
1847 100th increment. If the node sends messages very frequently a
1848 higher value makes more sense, whereas if the node sends
1864 to a large number may lead to security vulnerabilities if a node