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

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

commit 56fe4b51495fe942a2f803e3ea6bf5076bcab284 Author: Sven Eckelmann sven@narfation.org Date: Sun Oct 27 14:44:57 2019 +0000

doc: open-mesh/Analyzing_virtual_network_packets

56fe4b51495fe942a2f803e3ea6bf5076bcab284 open-mesh/Analyzing_virtual_network_packets.textile | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/open-mesh/Analyzing_virtual_network_packets.textile b/open-mesh/Analyzing_virtual_network_packets.textile index be2bc02..99f24f9 100644 --- a/open-mesh/Analyzing_virtual_network_packets.textile +++ b/open-mesh/Analyzing_virtual_network_packets.textile @@ -4,9 +4,11 @@ h2. Wireshark

The easiest way to get the traffic of a virtual machine is via the tap interfaces. It is recommended to use the newest wireshark version (git master branch) to get support for batman-adv's packet format. Wireshark can then be started manually on a specific tap interface:

-<pre> +<pre><code class="shell"> wireshark -k -i tap1 -</pre> +</code></pre> + +

h2. View traffic via wireshark from virtual machine

@@ -18,4 +20,3 @@ 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 </code></pre> \ No newline at end of file -