Searched refs:network (Results 1 – 25 of 302) sorted by relevance
12345678910>>...13
| /Zephyr-Core-3.5.0/subsys/net/lib/capture/ |
| D | Kconfig | 1 # Capture network packets
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"
39 network traffic.
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 12 The Zephyr network stack is a native network stack specifically designed
21 High level overview of the network stack
25 :alt: Overview of the network stack architecture
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
37 the network and set related parameters such as network link options,
38 starting a scan (when applicable), listen network configuration events, etc.
39 The :ref:`network interface API <net_if_interface>` can be used to set IP
[all …]
|
| D | net_pkt_processing_stats.rst | 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
54 took for a network packet to go from previous state to next.
[all …]
|
| D | network_monitoring.rst | 10 It is useful to be able to monitor the network traffic especially when
12 Zephyr. This page describes how to set up a way to capture network traffic so
14 network packets sent or received by a Zephyr device.
23 network RX and TX traffic. Similar instructions should work also in other
52 Zephyr will send captured network packets to one of these interfaces.
54 You can then use Wireshark to monitor the proper network interface.
58 captured network packets. The ``net-capture.py`` provides an UDP listener,
78 Listen captured network data from Zephyr and save it optionally to pcap file.
80 -i | --interface <network interface>
101 containing the captured network packets to the configured IP tunnel, so we
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | net_core.rst | 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 | 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_if.rst | 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
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 *``
30 pointer or by a network interface index. The network interface can be
36 The IP address for network devices must be set for them to be connectable.
[all …]
|
| D | net_shell.rst | 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
41 "net stats", "Show network statistics."
|
| D | net_offload.rst | 16 The network offloading API provides hooks that a device vendor can use
18 actual network connection creation, data transfer, etc., is done in the vendor
19 HAL instead of the Zephyr network stack.
34 In addition to the network offloading API, Zephyr allows offloading of networking
40 implementation on how to integrate network offloading at socket level.
|
| D | promiscuous.rst | 13 Promiscuous mode is a mode for a network interface controller that
17 to diagnose network connectivity issues by showing an application
18 all the data being transferred over the network. (See the
22 The network promiscuous APIs are used to enable and disable this mode,
23 and to wait for and receive a network data to arrive. Not all network
24 technologies or network device drivers support promiscuous mode.
44 If there is no error, then the application can start to wait for network data:
|
| D | net_config.rst | 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
50 this option tells that the network application needs IPv6 router to exists
[all …]
|
| /Zephyr-Core-3.5.0/scripts/net/ |
| D | run-sample-tests.sh | 7 network=net-tools0
89 if ! docker network ls | grep "$network" > /dev/null; then
94 echo "Could not start Docker network '$network'" >&2
98 echo "Started Docker network '$network' bridge interface" \
111 --rm -dit --network=$network $image > /dev/null; then
137 bridge_interface=$(docker network ls | grep "$network" | cut -d " " -f 1)
139 docker network rm "$network" > /dev/null
141 echo "Stopped Docker network '$network' bridge interface" \
144 echo "Could not stop Docker network '$network'" >&2
289 network implemented by the 'net-tools' subproject.
[all …]
|
| /Zephyr-Core-3.5.0/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:
|
| D | Kconfig | 1 # Private config options for virtual network interface sample app
6 mainmenu "Networking virtual network interface sample application"
11 The value depends on your network setup.
16 The value depends on your network setup.
28 The value depends on your network setup.
33 The value depends on your network setup.
|
| /Zephyr-Core-3.5.0/tests/net/virtual/ |
| D | Kconfig | 1 # Private config options for virtual network interface test app
6 mainmenu "Virtual network interface test application"
12 The value depends on your network setup.
18 The value depends on your network setup.
24 The value depends on your network setup.
|
| /Zephyr-Core-3.5.0/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.
105 as a network status indication. See the manual for the gpio ids
|
| /Zephyr-Core-3.5.0/subsys/net/ip/ |
| D | Kconfig.debug | 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.
62 module-str = Log level for network traffic class code
[all …]
|
| D | Kconfig.mgmt | 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
59 bool "Monitor network events from net shell"
62 Allow user to monitor network events from net shell using
72 Allow user to start monitoring network events automatically
78 module-str = Log level for network management event core
79 module-help = Enable debug messages output for network management events.
|
| /Zephyr-Core-3.5.0/samples/net/lldp/ |
| D | Kconfig | 6 # This sample application will have three network interfaces.
17 The value depends on your network setup.
22 The value depends on your network setup.
36 The value depends on your network setup.
41 The value depends on your network setup.
|
| /Zephyr-Core-3.5.0/subsys/net/l2/virtual/ipip/ |
| D | Kconfig | 8 Add a IP-to-IP tunnel driver. If this is enabled, then a network
10 existing network interface. Application needs to attach the IPIP
11 driver at runtime to correct network interface.
13 network interface.
33 Enables printing of received and sent network packets.
|
| /Zephyr-Core-3.5.0/drivers/ethernet/ |
| D | Kconfig.native_posix | 15 bool "Start network interface automatically"
17 If set, the native_posix ethernet driver will set up the network
20 If not set (the default and recommended way), the network interface
32 network interface is created. The script should setup IP addresses
33 etc. for the host TAP network interface.
35 -i|--interface <network interface name>, default is zeth
47 network interface is created and setup script has been run.
49 the network traffic for the freshly started network interface.
50 Note that the network interface name CONFIG_ETH_NATIVE_POSIX_DRV_NAME
69 int "Number of network interfaces created"
[all …]
|
| /Zephyr-Core-3.5.0/samples/net/zperf/ |
| D | README.rst | 5 Use the zperf shell utility to evaluate network bandwidth.
11 allows to evaluate network bandwidth.
30 the target platform must provide a network interface supported by Zephyr.
45 Depending on the network technology chosen, extra steps may be required
46 to setup the network environment.
|
| /Zephyr-Core-3.5.0/samples/net/sockets/echo_server/ |
| D | Kconfig | 18 The value depends on your network setup.
23 The value depends on your network setup.
28 The value depends on your network setup.
42 The value depends on your network setup.
47 The value depends on your network setup.
52 The value depends on your network setup.
73 The value depends on your network setup.
|
| /Zephyr-Core-3.5.0/samples/net/stats/ |
| D | README.rst | 5 Query and display network statistics from a user application.
10 This sample shows how to query (and display) network statistics from a user
27 Follow these steps to build the network statistics sample application:
37 current network statistics to the console.
41 Global network statistics
|
12345678910>>...13
