Lines Matching refs:ifaces

19 …r_monitoring.h`) monitors all available :ref:`Zephyr network interfaces (ifaces) <net_if_interface…
38 Connectivity monitoring tracks all available ifaces (whether or not they support :ref:`Connectivity…
59   * Ignored ifaces are always treated as unready.
72 Afterwards, ifaces can become ready or unready without firing additional events, so long as there a…
74 When there are no longer any ready ifaces left, the :c:macro:`NET_EVENT_L4_DISCONNECTED` :ref:`netw…
85 …NET_EVENT_L4_DISCONNECTED`, but specifically track whether IPv4- and IPv6-capable ifaces are ready.
178 Ignoring ifaces
181 Applications can request that ifaces be ignored by Connection Manager by calling :c:func:`conn_mgr_…
185 This has the effect of individually ignoring all the ifaces using that :ref:`L2 implementation <net…
189 This may be useful, for instance, if your application has configured one or more ifaces that cannot…
191 :ref:`Bulk convenience functions <conn_mgr_control_api_bulk>` optionally skip ignored ifaces.
211 For such ifaces, connectivity control can provide a generic API to request network association (:c:…
219 …k>` for controlling the admin state and network association of all available ifaces simultaneously.
290 These features describe how ifaces should behave during connect and disconnect events.
417 …In Zephyr, ifaces are automatically taken admin-up (see :ref:`net_if_interface_state_management` f…
435 … this for all ifaces by disabling the :kconfig:option:`CONFIG_NET_CONNECTION_MANAGER_AUTO_IF_DOWN`…
451 Connectivity control provides several bulk functions allowing all ifaces to be controlled at once.
453 …ions to operate only on non-:ref:`ignored <conn_mgr_monitoring_ignoring_ifaces>` ifaces if desired.