Lines Matching refs:capture

12 Zephyr. This page describes how to set up a way to capture network traffic so
16 See also the :zephyr:code-sample:`net-capture` sample application from the Zephyr
22 The instructions here describe how to setup a Linux host to capture Zephyr
59 ``net-capture.py`` script from ``net-tools`` project to print or save the
60 captured network packets. The ``net-capture.py`` provides an UDP listener,
66    $ ./net-capture.py -i zeth-ip6ip -w capture.pcap
76 The ``net-capture.py`` has following command line options:
81    ./net-capture.py \
85 		UDP port (default is 4242) where the capture data is received
93 Instead of the ``net-capture.py`` script, you can for example use ``netcat``
117    :zephyr-app: samples/net/capture
131 configuration options are enabled (see ``samples/net/capture/prj.conf`` file
134 The network capture can be configured automatically if needed, but
135 currently the ``capture`` sample application does not do that. User has to use
139 ``net capture setup`` command for doing that. The command syntax is
143    net capture setup <remote-ip-addr> <local-ip-addr> <peer-ip-addr>
154    net capture setup 192.0.2.2 2001:db8:200::1 2001:db8:200::2
166    net capture setup 192.0.2.2 [2001:db8:200::1]:9999 [2001:db8:200::2]:9998
172    net capture setup 192.0.2.2 198.51.100.1:9999 198.51.100.2:9998
180    uart:~$ net capture
181    Network packet capture disabled
193    net capture enable 2
195 The ``2`` tells the network interface which traffic we want to capture. In
198 monitoring in this example. The monitoring system avoids to capture already
201 Note that you cannot capture traffic from the tunnel interface as that would
205 ``net capture setup`` so that the IP tunnel is attached to desired network
207 The capture status can be checked again like this:
211    uart:~$ net capture
212    Network packet capture enabled
224    net capture disable
231    net capture cleanup
234 The :ref:`network capture API <net_capture_interface>` functions can be called