| /hal_espressif-3.6.0/docs/en/api-guides/ |
| D | esp-wifi-mesh.rst | 6 …tocol. Please see the :doc:`ESP-WIFI-MESH API Reference<../api-reference/network/esp-wifi-mesh>` f…
13 … Network). ESP-WIFI-MESH is self-organizing and self-healing meaning the network can be built and …
21 3. :ref:`mesh-building-a-network`
23 4. :ref:`mesh-managing-a-network`
29 7. :ref:`mesh-network-performance`
41 .. figure:: ../../_static/mesh-traditional-network-architecture.png
48 …network is a point-to-multipoint network where a single central node known as the access point (AP…
50 .. figure:: ../../_static/mesh-esp-wifi-mesh-network-architecture.png
57 …network to have much greater coverage area as nodes can still achieve interconnectivity without ne…
77 - Any device that **is** or **can be** part of an ESP-WIFI-MESH network
[all …]
|
| D | wireshark-user-guide.rst | 13 …network packet analyzer that captures network packets and displays the packet data as detailed as …
15 You could think of a network packet analyzer as a measuring device used to examine what is going on…
29 * Network administrators use it to troubleshoot network problems.
35 * People use it to learn more about network protocol internals.
47 * Captures live packet data from a network interface
69 * **Live capture from different network media**.
71 Wireshark can capture traffic from different network media, including wireless LAN.
87 …It will not warn you if there are any suspicious activities on your network. However, if strange t…
89 * **Wireshark does not manipulate processes on the network, it can only perform "measurements" with…
91 …Wireshark does not send packets on the network or influence it in any other way, except for resolv…
|
| D | openthread.rst | 4 …d>`_ is a IP stack running on the 802.15.4 MAC layer which features mesh network and low power con…
65 …ask calls :cpp:func:`nvs_flash_init` to initialize the NVS where the Thread network data is stored.
67 …n task calls :cpp:func:`esp_netif_init` only when it wants to create the network interface for Thr…
75 OpenThread network interface initialization
77 The whole stage is **optional** and only required if the application wants to create the network in…
96 …pp:func:`esp_openthread_netif_glue_deinit` to deintialize the OpenThread network interface if you …
102 The OpenThread border router connects the Thread network with other IP networks. It will provide IP…
|
| /hal_espressif-3.6.0/examples/openthread/ot_br/main/ |
| D | Kconfig.projbuild | 4 string "OpenThread network name"
7 The OpenThread network name for example to use
10 int "OpenThread network channel"
14 The OpenThread network channel to use
17 hex "OpenThread network pan id"
21 The OpenThread network pan id to use
27 The OpenThread network extended pan id in hex string format
33 The OpenThread network master key in hex string format
|
| /hal_espressif-3.6.0/docs/en/api-reference/network/ |
| D | esp_netif.rst | 11 … configure DHCP. Other functions are intended for internal ESP-IDF use by the network driver layer.
13 …ot need to call ESP-NETIF APIs directly as they are called from the default network event handlers.
15 ESP-NETIF component is a successor of the tcpip_adapter, former network interface abstraction, whic…
16 Please refer to the :doc:`/api-reference/network/tcpip_adapter_migration` section in case existing …
59 * ``********`` Events aggregated in ESP-NETIF propagates to driver, user code and network stack
69 …n interaction with a specific IO driver for communication media and configured TCP/IP network stack
87 B) Interaction with network interfaces using ESP-NETIF API
103 …* Installs driver_transmit to appropriate ESP-NETIF object, so that outgoing packets from network …
104 * Calls :cpp:func:`esp_netif_receive()` to pass incoming data to network stack
110 ESP-NETIF is an intermediary between an IO driver and a network stack, connecting packet data path …
[all …]
|
| D | tcpip_adapter_migration.rst | 6 …network interface abstraction component used in IDF prior to v4.1. This page outlines migration fr…
9 Updating network connection code
16 …)`` with ``esp_netif_init()``. Please note that the :doc:`/api-reference/network/esp_netif` initia…
30 Network interface instance shall be explicitly constructed for the :doc:`/api-reference/network/esp…
80 Additional step in porting an application to fully benefit from the :doc:`/api-reference/network/es…
|
| D | esp-wifi-mesh.rst | 58 …can be used to indicate when the root node can and cannot transmit data to the external IP network.
66 …equired by the root node to transmit/receive data to/from an external IP network. However, since e…
89 …er nodes to begin transmitting/receiving packets to/from the external IP network. However, this st…
123 After initializing LwIP and Wi-Fi, the process of getting an ESP-WIFI-MESH network up and running c…
209 …connected to the network. After connecting, the application can start transmitting and receiving p…
219 …network to operate with high degree of autonomy by making the network robust to dynamic network to…
221 …election of the root node (see **Automatic Root Node Selection** in :ref:`mesh-building-a-network`)
222 …ection of a preferred parent node (see **Parent Node Selection** in :ref:`mesh-building-a-network`)
223 …ecting a disconnection (see **Intermediate Parent Node Failure** in :ref:`mesh-managing-a-network`)
331 …ates how to set up a ESP-WIFI-MESH network and have the root node send a data packet to every node…
|
| D | esp_netif_driver.rst | 6 …ons, post-attach callback and in most cases also default event handlers to define network interface
29 A final part of the network interface initialization consists of attaching the esp-netif instance t…
76 I/O drivers also typically provide default definitions of lifecycle behaviour of related network in…
77 on state transitions of I/O drivers. For example *driver start* ``->`` *network start*, etc.
94 …ly from its TCP/IP stack connecting layer. The following API reference outlines these network stack
|
| D | index.rst | 60 The TCP/IP Adapter (legacy network interface library) has been deprecated, please consult the :doc:…
66 Documentation for Application layer network protocols (above the IP Network layer) are provided in …
|
| /hal_espressif-3.6.0/examples/mesh/internal_communication/main/ |
| D | Kconfig.projbuild | 58 int "Mesh PS network duty cycle"
63 Mesh PS network duty cycle.
66 int "Mesh PS network duty cycle duration (unit: minutes)"
71 Mesh PS network duty cycle duration.
74 bool "Mesh PS network duty cycle rule"
78 Mesh PS network duty cycle rule.
92 Mesh PS network duty cycle rule.
100 Max layer allowed in mesh network.
107 mesh network channel.
171 The number of devices over the network(max: 300).
|
| /hal_espressif-3.6.0/examples/network/network_tests/ |
| D | README.md | 1 # Intel net test suite for LwIP network stack
3 This project provides a test interface to esp32 network stack in order to execute standard set of
4 Intel network test suite defined in TTCN3 framework.
11 These network tests could be executed in both manual or automated mode in CI.
44 Purpose of this test is to execute standard network suite on a ESP32 network stack.
47 and from the network stack. Embedded code `net_suite.c` implements an application which serves stdi…
49 Standard Intel net suite executed by TTCN3 engine uses udp ports for input/ouput of network packets…
50 … after propagating over USB/UART to the ESP32 board are processed in the network stack (on the tar…
|
| /hal_espressif-3.6.0/components/esp_netif/ |
| D | README.md | 35 Overall application interaction with communication media and network stack
41 2) network stack options (netif init and input functions, not publicly available)
47 - interact with network interfaces using ESP-NETIF API
54 network stack are passed to the IO driver
55 - calls esp_netif_receive to pass incoming data to network stack
59 * IO API: for passing data between IO driver and network stack
63 * network stack abstraction: enabling user interaction with TCP/IP stack
78 * `********` Events agregated in ESP-NETIP propagates to driver, user code and network stack
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_console/ |
| D | ble_mesh_commands_README.md | 18 * `-n`: `<network index>:network index`
59 * `-z`: `<action type>:add app key or network key`
60 * `-n`: `<net key index>:network key index`
61 * `-k`: `<key>:appkey or network`
71 * `-n`: `<network>:net work index`
86 * `-n`: `<netkey index>:network key index`
113 * `bmnnwk`: An unprovisioned device enters the mesh network and becomes a node without the provisio…
114 * `-k`: `<net key>:network key`
115 * `-n`: `<net index>:network key index`
124 …ce's information into the mesh database while unprovisioned device enter mesh network automatically
[all …]
|
| /hal_espressif-3.6.0/docs/ |
| D | page_redirects.txt | 14 api-reference/ethernet/index api-reference/network/index
15 api-reference/ethernet/esp_eth api-reference/network/esp_eth
16 api-reference/mesh/index api-reference/network/index
17 api-reference/mesh/esp_mesh api-reference/network/esp_mesh
20 api-reference/wifi/index api-reference/network/index
21 api-reference/wifi/esp_now api-reference/network/esp_now
22 api-reference/wifi/esp_smartconfig api-reference/network/esp_smartconfig
23 api-reference/wifi/esp_wifi api-reference/network/esp_wifi
24 api-reference/system/tcpip_adapter api-reference/network/esp_netif
61 api-reference/network/tcpip_adapter api-reference/network/esp_netif
[all …]
|
| /hal_espressif-3.6.0/docs/en/api-guides/esp-ble-mesh/ |
| D | ble-mesh-terminology.rst | 16 - A device that is not a member of a mesh network is known as an unprovisioned device.
20 …network. Nodes (such as lighting devices, temperature control devices, manufacturing equipments, a…
26 …network. Generally, mobile apps need a Proxy node to access Mesh network. Without Proxy nodes, mob…
34 - A node that is capable of adding a device to a mesh network.
49 …- Each node in a ESP-BLE-MESH network has an independent set of state values that indicate certain…
71 …- The ability to operate within a mesh network at significantly reduced receiver duty cycles only …
78 …direct radio transmission between two nodes, thereby covering the entire network. When a node is e…
81 … to allow nodes without an advertising bearer to access the ESP-BLE-MESH network. The proxy featur…
98 …vices which don't implement such service cannot be provisioned into mesh network through PB-GATT b…
100 …- Provisioning is a process of adding an unprovisioned device to a mesh network, managed by a Prov…
[all …]
|
| /hal_espressif-3.6.0/docs/zh_CN/api-guides/esp-ble-mesh/ |
| D | ble-mesh-terminology.rst | 16 - "A device that is not a member of a mesh network is known as an unprovisioned device."
34 - "A node that is capable of adding a device to a mesh network."
71 …- "The ability to operate within a mesh network at significantly reduced receiver duty cycles only…
100 …- "Provisioning is a process of adding an unprovisioned device to a mesh network, managed by a Pro…
158 …network key (NetKey) and can be used by other nodes in the same network. Messages encrypted with m…
172 …- "Segmentation and reassembly (SAR) is a method of communication network, which is divided into s…
188 - "This model is used to represent a mesh network configuration of a device."
194 - "This model is used to represent a mesh network diagnostics of a device."
201 .. _ble-mesh-terminology-network-management:
211 …- "This procedure is used when the security of one or more network keys and/or one or more of the …
[all …]
|
| /hal_espressif-3.6.0/examples/mesh/ip_internal_network/main/ |
| D | Kconfig.projbuild | 8 mesh network channel.
72 Max layer allowed in mesh network.
79 The number of devices over the network(max: 300).
95 for internal IP subnet formed by the mesh network
97 Note: The IP address is in platform (not network)
|
| /hal_espressif-3.6.0/examples/mesh/internal_communication/ |
| D | README.md | 3 …rates how to use the mesh APIs to set up a mesh network, send and receive messages over the mesh n…
19 Open project configuration menu (`idf.py menuconfig`) to configure the mesh network channel, router…
21 When the mesh network is established and if you happen to run this example on ESP-WROVER-KIT boards…
|
| /hal_espressif-3.6.0/docs/zh_CN/api-reference/network/ |
| D | tcpip_adapter_migration.rst | 6 TCP/IP 适配器是在 IDF V4.1之前使用的网络接口抽象组件。本文档概述了从 tcpip_adapter 移出至其后继者 :doc:`/api-reference/network/esp_n…
16 只需将 ``tcpip_adapter_init()`` 替换为 ``esp_netif_init()``。请注意，:doc:`/api-reference/network/esp_netif` 初…
30 网络接口的设计应严格参考 :doc:`/api-reference/network/esp_netif`，以使其能够连接到 TCP/IP 软件栈。
81 为了移植应用程序使其可以使用 :doc:`/api-reference/network/esp_netif` 还需完成的步骤包括：在组件配置中禁用 tcpip_adapter 兼容层。
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_coex_test/main/ |
| D | Kconfig.projbuild | 24 SSID (network name) for the example to connect to. The length cannot exceed 20 bytes.
30 Can be left blank if the network has no security set.
61 SSID (network name) for the example to connect to. The length cannot exceed 20 bytes.
67 Can be left blank if the network has no security set.
|
| /hal_espressif-3.6.0/docs/zh_CN/api-guides/ |
| D | esp-wifi-mesh.rst | 6 本指南提供有关 ESP-WIFI-MESH 协议的介绍。更多有关 API 使用的信息，请见 :doc:`ESP-WIFI-MESH API 参考 <../api-reference/network/…
21 3. :ref:`mesh-building-a-network`
23 4. :ref:`mesh-managing-a-network`
29 7. :ref:`mesh-network-performance`
41 .. figure:: ../../_static/mesh-traditional-network-architecture.png
50 .. figure:: ../../_static/mesh-esp-wifi-mesh-network-architecture.png
217 .. _mesh-building-a-network:
230 .. figure:: ../../_static/mesh-network-building.png
357 .. _mesh-managing-a-network:
707 .. _mesh-network-performance:
|
| /hal_espressif-3.6.0/components/openthread/ |
| D | Kconfig | 38 … Select this to enable Full Thread Device which can act as router and leader in a Thread network.
43 … Select this to enable Minimal Thread Device which can only act as end device in a Thread network.
69 …commissioner in the Thread network. A commissioner checks the pre-shared key from a joining device…
70 …the Thread commissioning protocol and shares the network parameter with the joining device upon su…
77 … this option to enable Joiner in OpenThread. This allows a device to join the Thread network with a
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_fast_provision/fast_prov_server/tutorial/ |
| D | EspBleMesh.md | 3 This demo demonstrates the fast provisioning of ESP BLE Mesh network and how to use the EspBleMesh …
16 …ng of the performance of the BLE Mesh network, we recommend that at least 3 devices should be adde…
45 …eMesh` app, and follow the steps described below to establish a BLE Mesh network and control any i…
51 4. Enter the number of devices you want to add in your mesh network;
77 1. The Top Provisioner configures the first device to access the network with the GATT bearer.
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_fast_provision/fast_prov_client/tutorial/ |
| D | BLE_Mesh_Fast_Prov_Client_Example_Walkthrough.md | 9 4. Getting the addresses of all the nodes in the fast provisioning network.
18 - The **Configuration Server** model is used to represent a mesh network configuration of a device.
31 …ess range can be assigned by a node, and the maximum number of nodes supported by the mesh network.
37 | `app_key[16]` | Appkey, which is used throughout the network |
38 | `node_addr_cnt`| The maximum number of nodes supported in the mesh network，which serves the same …
39 | `unicast_min` | Minimum unicast address to be assigned to the nodes in the mesh network |
40 | `unicast_max` | Maximum unicast address to be assigned to the nodes in the mesh network |
41 …ress, which is used to control the on/off state of all nodes in the mesh network, that is said, tu…
191 …ut, the provisioner starts to get the addresses of all nodes in the mesh network by calling the `e…
|
| /hal_espressif-3.6.0/examples/ |
| D | README.md | 15 * `ethernet` Ethernet network examples.
18 * `network` Examples related to general network environment, test & analysis.
21 * `protocols` Examples showing network protocol interactions.
26 * `wifi` Advanced Wi-Fi features (For network protocol examples, see `protocols` instead.)
|
