The traffic to and from your local machine is obviously available independent of your network topology, so you don't need to worry about the topology for now.Ĭhoose the right interface to capture from (see /NetworkInterfaces) and start a capture. In this step: Capturing 'your own local traffic' is the easiest way to successfully capture your first traffic. Step 3: Capture traffic 'sent to' and 'sent from' your local machine User's Guide about Time Zones your computer's time and time zone settings should be correct, so the time stamps captured are meaningful capture support is enabled / a capture driver is installed CaptureSupport - your operating system must support packet capturing, e.g. special privileges allowing capturing as a normal user (preferred) or root / Administrator privileges CapturePrivileges - you must have sufficient privileges to capture packets, e.g. In this step: Setup the machine's configuration to be able and allowed to capture. If you have to change network cabling to start a capture, ensure that you are allowed to do so! Network administrators and other people are usually not amused with re-arrangements to 'their' network. In this step: Make sure you're allowed to do what you're going to do!Įnsure that you are allowed to capture packets from the network you are working on! For example, corporate policies or applicable law might prevent you from capturing on the network you're using! Step 5: Capture traffic using a remote machine.Step 4: Capture traffic destined for machines other than your own.Step 3: Capture traffic 'sent to' and 'sent from' your local machine.

Download wireshark packet capture