| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| D | capture.rst | 26 In cooked mode capture, arbitrary network packets can be captured and there
28 packets in PPP can be captured, as the HDLC L2 layer data is stripped away when
30 network data could be captured although currently there is no support in the
36 mode captured packets are written by the cooked mode capture API.
42 layer 2 protocol type of the captured data. The cooked mode capture API is then
45 interface is marked as captured network interface.
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/ |
| D | network_monitoring.rst | 52 Zephyr will send captured network packets to one of these interfaces.
58 captured network packets. The ``net-capture.py`` provides an UDP listener,
59 it can print the captured data to screen and optionally can also save the
78 Listen captured network data from Zephyr and save it optionally to pcap file.
101 containing the captured network packets to the configured IP tunnel, so we
156 the ``2001:db8:200::2`` is the peer IP address where the captured network
195 captured network traffic as that would lead to recursion.
199 The captured network traffic can be sent to some other network interface
213 After enabling the monitoring, the system will send captured (either received
237 captured network traffic in a useful way.
[all …]
|
| /Zephyr-Core-3.7.0/samples/net/capture/ |
| D | README.rst | 13 The captured packets are sent to
17 then the remote host where the captured packets are sent can also be reached
143 Next the monitoring is setup so that captured packets are sent as a payload
168 The tunneling interface will be UP and the captured packets will be sent to
201 You should see a ICMPv4 message sent to ``192.0.2.2`` and also the captured
206 The actual captured network packets received at the end of the tunnel will look
214 Frame 34: 94 bytes on wire (752 bits), 94 bytes captured (752 bits) on interface zeth-ip6ip, id 0
225 Frame 35: 94 bytes on wire (752 bits), 94 bytes captured (752 bits) on interface zeth-ip6ip, id 0
|
| /Zephyr-Core-3.7.0/tests/kernel/fatal/message_capture/ |
| D | README | 1 This test case verifies that kernel fatal error logging message can be captured.
|
| /Zephyr-Core-3.7.0/subsys/net/lib/capture/ |
| D | Kconfig | 16 The captured packets are sent to another host for processing.
19 The captured network packets are sent using IPIP tunnel
46 if one needs to send captured data to multiple different devices,
94 This defines how many ETH_P_* link type values can be captured
|
| D | capture.c | 514 struct net_pkt *captured; in net_capture_pkt_with_status() local
546 captured = pkt; in net_capture_pkt_with_status()
551 captured = net_pkt_clone(pkt, K_NO_WAIT); in net_capture_pkt_with_status()
555 if (captured == NULL) { in net_capture_pkt_with_status()
563 net_pkt_set_orig_iface(captured, iface); in net_capture_pkt_with_status()
564 net_pkt_set_iface(captured, ctx->tunnel_iface); in net_capture_pkt_with_status()
567 ret = net_capture_send(ctx->dev, ctx->tunnel_iface, captured); in net_capture_pkt_with_status()
570 net_pkt_unref(captured); in net_capture_pkt_with_status()
|
| /Zephyr-Core-3.7.0/samples/sensor/mcux_acmp/ |
| D | README.rst | 17 captured on J25-13, the :ref:`frdm_ke17z` and :ref:`frdm_ke17z512` boards are
18 captured in J2-3, need change the external voltage signal to check the output.
|
| /Zephyr-Core-3.7.0/drivers/net/ |
| D | Kconfig | 76 packet capturing in core network stack to send the captured packets
78 where the captured packets are sent for processing. Note that you
87 The captured PPP frames are temporarily stored into this buffer.
|
| /Zephyr-Core-3.7.0/samples/net/sockets/dumb_http_server_mt/ |
| D | README.rst | 43 You should see a page with a sample content about Zephyr (captured at a
|
| /Zephyr-Core-3.7.0/samples/net/sockets/dumb_http_server/ |
| D | README.rst | 44 content about Zephyr (captured at a particular time from Zephyr's web
|
| /Zephyr-Core-3.7.0/arch/arm/core/cortex_a_r/ |
| D | Kconfig | 12 # related to that core. Everything else is captured inside the if
|
| /Zephyr-Core-3.7.0/doc/hardware/peripherals/sensor/ |
| D | read_and_decode.rst | 98 should be captured with the event.
|
| /Zephyr-Core-3.7.0/include/zephyr/net/ |
| D | net_pkt.h | 186 uint8_t captured : 1; /* Set to 1 if this packet is already being member
445 return !!(pkt->captured); in net_pkt_is_captured()
450 pkt->captured = is_captured; in net_pkt_set_captured()
|
| /Zephyr-Core-3.7.0/doc/project/ |
| D | working_groups.rst | 79 - Working group meetings and offline discussions shall be captured in a
|
| /Zephyr-Core-3.7.0/doc/services/portability/posix/overview/ |
| D | index.rst | 71 inactive (for reference only). Nevertheless, the intent is still captured as part of POSIX-1.2017
|
| /Zephyr-Core-3.7.0/doc/services/shell/ |
| D | index.rst | 93 Details on the configuration settings are captured in the following files:
108 Details on the configuration settings are captured in the following files:
122 Details on additional configuration settings are captured in:
740 separating them, the log can be captured or monitored without shell output or
|
| /Zephyr-Core-3.7.0/doc/hardware/porting/ |
| D | shields.rst | 63 shields (and/or targets) shall not be captured here.
|
| /Zephyr-Core-3.7.0/doc/services/ |
| D | formatted_output.rst | 50 is deferred. In that case, a state (format string and arguments) must be captured.
|
| /Zephyr-Core-3.7.0/cmake/emu/ |
| D | qemu.cmake | 253 # PCAP has been set to the file where traffic should be captured
|
| /Zephyr-Core-3.7.0/doc/develop/west/ |
| D | west-apis.rst | 476 Standard error is now captured.
|
| /Zephyr-Core-3.7.0/subsys/shell/backends/ |
| D | Kconfig.backends | 591 characters that will be captured from command output.
|
| /Zephyr-Core-3.7.0/doc/security/ |
| D | secure-coding.rst | 26 security perspective. Many of the ideas contained herein are captured
|
| /Zephyr-Core-3.7.0/arch/arm/core/cortex_m/ |
| D | Kconfig | 9 # else is captured inside the if CPU_CORTEX_M block so they are not exposed
|
| /Zephyr-Core-3.7.0/doc/kernel/usermode/ |
| D | syscalls.rst | 537 as data captured from some MMIO region, the implementation function must
|
| /Zephyr-Core-3.7.0/doc/services/logging/ |
| D | index.rst | 719 logging. This is useful when the log data needs to be captured manually
|
