- 1 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 2 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 3 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 4 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
- 5 Docker Reaches Across Universes at Dockercon EU
tcpdump for Network Troubleshooting
To invoke it, you must be root. The absolute basic command is just tcpdump, which captures every package into or out of the system and print a line of text to standard out. This is great if you're directly logged into a machine, but not so good if you're using ssh because every time tcpdump prints to stdout, it sends a packet with this information across the ssh connection, producing another packet whose information is printed to stdout, which is then sent across ssh ... and so on. So to filter out ssh packets, try:
tcpdump not port 22
The output will start with a precise timestamp, identify the packet as IP or as a type of TCP, and then give source and destination (both with port), followed by some packet information. Check the man page for more detail.
12:28:02.958545 IP client.example.com.59713 > ldap.example.com.ldaps: P 170:367(197) ack 149 win 60 <nop,nop,timestamp 731749928 3462143864>
There are also options to, among other things: Turn off name resolution; specify a particular network interface; get a sample of packets then exit; capture output to a file; replay information from a file; and do packet match filtering. Check the manpage for further information.