π Lecture 98 β Wireshark Lab 10
π Overview: This lecture teaches how to launch and navigate through Wiresharkβs Expert Infos feature. Understanding Expert Infos allows network analysts to quickly detect problems, obtain basic communication information, and view/jump to packet comments, making it essential for efficient network troubleshooting.
ποΈ Topics Covered
The lecture covers opening the Expert Infos window via the Status Bar, exploring its six tabs (Errors, Warnings, Notes, Chats, Details, Packet Comments), disabling IPv4 checksum validation to eliminate false errors, and using the tool to jump to specific packets. It also demonstrates how Expert Infos reveals issues like duplicate ACKs caused by high latency or connection outages.
π Lecture Summary
Step 1-3: Opening and Understanding Expert Infos
To begin, open tr-twohosts.pcapng. Click the Expert Infos button in the bottom left corner of the Status Bar to open the Expert Infos window. The window is divided into six tabs:
- Errors: Checksum errors, dissector failures.
- Warnings: Potential problems detected.
- Notes: Symptoms of problems; typically recovery processes.
- Chats: TCP connection overhead (handshake, Window updates, disconnects).
- Details: Summary of Errors, Warnings, Notes, and Chats.
- Packet Comments: List of all packet comments in the trace file.
If IPv4 checksum validation is disabled, no Expert Infos Errors appear. Otherwise, 6,767 IPv4 Bad Checksum Errors will show. To disable validation, right-click on the Internet Protocol Version 4 line in the Packet Details Pane, select Protocol Preferences, and toggle off Validate IPv4 checksum if possible. Click the Warnings tab of the Expert Infos window, then click on a packet to jump to that location in the trace file.
π‘ Why this matters: Disabling checksum validation avoids false positives caused by hardware offloading, allowing you to focus on real network issues.
Step 4: Interpreting Notes
Click the Notes tab. As you scroll, you will see 589 Duplicate ACKs sent by the receiver to recover a missing packet. This can be caused by a very high latency path or a brief connection outage.
π Definition β Duplicate ACK: An acknowledgment sent by the receiver for the same sequence number multiple times, indicating a missing packet that triggers fast retransmission.
π Example: In tr-twohosts.pcapng, 589 Duplicate ACKs appear in the Notes tab, signaling a missing packet due to high latency or a brief connection outage.
β Key Takeaways
The Expert Infos window in Wireshark is a powerful troubleshooting tool with six tabs: Errors, Warnings, Notes, Chats, Details, and Packet Comments. Disabling IPv4 checksum validation under Protocol Preferences eliminates false error counts caused by hardware offloading. The Notes tab reveals recovery processes like Duplicate ACKs, which indicate packet loss from high latency or brief outages. You can click any Expert Infos entry to jump directly to the corresponding packet in the trace file. Mastering Expert Infos enables rapid detection of network problems efficient navigation of large captures.
π§ Quick Revision Questions
- What are the six tabs in the Wireshark Expert Infos window?
- How can you disable IPv4 checksum validation in Wireshark?
- What does the presence of many Duplicate ACKs in the Notes tab indicate?
- How do you jump directly to a specific packet from an Expert Infos entry?
- What type of information is found under the Chats tab of Expert Infos?
π Lecture 99 β Wireshark Lab 11
π Overview: This lecture demonstrates how to change the dissector behavior in Wireshark to properly measure network performance metrics. It focuses on the critical preference setting "Allow subdissector to reassemble TCP streams" and shows how its default setting can lead to inaccurate HTTP response time measurements.
ποΈ Topics Covered
The lecture covers changing the TCP dissector reassembly preference setting, opening a specific pcap file (tr-youtubebad.pcapng), navigating packets using hyperlinks, identifying incorrect HTTP response time calculations, and toggling protocol preferences to obtain accurate measurements.
π Lecture Summary
Change the TCP Dissector Reassembly Setting to Properly Measure HTTP Response Times
Some of Wireshark's predefined preference settings are not ideal for troubleshooting. For example, the Allow subdissector to reassemble TCP streams preference setting can hide important information and produce incorrect metrics.
π Definition β Allow subdissector to reassemble TCP streams: A Wireshark preference setting that reassembles TCP segments into complete application-layer messages before passing them to the subdissector (e.g., HTTP).
Step 1: Open tr-youtubebad.pcapng. The Response Code in the Info column for Packet 6 cannot be seen because the Allow subdissector to reassemble TCP streams preference setting is enabled.
Step 2: In the Packet Detail pane of Packet 4, right-click the Hypertext Transfer Protocol heading and select Expand Subtrees. A hyperlink to the response packet is located at the bottom of the HTTP section. Double-click the hyperlink to jump to Packet 29,259.
Step 3: Scroll to the bottom of the HTTP header in Packet 29,259. The Time Since Request (http.time) field indicates the HTTP response time was over 276 seconds.
π Formula: http.time = Time Since Request β The time difference between the HTTP request packet and the HTTP response packet with the 200 OK response.
π‘ Why this matters: This measured response time is not correct. The HTTP response time is measured from the HTTP request packet to the HTTP response packet that contains the 200 OK response.
Step 4: To find the actual HTTP response time, in the Packet Details pane of any packet, right-click the TCP header, select Protocol Preferences, and toggle off the Allow subdissector to reassemble TCP streams preference setting.
Step 5: Click Close to shut down the Expert Infos window.
β Key Takeaways
The default Wireshark preference "Allow subdissector to reassemble TCP streams" can produce misleading HTTP response time measurements by reassembling TCP streams before the HTTP dissector processes them. Students must know how to locate the HTTP response time field (http.time) in the packet details, use hyperlinks to jump between related packets, and toggle protocol preferences by right-clicking the TCP header and selecting Protocol Preferences. The correct HTTP response time measurement requires this preference to be turned off, as demonstrated by correcting a measured value of over 276 seconds to the actual value. This skill is essential for accurate network troubleshooting using Wireshark.
π§ Quick Revision Questions
- What is the specific preference setting that causes incorrect HTTP response time measurements in Wireshark?
- How do you navigate directly from an HTTP request packet to its corresponding response packet in Wireshark?
- What field in the HTTP header indicates the HTTP response time, and in which packet (by number) was it shown as over 276 seconds?
- What step must you follow to toggle off the Allow subdissector to reassemble TCP streams preference?
- Why does the "Allow subdissector to reassemble TCP streams" setting produce an incorrect HTTP response time measurement?
π Lecture 100 β Wireshark Lab 12
π Overview: This lecture demonstrates how to use Wiresharkβs Conversations window to identify the most active network conversation in a packet capture file. It also shows how to apply a filter to isolate and analyze the packets belonging to that conversation. Understanding top talkers is critical for network troubleshooting, security analysis, and performance monitoring.
ποΈ Topics Covered
This lecture covers using the Statistics β Conversations feature in Wireshark to find the most active TCP conversation by byte count, sort conversations by byte count, and apply a filter to view only packets from that specific conversation. It uses the tr-general.pcapng trace file as the working example.
π Lecture Summary
Step 1: Open the Trace File
Open the file tr-general.pcapng in Wireshark to begin the analysis.
Step 2: Open the Conversations Window
Navigate to Statistics β Conversations. A dialog box appears with tabs indicating the number of each type of conversation (Ethernet, IPv4, TCP, UDP, etc.) seen in the trace file.
Step 3: Find the Most Active TCP Conversation
We are interested in the most active TCP conversation by byte count. Click the TCP tab, then click the Bytes column heading twice to sort from high to low. The most active conversation displayed is between IP address 192.168.1.72 on port 32313 and IP address 192.87.106.229 on port 80 (listed as http).
Step 4: Filter to Show Only This Conversation
Right-click on this top conversation and select Apply as Filter β Selected A <-> B. Wireshark applies the filter and displays the 123 packets belonging exclusively to this conversation.
β Key Takeaways
The Conversations window in Wireshark is the primary tool for identifying the most active conversations in a capture. Sorting by the Bytes column (high to low) reveals the conversation with the most data transferred. The Apply as Filter β Selected A <-> B option allows you to isolate all packets of a specific conversation for focused analysis. The most active TCP conversation in the example is a web (HTTP) connection between a local host and a remote server on port 80.
π§ Quick Revision Questions
- Which menu path opens the Conversations window in Wireshark?
- How do you sort conversations to find the one with the highest byte count?
- What is the IP address and port of the local host in the most active TCP conversation in the example?
- What option allows you to filter all packets belonging to a selected conversation?
- How many packets belong to the most active conversation in the example trace?
π Lecture 101 β Wireshark Lab 13
π Overview: This lecture demonstrates how to build and use a basic IO Graph in Wireshark to visualize network throughput. It is critical for troubleshooting because the IO Graph helps you quickly identify performance problems like delays and packet loss recovery in TCP conversations.
ποΈ Topics Covered
This lecture covers building a basic IO Graph in Wireshark, interpreting throughput drops found in the graph, investigating two specific problem points in a trace file (tr-winsize.pcapng), analyzing a TCP Window Update packet with a 2.75-second delay, and observing packet loss recovery at the client side.
π Lecture Summary
Building a Basic IO Graph in Wireshark
The IO Graph is a tool used to view throughput levels for all traffic in a trace file, or to plot a subset of traffic based on display filters. It helps you prioritize troubleshooting tasks by visually showing network performance issues. To begin, open the trace file tr-winsize.pcapng, which contains a single TCP conversation where an HTTP client downloads a large file from a web server. Then select Statistics | IO Graph. By default, Wireshark displays the packets per second rate (packet per tick with a default tick rate of one second).
Investigating the First Throughput Drop
To investigate the first drop in throughput seen on the graph, click on it. Wireshark jumps to that point in the trace file for further analysis. If your Time column is set to Seconds Since Previous Displayed Packet (View | Time Display Format), you will see a delay of over 2.75 seconds in the trace file. Packet 375 is marked as a TCP Window Update packet. This indicates that the delay may be related to the Window Size value advertised by the client (10.0.52.164).
π Definition β TCP Window Update: A packet that informs the sender about the current size of the receiverβs receive window, indicating how much data the receiver is willing to accept. π‘ Why this matters: A small or shrinking window size can throttle throughput, causing significant delays in data transfer.
Investigating the Second Throughput Drop
Go to the IO Graph and click on the second problem point. From Wiresharkβs window, you can see what is happening at this point in the file download process. The client appears to be in the middle of a packet loss recovery process.
π Definition β Packet Loss Recovery: The process by which TCP detects and retransmits lost packets, often triggered by duplicate acknowledgments or timeouts. π‘ Why this matters: Packet loss recovery can drastically reduce throughput, and spotting it in an IO Graph helps you locate the exact moment and cause.
After analysis, go to the IO Graph and click Close.
β Key Takeaways
The IO Graph is a powerful tool for quickly visualizing throughput levels and spotting network problems in a trace file. The first throughput drop was caused by a TCP Window Update packet, introducing a delay of over 2.75 seconds, likely due to a small client window size. The second drop occurred because the client was engaged in a packet loss recovery process. Plotting subsets of traffic with display filters can further refine troubleshooting. Understanding these two common causes β window updates and packet loss recovery β is essential for diagnosing HTTP download slowdowns in Wireshark.
π§ Quick Revision Questions
- What is the default metric plotted by the IO Graph in Wireshark?
- What type of packet was Packet 375, and what was the delay associated with it?
- What does a TCP Window Update packet indicate about the receiver?
- What network event was the client experiencing at the second throughput drop point?
- Why is the IO Graph useful for prioritizing troubleshooting tasks?
π Lecture 102 β Wireshark Lab 14
π Overview: This lecture teaches how to create a coloring rule in Wireshark to quickly identify specific packet types. The focus is on building a rule to highlight DNS errors with an orange background, making them stand out in the Packet List pane. This skill is essential for efficient network troubleshooting and packet analysis.
ποΈ Topics Covered
The lecture covers the step-by-step process of adding a coloring rule in Wireshark. It begins with opening a sample capture file and filtering for DNS traffic. It then explains how to use the Packet Details pane to examine DNS response codes, and how to create a new coloring rule that triggers when the Reply Code field indicates an error (value greater than 0). Finally, it covers setting the background color to orange and applying the rule.
π Lecture Summary
Step 1: Open the Capture File
Open the provided pcapng file tr-chappellu.pcapng. This file contains a network trace where a client attempts to resolve a domain name multiple times.
Step 2: Filter for DNS Traffic
Type dns in the display filter area and click Apply. This filters the packets to show only DNS traffic. In this capture, 43 packets match. The client sends requests to two DNS servers (75.75.75.75 and 75.75.76.76) to resolve www.chappellU.com. It sends nine requests before receiving a successful answer in Packet 12.
Step 3: Examine the DNS Response
Right-click on the Domain Name System (query) section in the Packet Details window for Packet 12. Select Expand Subtrees to see the full structure. Inside the Flags section, locate the Reply Code field.
π Definition β Reply Code (rcode): A field in a DNS response that indicates the status of the query. A value of 0 means success, while any value greater than 0 indicates a DNS error (e.g., NXDOMAIN, SERVFAIL).
π Example: In Packet 12, the Reply Code is 0, meaning the DNS query was successful.
Step 4: Create a New Coloring Rule
Right-click on the Reply Code field and select Colorize with Filter | New Coloring Rule.
Step 5: Name the Rule and Set the Filter
Enter DNS Errors as the name of the new coloring rule. Change the String value to dns.flags.rcode > 0. This filter matches any DNS packet where the Rcode field is greater than 0, i.e., any DNS error.
π Formula: dns.flags.rcode > 0 β This selects packets where the DNS response indicates an error condition.
Step 6: Set the Background Color
Click the Background Color button. In the Color Name field, type orange. Wireshark automatically converts the word "orange" to its hex value #FFA500 and shows a preview of the color. Click OK to close the Background Color window, then click OK to close the Edit Color Filter window.
π‘ Why this matters: The new rule appears at the top of the list of color filters. Packets are processed in order through this list. Now, any DNS error packet will appear with an orange background in the Packet List pane.
β Key Takeaways
The most critical skill from this lecture is that coloring rules allow you to visually highlight packets matching specific display filters. The key to creating a useful rule is to identify a field (like dns.flags.rcode) and define a condition (> 0) that indicates the packets of interest. Colors are set by name (e.g., "orange") or hex value (e.g., #FFA500), and rules are processed top-down. For the exam, remember the exact syntax for the DNS error filter (dns.flags.rcode > 0) and the steps to create a coloring rule via the right-click context menu.
π§ Quick Revision Questions
- What is the exact display filter string used to highlight DNS errors in the coloring rule?
- What does a Reply Code (rcode) value of 0 signify in a DNS response?
- In which pane of Wireshark do you right-click to open the "Colorize with Filter" option?
- How does Wireshark process multiple coloring rules when packets are displayed?
- What is the hex color value for the word "orange"?
π Lecture 103 β Capture Options for a Switched Network
π Overview: This lecture explains the challenges of capturing network traffic on a switched network and provides practical solutions such as port mirroring, hubs, and TAPs. It also covers essential configuration steps in Wireshark, including applying coloring rules to highlight specific packets (like DNS errors) and understanding where coloring rule details appear in the packet details pane. This topic matters because modern networks rely on switches, which by default isolate traffic, making packet capture non-trivial.
ποΈ Topics Covered
The lecture explains how to apply a coloring rule to mark packets (like DNS errors) in Wireshark and where the rule name and string appear in the Frame section. It then distinguishes between the four types of packets forwarded by a switch (broadcast, multicast, traffic to your hardware address, and traffic to an unknown hardware address), and details three methods for capturing another user's traffic on a switched network: using a hub, using a TAP, or using port mirroring (SPAN). The summary emphasizes that connecting directly to a switch port normally prevents listening to other users' traffic.
π Lecture Summary
Step 7: Click OK to close the Coloring Rules window.
After configuring a coloring rule in Wireshark, you click OK to close the Coloring Rules window. This applies the rule to packets in the trace.
Step 8: With dns filter still in place, scroll through the packets to see if you notice the two DNS errors in the trace file.
With a display filter for DNS still active, you scroll through the packets. Two DNS errors appear in the trace file at Packets 83 and 84, highlighted with an orange coloring rule.
Step 9: Expand the Frame section in the Packet Details pane of Packet 83.
In Packet 83, expand the Frame section in the Packet Details pane. This area lists your Coloring Rule Name and Coloring Rule String.
Topic 103: Capture Options for a Switched Network
This topic explains tips on choosing a capture location for a switched network. Today, almost all network clients connect through a switch. Four types of packets are forwarded by a switch: broadcast, multicast, traffic to your hardware address, and traffic to an unknown hardware address.
Because of this, when you connect a system running Wireshark directly to a switch port, you cannot listen to other users' traffic. To capture the traffic between a client and the upstream switch (and ultimately a remote host), you need to use one of three methods:
- Use a hub (which repeats all traffic to all ports)
- Use a TAP (a Test Access Point that copies all traffic to a monitoring port)
- Use port mirroring (also known as SPAN β Switched Port Analyzer), which configures the switch to send a copy of traffic from one port to another port where Wireshark is connected
π Definition β Port Mirroring (SPAN): A switch configuration that copies all traffic from one or more source ports to a destination (monitor) port, allowing Wireshark to capture traffic without interrupting the original flow.
π Definition β TAP (Test Access Point): A hardware device inserted between two network devices that copies all traffic passing through it to a monitoring port, with no impact on performance or packet loss.
π‘ Why this matters: Without using one of these three methods, a user connecting Wireshark directly to a switch port will only see their own traffic and broadcast/multicast frames, missing all other client conversations.
β Key Takeaways
To capture traffic from other users on a switched network, you must use a hub, a TAP, or port mirroring (SPAN) β a direct connection to a switch port only captures your own traffic, broadcast, multicast, traffic to your hardware address, and traffic to unknown hardware addresses. In Wireshark, coloring rules are applied via the Coloring Rules window, and the rule name and string appear in the Frame section of the Packet Details pane. DNS errors in a trace file can be highlighted (e.g., with orange coloring) to quickly spot issues. For exam purposes, remember the four packet types a switch forwards and the three capture solutions for switched networks.
π§ Quick Revision Questions
- What four types of packets does a switch forward?
- Why can't you capture other users' traffic when connecting Wireshark directly to a switch port?
- Name three methods for capturing traffic between a client and an upstream switch on a switched network.
- Where in the Packet Details pane do you find the Coloring Rule Name and Coloring Rule String?
- How do you apply a coloring rule to highlight DNS errors in a trace file?
π Lecture 104 β Wireshark Lab 15
π Overview: This lecture covers essential methods for capturing network traffic, with a focus on wireless capture options in Wireshark. Understanding these techniques is critical for network troubleshooting and security analysis, enabling you to obtain accurate traffic samples for examination.
ποΈ Topics Covered
The lecture begins by describing three methods for capturing wired traffic: installing Wireshark on the user's machine, using switch port spanning, and using a Test Access Port (Tap). It then shifts focus to wireless capture, explaining how to test if your native WLAN adapter can capture management and control traffic in monitor mode, with step-by-step instructions for verifying capture capabilities.
π Lecture Summary
(a) Install Wireshark on the user's machine
This is a great option if you can physically access the user's machine. It provides direct capture of all traffic sent and received by that host.
(b) Make the switch send a copy of the traffic down your analyzer port
The next option is Switch Port Spanning (also called "spanning"). This makes the switch send a copy of the traffic down to your analyzer port. However, not all switches support this feature. If there are corrupt frames traveling from the user's host, those corrupt frames won't be forwarded down the spanned port by the switch. Furthermore, avoid oversubscribing your switch portβthis means spanning a level of traffic that cannot "fit" down the pipe to your Wireshark system. The switch will drop excess packets and the trace file will be incomplete.
π‘ Why this matters: Oversubscription can lead to missing data in your capture, giving you an incomplete picture of network activity.
(c) Tap in and obtain a copy of the traffic between the client and the switch
Use a Test Access Port ("Tap"). A tap is a simple device that copies all the traffic flowing through it (including those corrupt packets) out to a monitor port. This method ensures you capture even faulty frames that spanning would miss.
Wireless Capture Options
You are lucky if your native WLAN adapter can capture WLAN Management and Control traffic. In Monitor Mode, you should be able to see traffic from any network as well.
π Definition β Monitor Mode: A special mode for wireless adapters that allows capture of all wireless traffic in range, including management and control frames, regardless of the network the adapter is associated with.
π Example: To test the capture capabilities of your WLAN native adapter, follow these steps:
- Step 1: Launch Wireshark and click the Interface List button on the Main Toolbar.
- Step 2: Select the checkbox in front of your WLAN adapter and click Start.
- Step 3: Go to a browser window and visit www.wireshark.org. Go to Wireshark and examine the packets you have captured. If your native adapter is suitable for network capture, you should see some WLAN management and control traffic (such as Beacon packets and Probe Request/Probe Response packets).
β Key Takeaways
The most critical points from this lecture are: (1) For wired captures, you have three optionsβinstall Wireshark locally, use switch port spanning (with the risk of missing corrupt frames and oversubscription), or use a tap to capture all traffic including corrupt packets. (2) For wireless captures, not all native WLAN adapters support capturing management and control frames; you must test your adapter by entering monitor mode. (3) A successful test will show Beacon frames and Probe Request/Response packets in your capture, confirming your adapterβs suitability for wireless analysis. (4) Oversubscribing a spanned port will cause packet drops and an incomplete trace file, so carefully monitor traffic volume. (5) The best method depends on your access to the network infrastructure and whether you need to see corrupt frames, which only a tap can capture.
π§ Quick Revision Questions
- What are the three methods for capturing wired traffic described in this lecture?
- Why might corrupt frames not appear in a capture taken from a spanned switch port?
- What problem does "oversubscribing" a switch port cause for your Wireshark capture?
- What is the key advantage of using a Test Access Port (tap) over switch port spanning?
- How can you test whether your native WLAN adapter is suitable for capturing management and control traffic in Wireshark?
π Lecture 105 β Wireshark Lab 16
π Overview: This lecture provides a step-by-step guide on how to capture network traffic to a File Set in high traffic rate situations using Wireshark. Understanding file sets is critical for managing large captures by splitting them into manageable, linked files that can be navigated systematically.
ποΈ Topics Covered
This lecture covers the concept of File Sets in Wireshark, why they are important in high traffic rate situations, and a complete lab exercise demonstrating how to configure automatic file rotation and stop conditions. It also explains how to navigate between files in a set while preserving display filters for efficient packet analysis.
π Lecture Summary
Capturing to a File Set in High Traffic Rate Situations
This section introduces the importance of capturing to file sets when dealing with high network traffic. File sets are groups of trace files that are linked based on their file name pattern, allowing the capture to be split into multiple smaller files rather than one enormous file. This prevents memory issues and makes analysis more practical.
π‘ Why this matters: In high-traffic environments, a single capture file can become too large to open or work with efficiently. File sets solve this by automatically rotating files at a set interval.
π File Set: A group of trace files that are linked based on their file name, allowing Wireshark to treat them as a single continuous capture.
Lab Exercise: Capturing Three Files
This section provides the practical steps to configure and execute a file set capture with an autostop condition.
Step 1: Click the Capture Options button on the Main Toolbar.
Step 2: In the Capture Options window, set the path and file name for your file set. Enable Use Multiple Files. Set Next file every 1 Minute(s). Set Stop capture after 3 Files. Click Start.
Step 3: Open a browser and visit several web sites. Browse for at least 3 minutes. Your capture process will automatically stop after 3 minutes. The third file will be displayed.
Step 4: To move from one file to the next file in a file set, select File | File Set | List Files. Select a file in the list and Wireshark will load that file. You can quickly locate specific packets in the file set by applying a display filter to one of the files and then clicking subsequent files in the file list. The display filter will remain in place as you open each file. When you are finished navigating through files, click Close on the File Set window.
π Configuration Rule: Next file every 1 Minute(s) + Stop after 3 Files = Total capture duration of exactly 3 minutes
π Example: If you set the file name to "capture.pcapng", Wireshark will generate files named "capture_00001_20250101120000.pcapng", "capture_00002_20250101120100.pcapng", and "capture_00003_20250101120200.pcapng", each containing 1 minute of traffic.
β Key Takeaways
File sets are essential for managing high-traffic captures by splitting them into smaller, linked time-based files. The lab demonstrates configuring a 1-minute file rotation with an automatic stop after 3 files, producing exactly 3 minutes of capture. Critical to remember is that when navigating between files in a set, any display filter applied to one file remains active when opening subsequent files, enabling consistent cross-file analysis. The File Set List window is accessed through File | File Set | List Files, and files are loaded by simply selecting them from the list.
π§ Quick Revision Questions
- What is a file set in Wireshark and why is it used?
- In the lab exercise, what two configuration parameters are set to control file rotation and capture duration?
- After the capture automatically stops, how many files will have been created?
- How do you navigate from one file to the next within a file set?
- What happens to a display filter when you open subsequent files in a file set?
π Lecture 107 β Verify the Target Host Traffic
π Overview: This lecture explains how to verify that you are capturing the correct traffic from target hosts in Wireshark. It covers common capture process problems and introduces the TCP/IP resolution process that applications must follow to communicate on a network. Understanding this verification step is critical for reliable network analysis.
ποΈ Topics Covered
This lecture covers two main areas: checking your capture process for common errors such as capture filter mismatches, tap connection issues, or switch spanning problems; and understanding the TCP/IP resolution process including port resolution, IP address resolution via DNS, MAC address resolution through ARP, and forwarding based on MAC addresses.
π Lecture Summary
Check Your Capture Process
The first step of any analysis process is to verify that the hosts are able to communicate and you can see their traffic in the trace file. If you do not see any traffic, something may have gone wrong during the capture process. There are three common causes: A) Wireshark had a capture filter in place and the complaining user's traffic did not match the capture filter. B) If you are using a tap, the user's network cable isn't plugged into the tap. C) If you are spanning a switch port, the switch is not spanning the traffic down your analyzer port.
π‘ Why this matters: If you cannot see the target host's traffic, your entire analysis will be based on incomplete or wrong data.
Consider the TCP/IP Resolution Process
All applications must go through a basic resolution process to build the packet to communicate with another host on a TCP/IP network. This process involves four sequential steps:
-
Port Resolution: The user specifies the Port number in the URL, in the application code. This determines which application service the packet should reach on the destination host.
-
IP Address Resolution: The application must resolve a fully qualified domain name (FQDN) to an IP address using DNS (Domain Name System).
-
MAC Address Resolution: The user's machine resolves the default gateway MAC address (if required) using ARP (Address Resolution Protocol). This translates the IP address of the next-hop router into a physical MAC address.
-
Forwarding: The packet is then built and forwarded to the next-hop router using that MAC address on the local Ethernet network.
π Definition β Resolution Process: The step-by-step method by which an application converts human-readable names and service identifiers into the numerical addresses (IP, MAC, and port) needed to construct and send a packet across a TCP/IP network.
π Process Flow: URL/Application β Port Number β DNS resolves FQDN to IP Address β ARP resolves IP to MAC Address β Packet forwarded using MAC address
π Example: When a user types www.wireshark.org in a browser: 1) Port 80 or 443 is specified in the URL or browser code. 2) DNS resolves www.wireshark.org to an IP address (e.g., 198.41.0.4). 3) ARP resolves the default gateway IP to its MAC address. 4) The packet is forwarded to the gateway using that MAC address.
β Key Takeaways
The most critical things to remember: always verify that you can see the target host's traffic before beginning analysis. If no traffic appears, check three things: capture filters, tap connections, and switch spanning port configurations. Every TCP/IP communication follows a four-step resolution process: port resolution, IP address resolution via DNS, MAC address resolution via ARP, and forwarding using the resolved MAC address. Understanding this process helps you identify where communication failures occur. The MAC address resolution step uses ARP to find the default gateway's MAC address, not the destination host's MAC address when communicating across networks.
π§ Quick Revision Questions
- What are three possible reasons you might not see traffic after starting a Wireshark capture?
- List the four steps of the TCP/IP resolution process in order.
- Which protocol resolves a fully qualified domain name to an IP address?
- Which protocol resolves an IP address to a MAC address?
- What does the user specify for port resolution, and where does this specification come from?
π Lecture 109 β Wireshark Lab 19
π Overview: This lecture describes how to identify local address resolution problems in Wireshark. It covers the critical role of MAC address acquisition before client communication can occur and demonstrates how to analyze ARP failure scenarios in packet captures.
ποΈ Topics Covered
The lecture examines the local address resolution process, focusing on how a client must obtain a MAC address for a local target or router before sending packets. It explains that the client checks its cache first and, if the MAC address is unknown, sends an ARP request. The lab demonstrates identifying when ARP requests go unanswered, causing communication to fail.
π Lecture Summary
Wireshark Lab 19: Identifying Local Address Resolution Problems
Before a client can send a packet to a local target or a local router, it must obtain the MAC (Media Access Control) address of that device. If the client does not have the MAC address information in cache, the client sends out an Address Resolution Protocol (ARP) request. If no response is received when trying to acquire the local target's MAC address, the client is doneβit cannot send out a packet to the target.
π Definition β MAC Address: The Media Access Control address is a unique hardware identifier assigned to network interfaces for local network communication. π‘ Why this matters: Without the MAC address, a client cannot deliver packets at Layer 2 of the OSI model, even if it knows the target's IP address.
π Example β ARP Failure Scenario: In the lab trace file tr-localresolution.pcapng, packets show ARP requests being sent without receiving corresponding ARP replies. This indicates the client failed to resolve the local target's MAC address, blocking all subsequent communication attempts.
The lab procedure consists of:
- Step 1: Open the capture file
tr-localresolution.pcapng - Step 2: Type
arpin the display filter area and click Apply to isolate ARP packets - Step 3: Observe ARP requests that have no matching ARP replies
- Step 4: Clear the display filter when finished
π Example β Analyzing ARP Failure: When filtering for arp in Wireshark, you can identify unresolved ARP requests by looking for packets with "Who has [IP address]? Tell [sender IP]" in the Info column, followed by no corresponding "is at [MAC address]" reply.
β Key Takeaways
The most critical concept from this lecture is that MAC address resolution is a prerequisite for all local network communication. The client first checks its local cache for the MAC address; if absent, it sends an ARP request. If no ARP reply is received, the communication attempt fails completely. Students must recognize that ARP failures are identifiable in Wireshark by searching for ARP requests without corresponding replies. This highlights that network problems can occur at Layer 2 (data link layer) even when higher-layer protocols appear functional.
π§ Quick Revision Questions
- What three conditions must be met for a client to successfully send a packet to a local target?
- What does the client do if the target's MAC address is not in its local cache?
- In Wireshark, what display filter would you use to isolate ARP traffic?
- What does the "Info" column show for an ARP request that has not received a response?
- Why would a client be unable to send any packets to a local target even if it knows the target's IP address correctly?
π Lecture 110 β Wireshark Lab 20
π Overview: This lecture examines the βNo server Response to TCP Connection Requestβ scenario in Wireshark. It explains why a server may fail to respond to a TCP connection attempt and how to diagnose such issues using packet traces, focusing on packet loss and firewall blocking as primary causes.
ποΈ Topics Covered
The lecture covers multiple reasons for missing TCP handshake responses, including SYN packet loss before reaching the server, firewall dropping of SYN packets, host-based firewall blocking of ports, and SYN/ACK packet loss or blocking on the return path. It also demonstrates how to open and analyze a specific trace file and use Wiresharkβs TCP stream index column to identify separate connections.
π Lecture Summary
Wireshark Lab 20 β No Server Response to TCP Connection Request
There are several reasons why a server may not respond to a TCP connection attempt. The TCP handshake request packet (SYN) may not arrive at the server. Maybe the SYN packet was lost. A firewall along the path dropped the SYN packet, or a host-based firewall on the server blocked access to the port. Alternately, the response (SYN/ACK) may not arrive at the client. The SYN/ACK packet was lost along the path, or a firewall along the path blocked the SYN/ACK.
Step 1: Open tr-noserver.pcapng.
Step 2: Scroll through this trace file. This trace file contains only SYN packets from 192.168.1.72 to 192.168.1.66. None of the SYN packets have received SYN/ACK responses. Expand the TCP header in Packet 1. Right-click on the [Stream index: 0] line and select Apply as Column. Wireshark shows that there are 6 separate connections (TCP Stream Index: 0-5).
π Definition β SYN (Synchronize): The first packet in a TCP three-way handshake, sent by a client to initiate a connection. π Definition β SYN/ACK (Synchronize-Acknowledgment): The second packet in a TCP three-way handshake, sent by a server to acknowledge the clientβs SYN and agree to establish the connection. π Definition β Stream Index: A Wireshark identifier that groups packets belonging to the same TCP connection.
π Example: In tr-noserver.pcapng, 192.168.1.72 sends SYN packets to 192.168.1.66 over 6 separate connections (Stream Index 0-5). None receive a SYN/ACK response, indicating the server is either unreachable or blocking the connection.
π‘ Why this matters: Identifying whether the SYN packet never reaches the server or the SYN/ACK never returns helps narrow down the location of the problem (client side, network path, or server side).
β Key Takeaways
Students must remember that a missing TCP handshake response can result from either the SYN not reaching the server (lost, dropped by firewall, or blocked by serverβs host-based firewall) or the SYN/ACK not returning to the client (lost or blocked). The trace file tr-noserver.pcapng demonstrates this scenario, where multiple SYN packets are sent but no SYN/ACK is received. Using the Stream Index column in Wireshark helps identify distinct TCP connections within a capture, even when no handshake is completed.
π§ Quick Revision Questions
- What are two main categories of reasons a server may not respond to a TCP SYN?
- What does the absence of any SYN/ACK packets in a trace file indicate?
- How can you identify separate TCP connections in Wireshark when no handshake is completed?
- What is the difference between a firewall dropping the SYN and a host-based firewall blocking the port?
- In tr-noserver.pcapng, what is the source IP address sending SYN packets and what is the destination IP address?
π Lecture 111 β Wireshark Lab 21
π Overview: This lecture demonstrates how to analyze the βNo Response to Service Requestβ situation in Wireshark using a specific trace file. It focuses on interpreting TCP traffic patterns when a server fails to respond to a clientβs service request, and on using filters and columns to isolate relevant connections.
ποΈ Topics Covered
The lecture covers opening and filtering the trace file tr-serverresponse.pcapng, using the Stream Index column to differentiate separate TCP connections between client 24.6.173.220 and server 50.62.146.230, applying a TCP Conversation Filter, and analyzing the traffic to understand the βNo Response to Service Requestβ scenario.
π Lecture Summary
Topic 111: Wireshark Lab 21 β Analyzing βNo Response to Service Requestβ
This topic discusses how to analyze the βNo Response to Service Requestβ situation in Wireshark.
Step 1: Open the file tr-serverresponse.pcapng.
Step 2: Scroll through this trace file to get familiar with the traffic pattern. Use the Stream Index column to differentiate the separate connections between 24.6.173.220 and 50.62.146.230. Right-click on Packet 1 in the Packet List pane and select Conversation Filter | TCP.
π Example: By applying the TCP Conversation Filter on Packet 1, Wireshark isolates only the packets belonging to that specific TCP stream between the two IP addresses, allowing focused analysis of the βNo Response to Service Requestβ behavior.
β Key Takeaways
The βNo Response to Service Requestβ scenario is identified by observing a TCP connection where the server does not reply to the clientβs request, often visible through repeated SYN packets or lack of SYN-ACK. The Stream Index column is essential for isolating individual connections in a trace file with multiple streams. Applying a Conversation Filter (TCP) simplifies analysis by showing only packets from a single conversation. This lab reinforces the skill of using Wiresharkβs filtering and column customization to diagnose network service failures.
π§ Quick Revision Questions
- What trace file is used in this lab for analyzing βNo Response to Service Requestβ?
- Which column helps differentiate separate TCP connections between two IP addresses?
- What filter is applied after right-clicking on Packet 1 in the Packet List pane?
- What are the two IP addresses involved in the analyzed TCP connection?
- What does the βNo Response to Service Requestβ situation typically look like in a packet capture?