Searched refs:network (Results 1 – 25 of 367) sorted by relevance
12345678910>>...15
| /Zephyr-latest/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_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 sockets", "Show network socket information and statistics. Only available if
[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 | capture.rst | 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.
35 * An ``any`` network interface is created. It acts as a sink where the cooked
[all …]
|
| 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 …]
|
| 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:
|
| /Zephyr-latest/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-latest/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 | net_config_guide.rst | 10 This document describes how various network configuration options can be
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
41 When using the fixed size data buffers, the memory consumption of network buffers
42 can be tweaked by selecting the size of the data part according to what kind of network
[all …]
|
| D | network_tracing.rst | 10 User can enable network core stack and socket API calls tracing.
12 The :kconfig:option:`CONFIG_TRACING_NET_CORE` option controls the core network
15 verdicts i.e., whether the network packet was successfully sent or received.
17 it took to deliver the network packet, and the network interface, priority
|
| /Zephyr-latest/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-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:
|
| 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-latest/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-latest/subsys/net/l2/dummy/any/ |
| D | Kconfig | 5 bool "Pseudo network interface a.k.a any interface"
9 This implements a pseudo network interface that does nothing
11 on top of it that can act as a network packet capture handlers.
12 The option will create an "any" network interface which acts
19 module-str = Log level for pseudo network interface
|
| /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
|
| /Zephyr-latest/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
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
99 bool "Monitor network events from net shell"
102 Allow user to monitor network events from net shell using
[all …]
|
| /Zephyr-latest/samples/net/mdns_responder/ |
| D | Kconfig | 11 The value depends on your network setup.
16 The value depends on your network setup.
21 The value depends on your network setup.
35 The value depends on your network setup.
40 The value depends on your network setup.
45 The value depends on your network setup.
|
| /Zephyr-latest/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-latest/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-latest/samples/net/vlan/ |
| D | Kconfig | 11 The value depends on your network setup.
16 The value depends on your network setup.
21 The value depends on your network setup.
35 The value depends on your network setup.
40 The value depends on your network setup.
45 The value depends on your network setup.
|
12345678910>>...15
