Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-11-07,master

commit 3c3383e81a504c384479b1981e00ba5abd91dfc5 Author: Sven Eckelmann sven@narfation.org Date: Sun Oct 27 14:44:44 2019 +0000

doc: open-mesh/Analyzing_virtual_network_packets

3c3383e81a504c384479b1981e00ba5abd91dfc5 open-mesh/Analyzing_virtual_network_packets.textile | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/open-mesh/Analyzing_virtual_network_packets.textile b/open-mesh/Analyzing_virtual_network_packets.textile index a6dcdbd..be2bc02 100644 --- a/open-mesh/Analyzing_virtual_network_packets.textile +++ b/open-mesh/Analyzing_virtual_network_packets.textile @@ -12,8 +12,10 @@ h2. View traffic via wireshark from virtual machine

It is not always possible to use the tap interface because either the packets are filtered somewhere in the path from/to the virtual machine. Or sometimes the packets are not even supposed to leave the virtual machine (for example with veth or hwsim). But is it also possible to start tcpdump inside the virtual machine via ssh and send the captured data to a local fifo (named pipe) on the host machine. Wireshark can read from the pipe and show the captured data

-<pre> + +<pre><code class="shell"> mkfifo remote-dump ssh root@192.168.251.51 'tcpdump -i enp0s1 -s 0 -U -n -w - "port not 22"' > remote-dump wireshark -k -i remote-dump -</pre> \ No newline at end of file +</code></pre> +