Searched full:network (Results 1 – 25 of 939) sorted by relevance
12345678910>>...38
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 3 Network Stack Architecture
12 The Zephyr network stack is a native network stack specifically designed
14 to other layers. Network stack functionality is highly configurable via Kconfig
21 High level overview of the network stack
25 :alt: Overview of the network stack architecture
28 Network stack overview
30 The network stack is layered and consists of the following parts:
32 * **Network Application.** The network application can either use the provided
34 :ref:`BSD socket API <bsd_sockets_interface>` directly to create a network
36 also use the :ref:`network management API <net_mgmt_interface>` to configure
[all …]
|
| D | net_pkt_processing_stats.rst | 3 Network Packet Processing Statistics
10 This page describes how to get information about network packet processing
11 statistics inside network stack.
13 Network stack contains infrastructure to figure out how long the network packet
18 network packet statistics is collected. For RX, only UDP, TCP or raw packet
19 type network packet statistics is collected.
21 After enabling these options, the :ref:`net stats <net_shell>` network shell
33 The TX time tells how long it took for network packet from its creation to
34 when it was sent to the network. The RX time tells the time from its creation
42 information for TX or RX network packets are collected when the network packet
[all …]
|
| D | net_config_guide.rst | 3 Network Configuration Guide
10 This document describes how various network configuration options can be
13 Network Buffer Configuration Options
16 The network buffer configuration options control how much data we
20 Maximum amount of network packets we can receive at the same time.
23 Maximum amount of network packet sends pending at the same time.
26 How many network buffers are allocated for receiving data.
34 can be the amount of data we have received from the network.
35 When data is received from the network, it is placed into net_buf data portion.
36 Depending on device resources and desired network usage, user can tweak
[all …]
|
| /Zephyr-latest/subsys/net/lib/capture/ |
| D | Kconfig | 1 # Capture network packets
7 bool "Network packet capture support"
15 This option allows user to capture network packets.
17 User can use network packet analyzer like Wireshark to
19 The captured network packets are sent using IPIP tunnel
25 int "How many network packets to allocate for capture"
29 network traffic. Each network frame sent or received
30 will allocate one net_pkt for network metadata.
32 the actual network data.
35 int "How many network buffers to allocate for capture"
[all …]
|
| /Zephyr-latest/lib/net_buf/ |
| D | Kconfig | 1 # Network buffer configuration options
7 bool "Network buffer support"
9 This option enables support for generic network protocol
15 bool "Network buffer logging"
18 Enable logs and checks for the generic network buffers.
27 int "Interval of Network buffer allocation warnings"
31 Interval in seconds of Network buffer allocation warnings which are
37 bool "Network buffer memory debugging"
40 Enable extra debug logs and checks for the generic network buffers.
45 bool "Network buffer pool usage tracking"
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_if.rst | 3 Network Interface
13 The network interface is a nexus that ties the network device drivers
14 and the upper part of the network stack together. All the sent and received
15 data is transferred via a network interface. The network interfaces cannot be
19 Network interfaces are created by ``NET_DEVICE_INIT()`` macro.
20 For Ethernet network, a macro called ``ETH_NET_DEVICE_INIT()`` should be used
23 network device driver source code.
25 The network interface can be turned ON by calling ``net_if_up()`` and OFF
26 by calling ``net_if_down()``. When the device is powered ON, the network
29 The network interfaces can be referenced either by a ``struct net_if *``
[all …]
|
| D | vlan.rst | 14 partitioned and isolated computer network at the data link layer
15 (OSI layer 2). For ethernet network this refers to
18 In Zephyr, each individual VLAN is modeled as a virtual network interface.
19 This means that there is an ethernet network interface that corresponds to
20 a real physical ethernet port in the system. A virtual network interface is
21 created for each VLAN, and this virtual network interface connects to the
22 real network interface. This is similar to how Linux implements VLANs. The
23 *eth0* is the real network interface and *vlan0* is a virtual network interface
28 many network interfaces there will be in the system. For example, if there is
29 one network interface without VLAN support, and two with VLAN support, the
[all …]
|
| D | net_shell.rst | 3 Network Shell
6 Network shell provides helpers for figuring out network status,
18 "net allocs", "Print network memory allocations. Only available if
22 "net capture", "Monitor network traffic See :ref:`network_monitoring`
24 "net conn", "Print information about network connections."
27 "net events", "Enable network event monitoring. Only available if
31 "net iface", "Print information about network interfaces."
34 "net mem", "Print information about network memory usage. The command will
38 "net ping", "Ping a network host."
39 "net route", "Show IPv6 network routes. Only available if
[all …]
|
| D | net_core.rst | 3 Network Core Helpers
13 The network subsystem contains two functions for sending and receiving
14 data from the network. The ``net_recv_data()`` is typically used by network
15 device driver when the received network data needs to be pushed up in the
16 network stack for further processing. All the data is received via a network
21 for sending and receiving network data.
|
| D | net_config.rst | 3 Network Configuration Library
13 The network configuration library sets up networking devices in a
20 .. csv-table:: Kconfig options for network configuration library
25 network system is configured or initialized at all. If not set, then the
27 do all the network related configuration itself. If this option is set,
29 first network interface in the system. Typically setting static IP addresses
39 ":kconfig:option:`CONFIG_NET_CONFIG_NEED_IPV4`", "The network application needs IPv4
40 support to function properly. This option makes sure the network application
44 ":kconfig:option:`CONFIG_NET_CONFIG_NEED_IPV6`", "The network application needs IPv6
45 support to function properly. This option makes sure the network application
[all …]
|
| D | capture.rst | 3 Network Packet Capture
13 The ``net_capture`` API allows user to monitor the network
14 traffic in one of the Zephyr network interfaces and send that traffic to
22 network traffic for a given network interface. If you would like to capture
23 network data when there is no network interface involved, then you need to use
26 In cooked mode capture, arbitrary network packets can be captured and there
27 does not need to be network interface involved. For example low level HDLC
29 using the normal network interface based capture. Also CANBUS or Bluetooth
30 network data could be captured although currently there is no support in the
31 network stack to capture those.
[all …]
|
| /Zephyr-latest/include/zephyr/net/ |
| D | virtual.h | 2 * @brief Virtual Network Interface
30 * @brief Virtual network interface support functions
31 * @defgroup virtual Virtual Network Interface Support Functions
93 * struct so that we are compatible with network interface API.
106 /** Send a network packet */
110 * Receive a network packet.
131 /* Make sure that the network interface API is properly setup inside
136 /** Virtual L2 context that is needed to binding to the real network interface
143 /* My virtual network interface */
148 * Other network interface this virtual network interface is
[all …]
|
| D | net_config.h | 2 * @brief Routines for network subsystem initialization.
23 * @brief Network configuration library
24 * @defgroup net_config Network Configuration Library
34 * network is possible. For IPv6 networks, this means that the device should
52 * @brief Initialize this network application.
54 * @details This will call net_config_init_by_iface() with NULL network
59 * @param timeout How long to wait the network setup before continuing
67 * @brief Initialize this network application using a specific network
70 * @details If network interface is set to NULL, then the default one
73 * @param iface Initialize networking using this network interface.
[all …]
|
| D | net_if.h | 9 * @brief Public API for network interface
16 * @brief Network Interface abstraction layer
17 * @defgroup net_if Network Interface abstraction layer
52 * @brief Network Interface unicast IP addresses
54 * Stores the unicast IP addresses assigned to this network interface.
143 * @brief Network Interface multicast IP addresses
145 * Stores the multicast IP addresses assigned to this network interface.
172 * @brief Network Interface IPv6 prefixes
174 * Stores the IPV6 prefixes assigned to this network interface.
183 /** Backpointer to network interface where this prefix is used */
[all …]
|
| D | capture.h | 2 * @brief Network packet capture definitions
4 * Definitions for capturing network packets.
24 * @brief Network packet capture support functions
25 * @defgroup net_capture Network packet capture
61 * @brief Setup network packet capturing support.
65 * This address is used to select the network interface where the tunnel
71 * @param dev Network capture device. This is returned to the caller.
73 * @return 0 if ok, <0 if network packet capture setup failed
79 * @brief Cleanup network packet capturing support.
84 * @param dev Network capture device. User must allocate using the
[all …]
|
| D | wifi_nm.h | 2 * @brief Wi-Fi Network manager API
4 * This file contains the Wi-Fi network manager API. These APIs are used by the
5 * any network management application to register as a Wi-Fi network manager.
23 * @brief Wi-Fi Network manager API
24 * @defgroup wifi_nm Wi-Fi Network Manager API
44 * @brief WiFi Network Managed interfaces
54 * @brief WiFi Network manager instance
57 /** Name of the Network manager instance */
79 * @brief Get a Network manager instance for a given name
81 * @param name Name of the Network manager instance
[all …]
|
| D | net_context.h | 2 * @brief Network context definitions
4 * An API for applications to define a network connection.
18 * @brief Application network context
19 * @defgroup net_context Application network context
81 * @brief Network data receive callback.
83 * @details The recv callback is called after a network data packet is
89 * @param pkt Network buffer that is received. If the pkt is not NULL,
108 * @brief Network data send callback.
110 * @details The send callback is called after a network data packet is sent.
203 * because the address is already set in the network interface struct.
[all …]
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 26 bool "Native network stack support"
102 part of the net stack in order to get network drivers working without
113 Can be used to select how the network connectivity is established
138 QEMU and uses that stack to implement a virtual NAT'd network.
148 include host / guest port forwarding, device id, Network address
157 Network initialization priority level. This number tells how
158 early in the boot the network stack is initialized.
185 bool "Network shell utilities"
190 Activate shell module that provides network commands like
199 By default all the network shell commands are there and the
[all …]
|
| D | Kconfig.debug | 7 bool "Network stack logging and debugging"
10 Enable logging in various parts of the network stack.
16 module-str = Log level for network packet and buffer allocation
17 module-help = Enables debug of network packet and buffer allocations and frees.
21 bool "Debug network packet and buffer individual allocation"
24 Enables printing of network packet and buffer allocations and frees for
29 int "How many external network packet allocations"
51 module-help = Enables core network stack code to output debug messages.
56 module-str = Log level for network interface code
57 module-help = Enables network interface code to output debug messages.
[all …]
|
| D | Kconfig.mgmt | 5 bool "Network Management API"
8 of the network stack as well as receiving notification on network
12 bool "Add support for runtime network event notifications"
17 (or else) needs to be notified on a specific network event
23 prompt "Network event scheduling"
27 bool "Separate network events thread"
29 Create a dedicated thread for network event callback handlers.
36 Submit work to the system work queue to schedule calling network
44 Call network event handlers when the event is emitted.
55 Hidden option to enable the network event's queue if asynchronous
[all …]
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | nrf53_cpunet_mgmt.h | 8 * @file Nordic Semiconductor nRF53 processors family management helper for the network CPU.
17 * @brief Enables or disables nRF53 network CPU.
19 * This function shall be used to control the network CPU exclusively. Internally, it keeps track of
20 * the requests to enable or disable nRF53 network CPU. It guarantees to enable the network CPU if
23 * In conseqeuence, if @p on equals @c true then the network CPU is guaranteed to be enabled when
25 * the network CPU when the function returns.
27 * @param on indicates whether the network CPU shall be powered on or off.
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.quectel-bg9x | 30 to the rest of the network stack, letting the rx thread continue
34 string "APN for establishing network connection"
37 This setting is used to set the APN name for the network connection
38 context. This value is specific to the network provider and may
42 string "Username for establishing network connection"
45 This setting is used to set the User name for the network connection
46 context. This value is specific to the network provider and may
50 string "Password for establishing network connection"
53 This setting is used to set the Password for the network connection
54 context. This value is specific to the network provider and may
|
| D | Kconfig.ublox-sara-r4 | 52 to the rest of the network stack, letting the rx thread continue
56 string "APN for establishing network connection"
60 for the network connection context. This value is specific to
61 the network provider and may need to be changed.
77 string "MCC/MNOfor establishing network connection"
80 for the network connection context. This value is specific to
81 the network provider and may need to be changed if auto is not
94 bool "Support for network status indication"
96 Choose this setting to use a modem GPIO pin as network indication.
101 int "Network status indication GPIO ID"
[all …]
|
| /Zephyr-latest/samples/net/virtual/ |
| D | README.rst | 1 .. zephyr:code-sample:: virtual-network-interface
2 :name: Virtual network interface
5 Create a sample virtual network interface.
10 This sample application creates a sample virtual network interface for
12 There are total 4 network interfaces.
14 Ethernet network interface is providing the real network interface and
17 On top of Ethernet interface there are two virtual network interfaces,
42 an Ethernet network interface. Build the sample application like this:
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | cellular.h | 10 * @brief Public cellular network API
43 /** Cellular network structure */
98 /** API for getting network signal strength */
124 * @details Cellular network devices support at least one cellular access technology.
128 * The cellular device can only use one cellular network technology at a time. It must
129 * exclusively use the cellular network configurations provided, and will prioritize
130 * the cellular network configurations in the order they are provided in case there are
131 * multiple (the first cellular network configuration has the highest priority).
133 * @param dev Cellular network device instance.
134 * @param networks List of cellular network configurations to apply.
[all …]
|
12345678910>>...38
