Home
last modified time | relevance | path

Searched refs:peers (Results 1 – 7 of 7) sorted by relevance

/openthread-latest/tests/toranj/cli/
Dtest-503-peer-tbr-discovery.py115 peers = br.br_get_peer_brs() variable
116 verify(len(peers) == 2)
121 verify(any([rloc16 in peer for peer in peers]))
/openthread-latest/src/cli/
DREADME_BR.md16 - [peers](#peers)
39 peers
226 ### peers subsection
228 Usage: `br peers`
248 > br peers
254 Usage: `br peers count`
DREADME.md3933 ### trel peers [list]
3938 > trel peers
3945 > trel peers list
/openthread-latest/third_party/mbedtls/repo/tests/suites/
Dtest_suite_psa_crypto_pake.function1146 const char *peers[] = { "client", "server", "other" };
1161 for (size_t i = 0; i < ARRAY_LENGTH(peers); i++) {
1162 uint8_t *peer = (uint8_t *) peers[i];
1163 uint8_t peer_len = strlen(peers[i]);
/openthread-latest/third_party/mbedtls/repo/tests/
Dcompat.sh172 -p|--peers)
/openthread-latest/third_party/mbedtls/repo/docs/
D3.0-migration-guide.md662 and relied on that version in order to communicate with peers that are not up
663 to date. If one of your peers is in that case, please try contacting them and
/openthread-latest/third_party/mbedtls/repo/
DChangeLog802 If you need to communicate with peers that use earlier versions of
804 to 1, but then you won't be able to communicate with peers that use the
806 If you need to interoperate with both classes of peers with the
4185 with some peers over unreliable links. Avoid dropping an entire DTLS