π Lecture 152 β Wireshark Lab 54
π Overview: This lecture teaches how to identify out-of-order packets using Wireshark's Expert Infos feature and manual analysis of sequence numbers. It covers the practical steps for detecting packet loss patterns when multiple out-of-order packets appear in close proximity, which indicates retransmissions.
ποΈ Topics Covered
The lecture covers two main activities: using Wireshark's Expert Infos to find out-of-order packets and setting up custom columns (SEQ#, NEXTSEQ#, ACK#) for deeper packet analysis. It explains the significance of out-of-order packets appearing in close proximity as an indicator of packet loss and retransmissions.
π Lecture Summary
Step 1: Open the capture file
Open the file tr-general101d.pcapng in Wireshark.
Step 2: Access Expert Infos
On the Status Bar, click the Expert Infos button. This opens the Expert Infos dialog window.
π‘ Why this matters: Expert Infos provides a summary of all Wireshark-detected anomalies, including out-of-order packets, without manually scanning the packet list.
Step 3: Find Out-of-Order Warnings
Click the Warnings tab. Expand the Out-of-Order segment section to see all out-of-order packets.
π Definition β Out-of-Order segment: A packet whose Sequence Number (SEQ#) is lower than the Expected Sequence Number (i.e., the Next Sequence Number of the previous packet), or whose SEQ# is less than previously seen SEQ# values.
Click on the first entry β Packet 4,206. Then click the Close button to return to the main Wireshark window.
π Example: In this capture, Packet 4,206 and Packet 32,018 are identified as out-of-order packets. The remaining 6 packets belong to a group of out-of-order packets in close proximity.
Interpreting Out-of-Order Proximity
If you find multiple Out-of-Order packets in close proximity, then it is likely that a set of packets have been lost. These packets are Retransmissions that arrived within 3 ms.
π‘ Why this matters: A cluster of out-of-order packets within a short time window (~3 ms) strongly suggests packet loss followed by rapid retransmission, not just network reordering.
Step 4: Create Custom Columns
If you have previously created SEQ#, NEXTSEQ#, and ACK# columns, right-click on any column heading and display them. Otherwise, create them as follows:
- Select the Sequence number field in the TCP header of any packet.
- Right-click and choose Apply as a Column.
- Rename the column as SEQ# by right-clicking on the column and selecting Edit Column Details.
π Example: Creating the SEQ# column allows you to manually verify out-of-order conditions by comparing the SEQ# of each packet against the NEXTSEQ# of the previous packet.
Step 5: Clear the filter
When you are done analyzing, click the Clear button to remove the filter.
β Key Takeaways
Out-of-order packets in Wireshark are detected through Expert Infos under the Warnings tab, specifically in the Out-of-Order segment section. Multiple out-of-order packets appearing in close proximity (within 3 ms) strongly indicate actual packet loss, where the out-of-order packets are retransmissions of lost packets. To manually verify this, you must create SEQ#, NEXTSEQ#, and ACK# columns using the Apply as a Column feature on TCP header fields. The key diagnostic pattern is a cluster of out-of-order packets rather than isolated ones.
π§ Quick Revision Questions
- What is the first step to find out-of-order packets in Wireshark?
- In which tab of the Expert Infos dialog do you find Out-of-Order segments?
- What does it mean if multiple out-of-order packets appear in close proximity (within 3 ms)?
- How do you create a custom SEQ# column in Wireshark?
- Which two packet numbers are specifically identified as out-of-order in this lecture?
Here is the summary of Lecture 154, formatted exactly as requested.
π Lecture 154 β Wireshark Lab 55
π Overview: This is a hands-on lab lecture where students learn how to use Wireshark to identify and count fast retransmission packets. The lecture reinforces the theory of fast retransmissions by applying a specific display filter to a real packet capture file, teaching students how to diagnose packet loss from a network analysis perspective.
ποΈ Topics Covered
This lecture guides students through a single, practical Wireshark exercise. The topics covered are opening a specific packet capture file (tr-general101d.pcapng) and applying the display filter tcp.analysis.fast_retransmission to isolate and count fast retransmission packets. The core skill being taught is how to translate theoretical knowledge about fast retransmissions into a practical network analysis technique.
π Lecture Summary
Topic 154: Wireshark Lab 55
This topic provides step-by-step instructions for a lab exercise to identify fast retransmission packets using Wireshark. The goal is to put into practice the concepts of fast retransmissions and duplicate ACKs by analyzing a real network capture.
Step 1: Open tr-general101d.pcapng.
The first step is to load the provided packet capture file into Wireshark. This file contains the network traffic that will be analyzed.
Step 2: Enter the filter tcp.analysis.fast_retransmission in the display filter area. Click Apply.
The core of the lab is to use Wiresharkβs expert analysis feature. The tcp.analysis.fast_retransmission filter is a built-in Wireshark display filter that is not a simple protocol field value, but rather an expert indicator. When applied, Wireshark will automatically evaluate all TCP segments in the capture and only show those that it identifies as a fast retransmission. This allows the user to count the number of packets suspected to be part of a fast retransmission event.
π Definition β Fast Retransmission (Wireshark context): A packet identified by Wireshark's expert analysis engine based on the presence of at least three duplicate ACKs and a retransmitted segment that matches the sequence number of the missing segment. π‘ Why this matters: This lab transforms the theoretical cause of fast retransmissions (three duplicate ACKs) into a practical, verifiable, and countable event in network traffic, which is a critical skill for network troubleshooting.
β Key Takeaways
The single, critical task in this short lab is learning to use the Wireshark display filter tcp.analysis.fast_retransmission to automatically detect and isolate fast retransmission packets. This filter is an expert analysis tool that leverages Wiresharkβs internal logic, not a simple packet header field match. Applying this filter is the primary method for counting fast retransmission events in a capture file. For the exam, you must know this specific filter and its function to identify packet loss as seen by the sender.
π§ Quick Revision Questions
- What is the exact display filter used in this lab to find fast retransmission packets?
- What is the name of the packet capture file used in this lab?
- Is
tcp.analysis.fast_retransmissiona simple field filter or an expert analysis filter? - What network event do fast retransmission packets indicate?
- After applying the filter, what is the main action a Wireshark user can perform to analyze the results?
π Lecture 155 β Wireshark Lab 56
π Overview: This lecture demonstrates how to identify and analyze Fast Retransmission packets using Wireshark's Expert Infos feature. It is critical for understanding TCP retransmission behavior and troubleshooting network performance issues.
ποΈ Topics Covered
The lecture covers detecting Fast Retransmissions via the Wireshark Status Bar, expanding the [SEQ/ACK analysis] section (cyan color), understanding that Fast Retransmission is a subset of Retransmission in Expert Infos, clearing filters after analysis, opening the trace file tr-general101d.pcapng, and navigating the Expert Infos Notes tab to locate Fast Retransmission entries starting at Packet 12,035.
π Lecture Summary
Detecting Fast Retransmissions in the Status Bar
In the trace file, Wireshark detects two Fast Retransmissions as indicated by the Status Bar. This is the first visual clue that TCP is retransmitting segments before the retransmission timer expires.
π Definition β Fast Retransmission: A TCP mechanism that triggers retransmission of a lost segment after receiving three duplicate ACKs, without waiting for the retransmission timeout. π‘ Why this matters: Fast Retransmission speeds up recovery from packet loss, improving TCP throughput.
Expanding the [SEQ/ACK analysis] Section
Step 3 instructs to expand the [SEQ/ACK analysis] section on one of the Fast Retransmission packets. Wireshark colors this area cyan, matching the color of the Expert Infos Notes. There are two Expert Infos indications marked on this single packet: the frame is labeled both a Fast Retransmission and a Retransmission β meaning Fast Retransmission is a specific type of Retransmission.
π Example: Packet marked as both "Fast Retransmission" and "Retransmission" β the former is a subset of the latter.
Clearing the Filter
Step 4: Click the Clear button to remove any applied filter after finishing the analysis. This ensures the display returns to all packets.
Opening the Trace File and Using Expert Infos
Topic 155: Wireshark Lab 56 β This topic focuses on finding fast retransmission packets with Expert Infos in Wireshark.
Step 1: Open tr-general101d.pcapng.
Step 2: Click the Expert Infos button on the Status Bar.
Step 3: Click the Notes tab. Scroll through the list. As you find the Fast Retransmissions section, expand it and click on the first entry, Packet 12,035. This navigates directly to the first Fast Retransmission packet in the trace.
β Key Takeaways
Fast Retransmissions are detectable through Wireshark's Status Bar and Expert Infos Notes tab. Each Fast Retransmission packet has two Expert Infos labels: "Fast Retransmission" and "Retransmission," with the former being a subset of the latter. The [SEQ/ACK analysis] section is color-coded cyan for these events. The trace file for this lab is tr-general101d.pcapng, and the first Fast Retransmission packet is Packet 12,035. Always remember to clear filters after analysis.
π§ Quick Revision Questions
- What two Expert Infos indications are marked on a Fast Retransmission packet?
- What color does Wireshark use for the [SEQ/ACK analysis] section in Fast Retransmissions?
- Which trace file is used in this lab?
- What is the packet number of the first Fast Retransmission entry in the Notes tab?
- Why is it important to click the Clear button after analyzing filters?
π Lecture 156 β Causes of Retransmissions
π Overview: This lecture examines how Wireshark identifies retransmissions and their underlying causes. It uses a detailed packet capture analysis to show the relationship between duplicate ACKs, fast retransmission, and the timing involved in TCP recovery. Understanding these mechanisms is critical for diagnosing network performance issues.
ποΈ Topics Covered
The lecture covers the observation of 808 Duplicate ACKs before Fast Retransmission, how to display SEQ#, NEXTSEQ#, and ACK# columns in Wireshark, the TCP Delta column showing retransmission timing within 20 ms of the last Duplicate ACK, and the definition of what Wireshark considers a Retransmission packet.
π Lecture Summary
We can observe that there are 808 Duplicate ACKs before the Fast Retransmission packet. Return to the main Wireshark window after clicking the Close button. Step 4: If you have created SEQ#, NEXTSEQ# and ACK# columns, then you can display them by right-clicking on a column and selecting them from Displayed Columns.
The packet capture analysis reveals 808 Duplicate ACKs were sent before the Fast Retransmission occurred. After closing the dialog box, you return to the main Wireshark window. To view key TCP sequence numbers, you can create SEQ#, NEXTSEQ#, and ACK# columns by right-clicking on an existing column and selecting them from the Displayed Columns menu.
From the TCP Delta column, we can see that the Fast Retransmission occurred within 20 ms of the last Duplicate ACK. If you consider time, you will find that only about 465 ms have passed between when packet with sequence number 9,164,761 went missing and when Fast Retransmission was initiated. Although there were 808 Duplicate ACKs, but this Β½βsecond delay would be unnoticeable by the user.
The TCP Delta column shows the Fast Retransmission occurred within 20 ms of the last Duplicate ACK. Only about 465 ms elapsed between the loss of packet with sequence number 9,164,761 and the initiation of Fast Retransmission. Despite the 808 Duplicate ACKs, this half-second delay would be unnoticeable to the user. π‘ Why this matters: This demonstrates that even a large number of duplicate ACKs can result in a very short, user-transparent recovery time.
Topic 156: Causes of Retransmissions
This topic describes retransmissions and their causes.
Wireshark considers a packet to be a Retransmission if the segment contains data or has the SYN or FIN bits set to 1. Sequence number is not advanced by the segment.
Wireshark identifies a packet as a Retransmission when the segment either contains data or has the SYN or FIN bits set to 1. Crucially, the sequence number is not advanced by the segment β meaning it carries the same sequence number as a previously transmitted packet.
π Definition β Retransmission: A packet that Wireshark labels as a retransmission if the segment contains data, or has the SYN or FIN bit set to 1, and the sequence number is not advanced by the segment.
π Formula: Retransmission detection condition: (segment contains data OR SYN=1 OR FIN=1) AND (sequence number not advanced)
π Example: Packet with sequence number 9,164,761 was lost. The receiver sent 808 Duplicate ACKs for this missing sequence number. The sender then retransmitted packet with sequence number 9,164,761 within 20 ms of the last Duplicate ACK, and about 465 ms after the original packet was lost.
β Key Takeaways
Wireshark identifies retransmissions by checking if a segment contains data or has SYN/FIN bits set to 1, with no advancement of the sequence number. In the example, 808 Duplicate ACKs were sent before Fast Retransmission was triggered, yet only 465 ms passed from packet loss to recovery. The TCP Delta column shows the retransmission occurred within 20 ms of the last Duplicate ACK. This half-second delay is imperceptible to the user, proving TCP's fast recovery is effective. You can display SEQ#, NEXTSEQ#, and ACK# columns by right-clicking and selecting from Displayed Columns.
π§ Quick Revision Questions
- What criteria does Wireshark use to identify a packet as a Retransmission?
- How many Duplicate ACKs were observed before the Fast Retransmission in the example?
- What does the TCP Delta column reveal about the timing of the Fast Retransmission relative to the last Duplicate ACK?
- How much time elapsed between the loss of packet sequence number 9,164,761 and the Fast Retransmission?
- Why is the half-second delay from packet loss to retransmission considered unnoticeable to the user?
π Lecture 157 β Wireshark Lab 57
π Overview: This lecture explains the role of the Retransmission Time Out (RTO) timer in TCP and how standard retransmissions differ from fast retransmissions. It then provides a practical Wireshark lab to filter and count retransmission packets, with guidance on excluding fast retransmissions to isolate standard ones.
ποΈ Topics Covered
The lecture begins by distinguishing when duplicate ACKs do not trigger retransmission, leading to an RTO. It defines the RTO timer, its calculation based on round-trip time, and its purpose to ensure data delivery even if the TCP peer stops ACKing. Next, it describes what causes retransmissions when the RTO expires. Finally, it presents Wireshark Lab 57, including steps to apply the tcp.analysis.retransmission filter and exclude fast retransmissions.
π Lecture Summary
Why Duplicate ACKs Have Not Triggered Retransmission
Duplicate ACKs have not triggered a retransmission. The segment arrives more than 3 ms later than the previous packet with a higher sequence number. A Retransmission Time Out (RTO) at a sender triggers Standard Retransmissions. The RTO timer is used to ensure data delivery continues even if the TCP peer stops communicating (with ACKs). Each TCP host calculates and maintains an RTO timer. This timer value is based on the round trip time learned through previous data transmissions and related acknowledgments. The RTO value consistently changes through the conversation.
π‘ Why this matters: The RTO is a dynamic timer that adapts to network conditions, and understanding when it fires (instead of fast retransmit) helps diagnose network delays or complete communication failures.
π Definition β Retransmission Time Out (RTO): A timer calculated by each TCP host based on observed round-trip times; if it expires without receiving an ACK for a sent data packet, the sender retransmits the unacknowledged packet.
What Causes Retransmissions?
A TCP host begins counting down the RTO when it sends a data packet. The sender retransmits the unacknowledged data packet if the RTO timer expires without receiving an ACK for that data packet. The sender has no idea whether the original packet was lost or the acknowledgment was lost. The sender just knows that there is some problem because it did not receive an ACK within the RTO.
π Concept: RTO expiration β Standard Retransmission. The sender cannot distinguish between a lost data packet and a lost ACK.
Topic 157: Wireshark Lab 57
This topic uses a filter to count retransmission packets in Wireshark. Applying tcp.analysis.retransmission in Wireshark as a filter for Retransmissions will also display Fast Retransmissions. You need to exclude Fast Retransmissions in the filter if you are interested in seeing packets that are only labeled as standard Retransmissions.
Step 1: Open tr-general101d.pcapng.
Step 2: Enter the filter tcp.analysis.retransmission in the display filter area. Click Apply.
π Important Distinction: The tcp.analysis.retransmission filter shows both standard and fast retransmissions. To see only standard retransmissions, you must explicitly exclude fast retransmissions from the filter.
β Key Takeaways
The RTO timer is a critical fallback mechanism that ensures data delivery when TCPβs fast retransmit mechanism (triggered by duplicate ACKs) fails to act. An RTO expires when no ACK is received within a dynamically calculated time window, and the sender blindly retransmits without knowing whether the data or ACK was lost. In Wireshark, the tcp.analysis.retransmission filter captures all retransmissions, so isolating standard RTO-triggered ones requires removing fast retransmissions. For the exam, remember that RTO is based on round-trip time measurements, that it constantly changes, and that it is the last-resort mechanism to recover lost segments.
π§ Quick Revision Questions
- What event at the sender triggers a standard retransmission?
- What information does the sender lack when an RTO expires?
- Why does the RTO timer value change throughout a TCP conversation?
- What Wireshark filter displays both standard and fast retransmissions?
- How can you modify the display filter to show only standard retransmissions (excluding fast retransmissions)?
π Lecture 158 β Wireshark Lab 58
π Overview: This lecture demonstrates how to identify and filter retransmission packets using Wireshark's Expert Infos feature. It explains how to distinguish between regular retransmissions and Fast Retransmissions, and how to analyze sequence numbers to understand the timing of retransmission events.
ποΈ Topics Covered
The lecture covers detecting retransmissions from the Status Bar, filtering between retransmissions and Fast Retransmissions, using the Expert Infos dialog to explore retransmission packets, creating and using SEQ# columns, and setting time references to analyze packet timing relative to retransmissions.
π Lecture Summary
Retransmission Detection from Status Bar
The Status Bar in Wireshark provides a quick overview of detected retransmissions. In the trace file, Wireshark detected 580 Retransmissions, which includes two Fast Retransmissions.
π Definition β Retransmission: A packet that is sent again because the original packet was lost or corrupted in transmission. π Definition β Fast Retransmission: A retransmission that occurs before the normal retransmission timer expires, triggered by receiving duplicate ACKs.
π Example: Filter tcp.analysis.retransmission && !tcp.analysis.fast_retransmission shows 578 packets β removing the two Fast Retransmissions from the view.
π‘ Why this matters: Distinguishing between regular retransmissions and Fast Retransmissions helps diagnose different types of network problems (e.g., packet loss vs. out-of-order delivery).
Finding Retransmission Packets with Expert Infos
The Expert Infos dialog provides a structured view of Wireshark's analysis of the trace file, including retransmission events.
Step 1: Open tr-general101d.pcapng.
Step 2: Click the Expert Infos button on the Status Bar.
Step 3: Click the Notes tab, scroll through the list, expand the Retransmissions section, and click on Packet 12,259. This navigates to the Main window.
Step 4: Close the Expert Infos dialog.
Creating SEQ# and ACK# Columns
To analyze retransmission timing, you need to create columns for Sequence Number (SEQ#) and Next Sequence Number (NEXTSEQ#).
Step 1: Right-click on any column heading and display SEQ#, NEXTSEQ#, and ACK# columns if previously created. Otherwise, create them. Step 2: Select the Sequence number field in the TCP header of a packet. Step 3: Right-click and select Apply as a Column. Step 4: Rename the column as SEQ# by right-clicking on the column and selecting Edit Column Details.
π Definition β Set Time Reference (toggle): A Wireshark feature that sets the selected packet as time zero (0.000), making it easier to measure relative times of subsequent packets.
π Example: Scroll up to find Packet 12,246 β a data packet from 10.9.9.9 with the highest Sequence No. field value at that point in the trace. Right-click on Packet 12,246 and select Set Time Reference (toggle) to make it the reference point.
π‘ Why this matters: Setting a time reference on the packet with the highest sequence number before the retransmission helps calculate how quickly the retransmission occurred, which is crucial for understanding network performance.
β Key Takeaways
The most critical skills from this lecture are: (1) using the Status Bar to quickly see retransmission counts; (2) filtering retransmissions to exclude Fast Retransmissions for more accurate analysis; (3) navigating to retransmission packets through Expert Infos for detailed inspection; (4) creating and using SEQ#, NEXTSEQ#, and ACK# columns to analyze sequence numbers; (5) setting time references to measure relative timing of retransmission events. Students must be able to distinguish between regular retransmissions and Fast Retransmissions, and explain why a packet with the highest sequence number is chosen as the time reference point.
π§ Quick Revision Questions
- How many total Retransmissions are detected in the Status Bar, and how many of these are Fast Retransmissions?
- What filter removes Fast Retransmissions from the display, and how many packets match this filter?
- Which packet in the Expert Infos Notes tab is selected to navigate to the Main window?
- What is the purpose of setting a time reference on Packet 12,246?
- Why is Packet 12,246 chosen as the reference packet rather than a later or earlier packet?
π Lecture 159 β Causes of ACKed Unseen Segments
π Overview: This lecture explains the concept of ACKed Unseen Segments in Wireshark, a condition where Wireshark observes an acknowledgment (ACK) but did not capture the corresponding data packet being acknowledged. Understanding this phenomenon is crucial for network troubleshooting, as it often indicates packet loss or capture problems rather than actual network errors.
ποΈ Topics Covered
The lecture defines what an ACKed Unseen Segment is, explains how Wireshark tracks sequence numbers and acknowledgment numbers to detect missing packets, and then covers the primary cause of this condition: problems during the capture process, specifically when a switch is oversubscribed during switch port spanning.
π Lecture Summary
Topic 159: Causes of ACKed Unseen Segments
What is ACKed Unseen Segment? When Wireshark sees an ACK, but it did not see the data packet that is being acknowledged, it calls it an ACK Unseen Segment. For each host, Wireshark keeps a track of sequence number, next sequence number, and acknowledgment number values. Wireshark also keeps a track of a "Maximum Sequence Number to be ACKed" (maxseqtobeacked) value. This value gets updated as data is received. If Wireshark sees an ACK to acknowledge a data packet that has a higher Sequence Number field value than maxseqtobeacked, then it shows that it has missed the data packet that is being ACKed. For example, let's assume that Wireshark is running on a client which is communicating with a server. An ACK being sent to acknowledge all sequence numbers up to 9,380 has been captured.
π Definition β ACKed Unseen Segment: A Wireshark indicator that appears when an acknowledgment packet is captured, but the data packet being acknowledged was not captured.
π‘ Why this matters: This condition does not necessarily mean the data packet was lost on the network; it often means Wireshark never received it due to capture limitations.
Causes of ACKed Unseen Segment: Problems occurring during the capture process can cause ACKed Unseen Segments. If the switch is oversubscribed when you are using switch port spanning, then it is dropping packets that should have been forwarded to Wireshark.
π Formula: Cause β Switch oversubscription + Switch port spanning β Dropped packets β Wireshark misses data packets β ACKed Unseen Segment
π‘ Why this matters: The root cause is typically a capture infrastructure problem, not a network communication failure.
β Key Takeaways
ACKed Unseen Segments occur when Wireshark sees an acknowledgment for a data packet it never captured. Wireshark detects this by comparing the acknowledgment's sequence number against its internally tracked "Maximum Sequence Number to be ACKed" (maxseqtobeacked) value. The primary cause discussed in this lecture is problems during the capture process, specifically when a switch becomes oversubscribed while using switch port spanning, causing it to drop packets before they reach Wireshark.
π§ Quick Revision Questions
- What does Wireshark call it when it sees an ACK but not the corresponding data packet?
- What internal value does Wireshark track to detect that it missed a data packet being acknowledged?
- What is the main cause of ACKed Unseen Segments discussed in this lecture?
- How does a switch being oversubscribed lead to ACKed Unseen Segments when using switch port spanning?
- Does an ACKed Unseen Segment always mean the data packet was lost on the network?
π Lecture 160 β Wireshark Lab 59
π Overview: This lecture demonstrates how to use a specific Wireshark display filter to identify and count ACKed Unseen Segment warnings in a packet capture. It explores the cause of this warning, focusing on asymmetric routing as a key network phenomenon. Understanding this filter is crucial for diagnosing network performance issues where data and acknowledgments travel different paths.
ποΈ Topics Covered
This lecture covers the concept of ACKed Unseen Segments in Wireshark, the role of asymmetric routing in causing these warnings, and a step-by-step lab procedure to apply the tcp.analysis.ack_lost_segment filter and view the count in the Status Bar.
π Lecture Summary
B) Asymmetric routing can cause ACKed Unseen Segments
Asymmetric routing occurs when data is transmitted along one network path while the corresponding ACKs (acknowledgments) travel along a different path. In this scenario, Wireshark captures the ACKs but fails to capture the original data segments they acknowledge. This results in a warning that the segments were "unseen" or lost from the captureβs perspective, even though they may have actually reached the destination via an alternate route.
π‘ Why this matters: Asymmetric routing is common in complex networks and can generate false positive warnings in Wireshark, making it important to recognize this cause before diagnosing actual packet loss.
π Definition β Asymmetric routing: A network condition where data packets and their corresponding acknowledgment packets traverse different paths between source and destination.
Step 1: Open tr-badcapture.pcapng
The lab begins by opening the provided capture file named tr-badcapture.pcapng. This file contains network traffic that is expected to produce ACKed Unseen Segment warnings.
Step 2: Enter the filter expression
The student enters the display filter expression tcp.analysis.ack_lost_segment into the Wireshark display filter area and clicks Apply. This filter isolates all packets that are associated with the ACKed Unseen Segment warning.
π Formula: tcp.analysis.ack_lost_segment β This filter shows only packets where Wireshark detected an acknowledgment for a segment that was not seen in the capture.
π Example: After applying the filter to tr-badcapture.pcapng, the Wireshark Status Bar displays the message "Displayed: 24 packets (24β¦)". This confirms that Wireshark detected exactly 24 ACKed Unseen Segments in the capture.
β Key Takeaways
The critical point is that ACKed Unseen Segments do not always indicate actual packet loss; they can result from asymmetric routing where data and ACKs take different network paths. The specific filter tcp.analysis.ack_lost_segment is used to isolate these warnings, and the count appears in the Wireshark Status Bar. In this lab, exactly 24 such segments were identified. Recognizing asymmetric routing as a common cause helps avoid misinterpreting the warning as real data loss.
π§ Quick Revision Questions
- What does the Wireshark filter
tcp.analysis.ack_lost_segmentspecifically detect? - How does asymmetric routing cause an ACKed Unseen Segment warning?
- In the lab, what was the exact number of ACKed Unseen Segments displayed after applying the filter?
- Where in the Wireshark interface does the count of filtered packets appear?
- Why might an ACKed Unseen Segment warning be a false positive for actual packet loss?
π Lecture 161 β Wireshark Lab 60
π Overview: This lecture demonstrates how to identify ACKed Unseen Segment indications in Wireshark using the Expert Infos tool. It provides a step-by-step procedure to locate packets where an acknowledgment (ACK) refers to a segment that was not captured, which is common at capture start. Understanding this helps in diagnosing packet capture issues and validating TCP sequence analysis.
ποΈ Topics Covered
The lecture covers opening a bad capture file (tr-badcapture.pcapng), accessing the Expert Infos button on the Status Bar, navigating to the Warnings tab to find "ACKed segment that wasn't captured" entries, and examining Packet 15 while displaying SEQ#, NEXTSEQ#, and ACK# columns for analysis.
π Lecture Summary
Using Expert Infos to Find ACKed Unseen Segments
In this step, you open a specific capture file and use the Expert Infos feature to locate warnings about ACKed Unseen Segments. These are packets where an acknowledgment references a data segment that Wireshark did not capture. The procedure ensures you can identify such anomalies quickly.
π Definition β ACKed Unseen Segment: A TCP packet that acknowledges a sequence number belonging to a segment that was not captured in the trace, often occurring at the start of a capture when a connection was already established.
Step 1: Open tr-badcapture.pcapng.
Step 2: Click the Expert Infos button on the Status Bar.
Step 3: Click the Warnings tab. Expand the section with title ACKed segment that wasn't captured (common at capture start).
Step 4: Click on the first entry, Packet 15, and then click the Close button. Now go to the main Wireshark window. Display the SEQ#, NEXTSEQ#, and ACK# columns.
π Example: In the provided capture, Packet 15 is identified as the first occurrence of an ACKed Unseen Segment warning. After closing Expert Infos, you would see the sequence numbers: SEQ# (the segment's own sequence number), NEXTSEQ# (the next expected sequence number), and ACK# (the acknowledgment number pointing to the unseen segment).
π‘ Why this matters: ACKed Unseen Segments are common at capture start because the capture begins after the TCP handshake. Recognizing them prevents false conclusions about missing retransmissions or duplicate ACKs.
β Key Takeaways
Students must remember that the Expert Infos tool provides a quick summary of packet anomalies, including warnings. For this lecture, the critical skill is locating ACKed Unseen Segment warnings under the Warnings tab, expanding the specific entry, and selecting the first packet (Packet 15) for detailed analysis. Displaying SEQ#, NEXTSEQ#, and ACK# columns is essential to visually confirm the acknowledgment sequence numbers. This warning is normal at capture start and indicates the capture began after the connection was established, not a network error.
π§ Quick Revision Questions
- What is the file name used in this lectureβs lab?
- Which tab in Expert Infos contains the βACKed segment that wasnβt capturedβ warning?
- What packet number is identified as the first entry of this warning?
- After closing Expert Infos, which three columns must be displayed to examine the TCP sequence numbers?
- Why is an ACKed Unseen Segment considered common at capture start?
π Lecture 163 β Wireshark Lab 61
π Overview: This is a hands-on lab that teaches you how to use a Wireshark display filter to identify and count Keep Alive and Keep Alive ACK packets in a packet capture file. Understanding how to filter these packets is essential for troubleshooting dead TCP connections and analyzing idle connection behavior.
ποΈ Topics Covered
This lab focuses on a single practical exercise: using the display filter tcp.analysis.keep_alive || tcp.analysis.keep_alive_ack on the provided tr-keepalives.pcapng capture file to isolate and count Keep Alive related packets in Wireshark.
π Lecture Summary
Wireshark Lab 61: Filtering Keep Alive Packets
This is a step-by-step lab that demonstrates how to apply a specific display filter in Wireshark. The goal is to count Keep Alive and Keep Alive ACK packets within a given trace file. You must follow the exact steps in order.
Step 1: Open the file tr-keepalives.pcapng in Wireshark.
Step 2: In the display filter area (the bar at the top of the main window), enter the following filter expression exactly:
tcp.analysis.keep_alive || tcp.analysis.keep_alive_ack
Step 3: Click the Apply button (or press Enter) to execute the filter. Wireshark will then show only the packets that are either Keep Alives or Keep Alive ACKs. The status bar at the bottom of the Wireshark window will display the total count of packets matching this filter.
π Definition β Keep Alive Probe: An ACK packet (empty or with 1 byte of data) used to detect dead connections. Its sequence number is 1 less than the next expected sequence number. π Definition β Keep Alive ACK: The acknowledgment packet sent in response to a Keep Alive probe. π Example: If the current Sequence Number is 100, a Keep Alive packet will have SEQ=99. The recipient's ACK for that probe is the Keep Alive ACK. π‘ Why this matters: Filtering these packets allows you to quickly identify all Keep Alive activity in a capture, helping you diagnose why a connection is being kept alive or if a peer is unresponsive.
β Key Takeaways
The most critical thing to remember is the exact display filter syntax: tcp.analysis.keep_alive || tcp.analysis.keep_alive_ack. You must use the double pipe (||) to include both packet types. The lab uses the file tr-keepalives.pcapng. The filter directly counts all Keep Alive probes and their corresponding ACKs in one view. This is a practical skill for network troubleshooting β knowing how to isolate these small, periodic packets helps identify dead peer detection and connection keep-alive behavior.
π§ Quick Revision Questions
- What is the exact display filter used in Lab 61 to count Keep Alive and Keep Alive ACK packets?
- What is the name of the pcapng file that must be opened for this lab?
- In Wireshark, where do you type the display filter?
- After applying the filter, what does the status bar at the bottom of Wireshark show?
- What does the double pipe (
||) operator do in the display filter for this lab?
π Lecture 164 β Wireshark Lab 62
π Overview: This lecture explores how to identify Keep Alive and Keep Alive ACK packets in Wireshark, both by filtering and through the Expert Infos tool. Understanding these packets is essential for network troubleshooting, as they maintain idle TCP connections and prevent timeouts.
ποΈ Topics Covered
The lecture begins with a filtering method to isolate Keep Alive packets using a display filter, followed by examining the TCP Delta column to verify Keep Alive Time values. It then demonstrates using Expert Infos to locate Keep Alives and Keep Alive ACKs, explaining their purpose in checking for dead TCP peers and avoiding connection timeouts.
π Lecture Summary
Find Keep Alive Packets with a Filter
We can see that only two packets match the filter. Step 3: Display TCP Delta column if it is hidden. Otherwise, create it. If you look at the TCP Delta before Packet 61, then you can see that 10.2.122.80 has a 300 second Keep Alive Time value. Packet 62 is the Keep Alive ACK packet. Step 4: Remove the filter by clicking the Clear button.
π Definition β Keep Alive Packet: A TCP packet sent to check if a peer is still reachable and to prevent idle connections from timing out. π Definition β Keep Alive ACK: The acknowledgment sent in response to a Keep Alive packet, confirming the peer is still alive.
π Example: Packet 61 is a Keep Alive packet from 10.2.122.80. The TCP Delta before this packet shows a 300 second Keep Alive Time. Packet 62 is the corresponding Keep Alive ACK.
π‘ Why this matters: Keep Alives and Keep Alive ACKs are normal behavior β they are not indications of problems β but they help prevent unnecessary disconnections of idle TCP sessions.
Topic 164: Wireshark Lab 62
In this topic, we find Keep Alive/Keep Alive ACK Packets with Expert Infos in Wireshark. Keep Alives and Keep Alive ACKs are typically used to check for dead TCP peers and avoid time out of idle connections. They are not indications of problems.
Step 1: Open tr-keepalives.pcapng. Step 2: Click the Expert Infos button on the Status Bar. Step 3: Click the Notes tab. You can see Keep Alives and Keep Alive ACKs. Expand the Keep Alive and Keep Alive ACK lines. You can see Packets 61 and 62 listed.
β Key Takeaways
Keep Alives and Keep Alive ACKs are normal TCP packets used to verify peer liveliness and prevent idle connection timeouts β they are not error indicators. In Wireshark, you can find them either by applying a display filter and checking the TCP Delta column for the Keep Alive Time value (e.g., 300 seconds), or by using Expert Infos β Notes tab, which conveniently lists all such packets. Only two packets (61 and 62) are typically involved: the Keep Alive and its ACK.
π§ Quick Revision Questions
- What is the primary purpose of Keep Alive and Keep Alive ACK packets?
- What value in the TCP Delta column is associated with Packet 61 in this lab?
- How many packets match the filter for Keep Alives in this capture?
- Which tab under Expert Infos displays Keep Alive and Keep Alive ACK packets?
- Are Keep Alives an indication of network problems? Why or why not?
π Lecture 165 β Wireshark Lab 63
π Overview: This lecture demonstrates how to identify TCP Keep Alive packets used in Zero Window Conditions using Wireshark. It explains the relationship between the Window Size field, Zero Window conditions, and the role of Keep Alive packets when a receiverβs buffer is full.
ποΈ Topics Covered
This lecture covers identifying Keep Alive packets in a Zero Window condition using Wiresharkβs Expert Infos and packet analysis. It explains how the Window Size field can drop to zero when a receiving application is slow, and how hosts use Keep Alives instead of Window Zero Probes. The lecture also shows that Keep Alive ACK responses are absent in this scenario, and walks through opening a specific pcapng file, accessing the Notes tab, and expanding the Keep-Alive section to locate the first Keep Alive packet.
π Lecture Summary
Step 4: Click on the Keep Alive entry (Packet 61)
After following Steps 1-3 from the previous section, you click on Packet 61 in the Keep-Alive section of the Expert Infos window. This takes you to the main Wireshark window where you close the Expert Infos window. You then display the SEQ#, NEXTSEQ#, and ACK# columns. For Packet 61, you observe that the Sequence Number field value has been decremented by 1 β from 10,943 to 10,942.
π‘ Why this matters: The decremented sequence number is a key signature of a Keep Alive packet β it βpretendsβ to retransmit the last byte to check if the peerβs window has reopened.
Topic 165: Wireshark Lab 63
This topic focuses on identifying Keep Alive Packets used in Zero Window Conditions in Wireshark. The two sides of a TCP conversation advertise their receive buffer space in the Window Size Value field. This is a 2-byte field whose maximum value can be 65,535 bytes. Over todayβs high-speed links, if a receiving application is slow in pulling data out of the receive buffer, itβs not unusual that the advertised Window Size value can drop to zero β a Zero Window Condition. Hosts can send TCP Keep Alives in place of Window Zero Probes. When a TCP host sends a Keep Alive to a peer that is advertising a Zero Window condition, you will not see Keep Alive ACK responses.
π Definition β Zero Window Condition: A TCP condition where the advertised Window Size field drops to zero because the receiving application is slow in pulling data out of the receive buffer. π Definition β Keep Alive Packet: A TCP packet sent by a host to check if a peerβs window has reopened, used in place of Window Zero Probes. π Example: In the tr-youtubebad.pcapng capture (Step 1), Packet 61 shows a Keep Alive where the Sequence Number is decremented from 10,943 to 10,942, indicating the attempt to probe the Zero Window condition.
Step 1: Open tr-youtubebad.pcapng
Open the provided capture file tr-youtubebad.pcapng in Wireshark.
Step 2: Click the Expert Infos button on the Status Bar and then click the Notes tab
Click the Expert Infos button on the Status Bar and then click the Notes tab. During a successful keep alive process, hosts exchange Keep Alives and Keep Alive ACKs. In this case, either the peer is dead or this is not a standard keep alive process.
Step 3: Expand the Keep-Alive section
If you expand the Keep-Alive section, you will find Packet 2,721, the first Keep Alive listed. Click on it and then click the Close button to return to the main Wireshark window.
π Definition β Keep Alive ACK: The acknowledgment response expected during a successful keep alive process β absent in this capture. π Example: In Packet 2,721, the first Keep Alive in the capture, no Keep Alive ACK is observed, indicating either the peer is dead or a non-standard keep alive process.
β Key Takeaways
The key takeaway is that Keep Alive packets in Wireshark are identified by a decremented Sequence Number (e.g., from 10,943 to 10,942), distinguishing them from normal retransmissions. These packets are used in Zero Window Conditions where the Window Size field drops to zero due to a slow receiving application. Unlike successful keep alive processes, in this scenario no Keep Alive ACK responses are seen, suggesting the peer may be dead or the process is non-standard. The lecture demonstrates practical Wireshark steps β opening tr-youtubebad.pcapng, using the Expert Infos Notes tab, and expanding the Keep-Alive section to locate Packet 2,721. Remember that Keep Alives replace Window Zero Probes when a host probes a receiver with a zero window.
π§ Quick Revision Questions
- What field in the TCP header advertises the receive buffer space, and what is its maximum value in bytes?
- What happens to the Sequence Number field in a TCP Keep Alive packet, as seen in Packet 61 of this lecture?
- In a Zero Window condition, what do hosts send in place of Window Zero Probes?
- What is missing from this capture that would be present in a successful keep alive process?
- Which specific packet (number) is the first Keep Alive listed in the captureβs Keep-Alive section?
π Lecture 166 β Causes of Reused Ports
π Overview: This lecture explains the concept of reused ports in TCP communications. It clarifies when port reuse is harmless versus when it causes significant communication delays, focusing on the critical condition that the previous TCP connection must be properly terminated.
ποΈ Topics Covered
The lecture covers the definition of reused ports, the distinction between problematic and non-problematic reuse scenarios, and the essential condition of proper TCP connection termination (via FINs or RSTs). It also references previous content about Keep Alive timers to clarify their purpose.
π Lecture Summary
Topic 166: Causes of Reused Ports
Reused ports occur when a client attempts to establish a new TCP connection using the same source port number as a previous connection. The critical factor determining whether this causes problems is whether the previous TCP connection was properly terminated.
When a previous connection is terminated (through TCP FINs or RSTs), reusing the port number is generally harmless. For example, a client establishes a TCP connection with a server using source port 1026 and destination port 80. After that connection properly closes, establishing a new connection with the same source port 1026 is not an issue.
However, reused ports become a significant problem when the previous connection has not been terminated. In the same example, if the client tries to establish a new connection with source port 1026 while the original connection to port 80 is still active, this creates confusion and can cause significant delays in communications.
π Definition β Reused Ports: The use of the same source port number for a new TCP connection before the previous connection using that port has been properly terminated via TCP FINs or RSTs.
π Concept: Proper termination required β A port can be safely reused only after the previous TCP connection using that port has been fully closed.
π Example: Client uses source port 1026 β Server port 80 (1st connection). If client tries to open new connection with source port 1026 to server port 80 while 1st connection still active β reused port problem. If 1st connection was terminated first β no problem.
β Key Takeaways
Reused ports are not inherently problematic. They become a serious issue only when a previous TCP connection using that same port has not been properly terminated through TCP FINs or RSTs. Students must remember that the termination status of the prior connection is the decisive factor. Attempting to reuse a port while a previous connection is still active causes confusion and can introduce significant communication delays. The Keep Alive timer mentioned at the start of the lecture is used to check for Window Updates, not for detecting dead peers.
π§ Quick Revision Questions
- What is the primary condition that makes reused ports a problem?
- How must a previous TCP connection be terminated for safe port reuse?
- What port numbers are used in the example scenario (client and server ports)?
- What is the Keep Alive timer used for in this context?
- Can reused ports ever be harmless? Explain briefly.