Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
tcpdump analysis
# On Controller node
$ tcpdump -envi eth0 | grep -i gre
$ tcpdump -envi br-int
$ tcpdump -envi br-tun
$ ip netns exec qrouter-d72adddf-4c02-4916-ae6d-16bfdaf59d99 tcpdump -nn -i qr-63ea2815-b5 icmp
$ ip netns exec qrouter-d72adddf-4c02-4916-ae6d-16bfdaf59d99 tcpdump -nn -i qg-e7110dba-a9 icmp
$ tcpdump -envi 192.168.122.163
$ tcpdump -envi br-ex
$ tcpdump -i eth0 -n arp or icmp
$ tcpdump -i eth0 -ne ip proto 47
$ ip netns exec qrouter-d72adddf-4c02-4916-ae6d-16bfdaf59d99 tcpdump -i qr-63ea2815-b5 -n
$ tcpdump -i br-ex -n
$ tcpdump -i br-ex -n icmp
$ tcpdump -i eth0 -n icmp
$ tcpdump -i any -n icmp
$ ip netns exec qrouter-d72adddf-4c02-4916-ae6d-16bfdaf59d99 tcpdump -i any icmp
$ tcpdump -i tape7110dba-a9 -n icmp
$ tcpdump -i eth0 -n not port 22
$ tcpdump -i eth0 -n not port 22 and not port amqp
# Run tcpdump on physical link used by GRE tunnels (on Controller node).
# This will isolate the problem to the compute node or the network node.
$ tcpdump -i eth0 -n ip proto gre
# On physical host
$ yum install tcpdump -y
$ tcpdump -nn -i virbr0 icmp host 192.168.122.11
$ tcpdump -nn -i virbr0 host 192.168.122.11 icmp
$ tcpdump -nn -i virbr0 host 192.168.122.11 proto icmp
$ tcpdump -nn -i virbr0 host 192.168.122.11 and proto icmp
$ tcpdump -nn -i virbr0 host 192.168.122.11
$ tcpdump -nn -i virbr0
$ tcpdump -nn -i virbr0 icmp
If you're using GRE, search for GRE on Compute node & Controller node:
[root@ostack-compute ~(keystone_kashyap)]$ tcpdump -envi eth0 | grep -i gre
[root@ostack-controller neutron(keystone_kashyap)]$ tcpdump -envi eth0 | grep -i gre
# More tcpdump analysis
1. On DHCP namespace:
[root@ostack-controller neutron(keystone_kashyap)]$ ip netns exec qdhcp-a3ec29fc-39d3-4059-9f0c-621d167578f3 tcpdump -nn -i ns-0e21a72b-01 icmp
2. On Router namespace, qr interface
[root@ostack-controller neutron(keystone_kashyap)]$ ip netns exec qrouter-57b895ce-aa5e-42c9-b5dc-fad6e3ae128b tcpdump -nn -i qr-d48caa63-3c icmp
3. On Router namespace, qg interface
[root@ostack-controller neutron(keystone_kashyap)]$ ip netns exec qrouter-57b895ce-aa5e-42c9-b5dc-fad6e3ae128b tcpdump -nn -i qg-4e064969-f7 icmp
4. On br-tun (On Controller-node & Compute-node):
[root@ostack-controller neutron(keystone_kashyap)]$ tcpdump -envi br-tun
5. On br-int (On Compute-node & Controller-node)
[root@ostack-compute c1f68599-5ed1-443e-b7ca-6bbb73fae8bd(keystone_kashyap)]$ tcpdump -envi br-int -n arp or icm
6. On br-ex (On Controller-node)
[root@ostack-controller neutron(keystone_kashyap)]$ tcpdump -i br-ex -n icmp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.