Lines Matching refs:network

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 …
112 configuring a network stack (compile time). In addition to that a set of API is provided to control…
116 2) Input/Output API (for passing data between IO driver and network stack)
119   * Used for network interface lifecycle management
122 4) Setters and Getters for basic network interface properties
148 For more specific cases please consult this guide: :doc:`/api-reference/network/esp_netif_driver`.
160 Please note that these functions return the ``esp_netif`` handle, i.e. a pointer to a network inter…
163 * The created object has to be destroyed if a network de-initialization is provided by an applicati…