Lines Matching refs:will
116 mesh-specific workqueue. This will ensure that messages are always sent.
134 will be affected by other users on the system work queue, resulting in
183 messages, the stack will use the main advertising set to relay
191 value. This in turn will result in increase of the power
199 otherwise a shared advertising set will be used.
206 otherwise a shared advertising set will be used. Using the separate
513 feature of specification, set to zero will not allow send any
525 feature of specification, set to zero will not allow receive any
539 Outgoing messages will allocate their segments at the start of the
613 segmented message to a unicast address that the stack will send if no
666 will additionally retransmit every acknowledgment message the
705 acknowledgment message that the stack will additionally send when the
746 enabled this choice will provide a non-persistent implementation
768 will update the replay protection cache for messages those cannot be handled
925 is instantiated on a Low Power node, the pull request count will be
941 size will be some number that is a power of two, and is between block
943 time warning will be issued.
951 size will be some number that is a power of two, and is between block
953 time warning will be issued.
970 possible and will be clamped to the max possible if set above.
987 Controls the number of times the client will attempt to resend missing
998 possible and will be clamped to the max possible if set above.
1283 of On-Demand Private Proxy Servers. The state determines if the peers will
1450 How many times Solicitation PDU advertisements will be repeated. 0 means that there will be
1573 duration range). The exact cadence will depend a lot on the
1574 ways that the node will be used and what kind of power source it
1618 will wait before starting to look for Friend nodes.
1686 will gradually grow toward the actual PollTimeout, doubling
1846 means that the sequence number will be stored to flash on every
1851 will add this number to the last stored one, so that it starts
1869 may make sense. Setting this value to -1 will disable this timer.
1872 IV Index is updated, the outdated RPL entries will still be
1877 will cause the device to not perform the replay protection
1889 means that the system workqueue will be blocked for the time needed