Home
last modified time | relevance | path

Searched refs:client (Results 176 – 200 of 326) sorted by relevance

12345678910>>...14

/Zephyr-latest/doc/connectivity/networking/
Darmfvp_user_networking_setup.rst35 DHCPv4 client sample.
36 See :zephyr:code-sample:`dhcpv4-client` sample application.
/Zephyr-latest/samples/net/cloud/aws_iot_mqtt/
DREADME.rst10 This sample application demonstrates the implementation of an MQTT client that
50 with the certificate it will be used as the client id. We will use
66 MQTT test client
69 Access the MQTT test client in the AWS IoT Core console, subscribe to the
/Zephyr-latest/subsys/modbus/
Dmodbus_core.c92 if (ctx->client == true) { in modbus_rx_handler()
247 ctx->client = false; in modbus_init_server()
336 ctx->client = true; in modbus_init_client()
Dmodbus_internal.h104 bool client; member
/Zephyr-latest/samples/net/sockets/echo_client/
DCMakeLists.txt21 target_sources( app PRIVATE src/echo-client.c)
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.vcp82 enabled for VCS client.
97 enabled for VCS client.
DKconfig.mcs37 control client will truncate the name when reading it.
46 client will truncate the name when reading it.
55 the media control client will truncate the title when reading it.
64 longer, the media control client will truncate the name when reading
DKconfig.vocs38 int "Volume Offset Control Service client max instance count"
DKconfig.aics40 int "Audio Input Control Service client max instance count"
/Zephyr-latest/doc/connectivity/networking/api/
Dthread.rst38 You can try using OpenThread with the Zephyr Echo server and Echo client samples,
41 See :zephyr:code-sample:`sockets-echo-server` and :zephyr:code-sample:`sockets-echo-client`
Dsocks5.rst49 For MQTT client, there is :c:func:`mqtt_client_set_proxy()` API that the
/Zephyr-latest/samples/net/sockets/echo/
DREADME.rst45 sockets, and thus can serve only one client connection at time. After the
46 current client disconnects, the next connection can proceed.
/Zephyr-latest/samples/net/sockets/socketpair/
DREADME.rst37 After the sample starts, several client threads are spawned. Each client
/Zephyr-latest/subsys/mgmt/mcumgr/transport/
DKconfig.dummy27 line sent by an mcumgr client.
/Zephyr-latest/tests/bsim/bluetooth/host/att/read_fill_buf/client/
Dmain.c21 LOG_MODULE_REGISTER(client, LOG_LEVEL_DBG);
/Zephyr-latest/doc/security/
Dsensor-threat.rst70 4. **Client secrets**. To authenticate the client to the service, the
71 client must possess some kind of secret. This is generally a private
80 periodically, which will require a way to update the client secret.
90 Also, token based client authentication will generally require the
91 client to sign a message containing a time window that the token is
127 b. **Client secret changes**. Changes and new client secrets should be
176 client secrets. This area is written and read by a subset of the
246 c. **Client authentication**. The client shall authenticate itself to
250 [th-tls-client-auth]_.
252 i. **TLS client certificates**. The TLS protocol allows the
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dhealth_cli.rst10 their first parameter. This is a pointer to the client model instance to be
/Zephyr-latest/doc/connectivity/bluetooth/autopts/
Dautopts-win10.rst6 This tutorial shows how to setup AutoPTS client and server to run both on
181 Server and client by default will run on localhost address. Run server:
201 Run client:
224 This is a problem with connection between auto-pts client and board. There are many possible causes…
/Zephyr-latest/subsys/net/l2/wifi/
DKconfig101 Station inactivity timeout is the period for which AP may keep a client
103 client. If a non-zero value is set, AP may choose to disassociate the
104 client after the timeout.
/Zephyr-latest/samples/bluetooth/mtu_update/
DREADME.rst35 To be able to send a large notification both the server and the client need to
36 update their MTU. The MTU is not a negotiated value, the client and the server
39 to the MTU of the client.
/Zephyr-latest/modules/thrift/src/thrift/transport/
DTServerSocket.h145 virtual std::shared_ptr<TSocket> createSocket(THRIFT_SOCKET client);
/Zephyr-latest/tests/bsim/net/sockets/echo_test/
DCMakeLists.txt29 target_sources( app PRIVATE ${echo_client_path}/src/echo-client.c)
/Zephyr-latest/samples/net/sockets/coap_download/
DREADME.rst5 Use the CoAP client API to download data via a GET request
10 This sample demonstrates the use of the CoAP client API to make GET requests to
/Zephyr-latest/samples/net/cloud/mqtt_azure/
DKconfig19 string "Azure cloud IoT hub MQTT client ID"
/Zephyr-latest/doc/hardware/peripherals/
Dregulators.rst17 client. For those situations the cost of using the regulator device

12345678910>>...14