


Using tcpdump, you can troubleshoot a wide range of network issues including but not limited to: Although GUI-based Wireshark provides equally powerful filtering/dissecting capabilities via a more user-friendly interface, its relatively high memory footprint (for buffering packets) and GUI-based operations make Wireshark unsuitable when you are troubleshooting directly from remote headless servers. The main power of tcpdump comes from its (1) flexible packet filtering rules and (2) versatile protocol dissection capability.

Tcpdump is a command-line tool packet sniffing that allows you to capture network packets based on packet filtering rules, interpret captured packet content, and display the result in a human-readable format. While required tools may vary depending on the types of network problems you are dealing with, there are a set of essential tools that every network administrator must be familiar with, and tcpdump is definitely one of them. Feel free to play with those filters in tcpdump and you’ll find nearly everything.įeel free to comment and I will add everything in more detail.When it comes to network troubleshooting and monitoring, what types of tools you are using make a world of difference. So basically 192.168.1.1 won’t be displayed on the WAN port and so on. Keep in mind, XG has to NAT the traffic, etc. The packet arrives on Port1, will be transferred to br0, and leaves the appliance on Port2 with my MASQ ip.

In my case, using a bridge, I will see the packets 3 times.
