π Lecture 127 β Wireshark Lab 34
π Overview: This lecture introduces the process for finding DNS response times in Wireshark using the
dns.timefield. It demonstrates how to create a custom column to monitor DNS server performance and identify slow DNS responses that can affect network applications.
ποΈ Topics Covered
The lecture covers DNS as a request/response protocol using UDP, the DNS time field available only in response packets, step-by-step instructions for creating a DNS Delta column in Wireshark, sorting the column to identify significant delays, and investigating why a DNS server might be responding slowly β illustrated with the tr-dns-slow.pcapng trace file.
π Lecture Summary
Topic 127: Wireshark Lab 34
This topic explains how to find DNS response times in Wireshark. Domain Name Service (DNS) provides the network IP address of a machine for a network name such as (such as www.wireshark.org). Applications protocols such as SMTP and HTTP generate DNS queries when a user provides a network name to them. DNS, which is a request/response protocol, employs UDP.
π Definition β DNS: Provides the network IP address of a machine for a network name π Formula: dns.time = Time between DNS query and DNS response (in seconds) π Example: DNS response Packet 3 has dns.time of 0.107083000 seconds
Step 1: Open tr-dns-slow.pcapng.
Step 2: The dns.time field exists only in DNS response packets. In this trace file, Packet 3 is the first DNS response packet. Use this packet to create a dns.time column. Expand Packet 3's the Domain Name System (response) section.
Step 3: Right-click on the [Time: 0.107083000 seconds] line and click Apply as Column.
Step 4: The newly created column appears to the left of the Info column. You can click and drag your new column to the right of the existing TCP Delta column.
Step 5: Right-click on the new column heading and select Edit Column Details. Rename the new column to DNS Delta. Click OK.
Step 6: By clicking the new DNS Delta column heading twice, it gets sorted from high to low.
A significant delay preceding Packet 11 of this trace file can be observed β almost 1.3 seconds. We need to investigate further to determine why the DNS server is working slowly.
π‘ Why this matters: A 1.3 second DNS response time indicates severe DNS server performance issues that will degrade all applications relying on name resolution, including web browsing and email delivery.
β Key Takeaways
The critical skill from this lecture is creating a DNS Delta column in Wireshark by applying the dns.time field from a DNS response packet as a column. This column only appears in response packets, not query packets. Sorting the DNS Delta column from high to low reveals the slowest DNS responses β in the example, Packet 11 had a 1.3 second delay, which is abnormally slow for DNS and requires investigation. Methods to rename and reposition columns were also demonstrated for efficient analysis. Understanding how to measure DNS response times enables network administrators to diagnose DNS server performance problems.
π§ Quick Revision Questions
- What protocol does DNS typically use for transport?
- In which type of DNS packets does the
dns.timefield exist? - What was the DNS response time value for Packet 3 in the tr-dns-slow.pcapng file?
- What was the significant delay observed for Packet 11, and what does it indicate?
- How do you sort the DNS Delta column to find the slowest DNS responses?
π Lecture 128 β Wireshark Lab 35
π Overview: This topic describes how to create a Button to detect High DNS response times in Wireshark. It matters because DNS delays can significantly impact web browsing performance, and network analysts need quick tools to identify problematic DNS queries.
ποΈ Topics Covered
This lecture covers the role of the Domain Name System (DNS) as a distributed database for address/name translation, the process by which a browser obtains an IP address for a hostname via DNS, and a step-by-step Wireshark tutorial on creating a custom filter button to detect DNS response times greater than 1 second using the dns.time > 1 display filter.
π Lecture Summary
DNS Overview
The Domain Name System (DNS) is a distributed database implemented in a hierarchy of many DNS servers. It is an application-layer protocol that allows hosts to query the distributed database to resolve names (address/name translation). Consider a browser (i.e., an HTTP client) running on some host A, who requests www.wireshark.org. In order for host A to be able to send an HTTP request message, host A must first obtain the IP address of the server. The host A runs the client side of the DNS application. The browser extracts the hostname from the URL and passes it to the client side of the DNS application. The DNS client sends a query using UDP to the DNS server listening at port 53. The DNS client eventually receives a reply which includes the IP address for the hostname. Once the browser receives the IP address from DNS, it can initiate a TCP connection to the HTTP server process located at port 80 at that IP address.
π Definition β DNS (Domain Name System): A distributed database implemented in a hierarchy of many DNS servers; an application-layer protocol that allows hosts to query the distributed database to resolve names (address/name translation).
π Example: A browser on host A requests www.wireshark.org. The browser extracts the hostname from the URL and passes it to the DNS client. The DNS client sends a UDP query to port 53 of a DNS server. The DNS server replies with the IP address. The browser then initiates a TCP connection to port 80 at that IP address to send the HTTP request.
Creating a Button to Detect High DNS Response Times
Letβs create a button to detect DNS response times larger than 1 second. Step 1: Open tr-dns-slow.pcapng. Step 2: Type dns.time > 1 in the display filter area and then click Save. Step 3: Name your button DNS Delay and click OK. Step 4: Click your new DNS Delay button. We observe that Packet 11 is the only packet that matched this filter, i.e., Packet 11 contains the largest DNS delay time. Figure 128.1 illustrates the creation of this button.
π Definition β dns.time: A Wireshark display filter field that represents the DNS response time (the time between a DNS query and its corresponding response).
π Formula: dns.time > 1 β This filter selects all DNS packets where the response time is greater than 1 second.
π Example: After opening tr-dns-slow.pcapng, the user types dns.time > 1 in the display filter area, saves the filter as a button named "DNS Delay", and clicks the button. Only Packet 11 matches this filter, indicating it contains the largest DNS delay time (greater than 1 second).
π‘ Why this matters: Creating custom filter buttons like this allows network analysts to quickly identify performance issues without retyping complex filters each time.
β Key Takeaways
The lecture demonstrates the fundamental DNS resolution process where a browser extracts a hostname from a URL, sends a UDP query to port 53 of a DNS server, and receives an IP address in reply. It then provides a practical Wireshark tutorial on creating a custom button using the display filter dns.time > 1 to detect DNS response times larger than 1 second. The critical steps are opening the correct pcap file (tr-dns-slow.pcapng), entering the filter condition, saving it as a named button, and clicking the button to reveal only qualifying packets. Packet 11 was the sole match in the provided capture, highlighting its high DNS delay. This technique enables rapid identification of DNS performance anomalies in network traffic analysis.
π§ Quick Revision Questions
- What port does the DNS server listen on for UDP queries?
- What display filter field is used to detect DNS response times in Wireshark?
- How many packets matched the filter
dns.time > 1in the tr-dns-slow.pcapng capture? - What is the first step in creating a custom DNS delay button in Wireshark?
- How does a browser obtain the IP address of a server before sending an HTTP request?
π Lecture 129 β Wireshark Lab 36
π Overview: This lecture teaches you how to visualize and analyze DNS response times using Wiresharkβs IO Graph feature, enabling detection of slow DNS responses in a network trace. Understanding this skill is critical for troubleshooting network performance issues, as DNS delays directly impact web browsing and application responsiveness.
ποΈ Topics Covered
This lecture covers the step-by-step process of creating a DNS response time graph in Wireshark using the IO Graph tool, specifically focusing on the MAX(*) calculation method for the dns.time field, and how to interactively identify problematic packets by clicking on graph peaks.
π Lecture Summary
Plotting DNS Response Times in Wireshark
To highlight DNS delays in a trace file, you create a specialized IO Graph. The process begins by opening the provided trace file tr-dns-slow.pcapng. Then, navigate to Statistics | IO Graph to access the graphing interface. In the Y Axis Unit area, select Advanced... to unlock custom calculation options. From the MAX(*) option under Graph 1 Calc, enter dns.time in the Calc field. Finally, click the Graph 1 button to plot the DNS response times.
π Definition β dns.time: The Wireshark field representing the time between a DNS query and its corresponding response, measured in seconds.
π Formula: MAX(*) β Calculates the maximum value of the specified field (here, dns.time) within each time interval of the graph.
π Example: When plotting tr-dns-slow.pcapng, after selecting MAX(*) and entering dns.time, the graph displays peaks at specific intervals. Clicking the highest point in the graph instantly takes Wireshark to that packet, allowing you to inspect the slow DNS response.
π‘ Why this matters: DNS slow response times can cause noticeable delays in web page loading and other network services. By plotting dns.time against time, you can visually identify outliers (the highest peaks) that represent abnormally slow DNS queries requiring further investigation.
β Key Takeaways
The primary takeaway is the ability to create a DNS response time graph in Wireshark using the IO Graph tool with the MAX() calculation on the dns.time field. You must remember the exact navigation path: Statistics | IO Graph β Y Axis Unit β Advanced... β MAX() Graph 1 Calc β enter "dns.time" β click Graph 1. The highest peak on the graph directly corresponds to the slowest DNS response, and clicking it automatically opens that packet for detailed inspection. This technique transforms raw packet data into an actionable visual tool for DNS performance troubleshooting.
π§ Quick Revision Questions
- What is the exact menu path to access the IO Graph in Wireshark?
- Which calculation option should be selected in the Advanced Y Axis Unit settings to plot DNS response times?
- What field name must be entered in the Calc area to plot DNS response times?
- What does clicking the highest point on the plotted graph do in Wireshark?
- What does the dns.time field represent in a captured packet trace?
π Lecture 130 β Wireshark Lab 37
π Overview: This lecture explains how to reassemble TCP streams by disabling the Allow Subdissector setting in Wireshark. It focuses on measuring HTTP response times accurately and understanding the difference between total download time and actual server response time. This knowledge is critical for network troubleshooting and performance analysis.
ποΈ Topics Covered
The lecture covers the HTTP response time estimation using the http.time field, the impact of disabling Allow Subdissector to reassemble TCP streams, and two practical methods to change this TCP preference setting. It also discusses how DNS query responses can cause delays and how sorting the dns.time column aids detection.
π Lecture Summary
Reassembling TCP Streams by Disabling Allow Subdissector
The delta time between an HTTP request (e.g., GET) and the response (e.g., 200 OK) is the HTTP response time. In Wireshark, this can be estimated with the http.time field. High HTTP response times can result from an overloaded web server or when the server needs to consult another server to answer client requests.
π Definition β Allow Subdissector to Reassemble TCP Streams: A Wireshark TCP preference that, when enabled, measures time from the HTTP Request to the final data packet of the response (total download time). When disabled, it measures only how quickly the server responded.
π Formula: HTTP response time = http.time field β time difference between HTTP request and first response packet (with subdissector disabled) OR last data packet (with subdissector enabled)
π Example: If a web server is overloaded or needs to consult another server, it can result in high HTTP response times. By disabling the subdissector, you learn how quickly the server responded, as opposed to the total download time of the object.
π‘ Why this matters: Distinguishing between server response time and total download time helps identify whether delays are caused by the server itself or by network/data transfer issues.
Two Methods to Change TCP Preference Setting
To estimate the total time taken by downloading an object, enable this setting. To learn how quickly the server responded, disable it.
Method 1: Right-click in Packet Details Step 1: Open tr-http-pcaprnet101.pcapng. Step 2: Right-click on the TCP header in the Packet Details of Packet 5. Select Protocol Preferences. Step 3: Uncheck Allow subdissector to reassemble TCP streams (as shown in Figure 130.1).
Method 2: Edit Menu Step 3: The 2nd method is: Select Edit | Preferences | (+) Protocols | TCP.
Figure 130.1 shows the checkbox in the TCP protocol preferences settings.
π‘ Why this matters: Knowing both methods ensures you can quickly configure Wireshark for accurate response time analysis in any situation.
β Key Takeaways
The HTTP response time, measured by the http.time field, can be interpreted in two ways: total download time (subdissector enabled) or server response time (subdissector disabled). High HTTP response times often indicate server overload or dependency on other servers. Sorting the dns.time column helps detect delays caused by DNS query responses. Two methods exist to change the TCP preference setting for reassembling streams: right-clicking the TCP header in Packet Details or navigating through Edit | Preferences | Protocols | TCP. Understanding this distinction is essential for accurate network performance troubleshooting.
π§ Quick Revision Questions
- What is the difference between HTTP response time with Allow Subdissector enabled versus disabled?
- What common server issues can result in high HTTP response times?
- List the two methods to change the TCP preference setting for reassembling TCP streams in Wireshark.
- Why might sorting the dns.time column help in detecting delays?
- In the example given, what type of packet caused the largest delay?
π Lecture 131 β Wireshark Lab 38
π Overview: This lecture demonstrates how to locate and display HTTP response times in Wireshark using a specific trace file. It provides a step-by-step practical procedure for creating a custom column to visualize the
http.timefield, which is critical for analyzing web server performance and network latency.
ποΈ Topics Covered
The lecture covers opening the trace file tr-http-pcaprnet101.pcapng, identifying the first HTTP response packet (Packet 10, HTTP 303 See Other), accessing the [Time since request] field in the Packet Details pane, applying it as a column, and repositioning the column for better visibility in the Wireshark interface.
π Lecture Summary
Step 1: Open the Trace File
Begin by opening the provided capture file named tr-http-pcaprnet101.pcapng in Wireshark. This file contains HTTP traffic suitable for analyzing response timing.
Step 2: Identify the First HTTP Response Packet
Only HTTP response packets contain the http.time field. In this trace file, the first HTTP response packet is Packet 10, which is an HTTP 303 See Other response. Use this packet to create your http.time column.
π Definition β HTTP response packet: A packet sent by a web server in reply to an HTTP request, containing status codes (e.g., 303 See Other) and timing metadata.
Steps 3β4: Create and Position the Column
In the Packet Details pane of Packet 10, right-click on the Hypertext Transfer Protocol section and select Expand Subtrees. Locate the line [Time since request: 0.026416000 seconds]. Right-click on this line and select Apply as Column. Your newly created column appears to the left of the Info column. Click and drag your new column to a position with better visibility for analysis.
π Formula: http.time = Timestamp of HTTP response packet β Timestamp of corresponding HTTP request packet. Measured in seconds.
π Example: In Packet 10, the [Time since request] value is 0.026416000 seconds, meaning the server took approximately 26.4 milliseconds to respond to the request.
π‘ Why this matters: HTTP response times directly indicate server responsiveness and network latency. Monitoring this metric helps diagnose web application performance issues.
β Key Takeaways
You must remember that only HTTP response packets contain the http.time field, and the first such packet in this trace is Packet 10 (HTTP 303 See Other). The key skill is right-clicking on the [Time since request] line in the Packet Details pane and selecting "Apply as Column" to create a custom column. After creation, you should reposition the column by dragging it for better visibility. The value 0.026416000 seconds represents the server's response time for that packet. Mastering this column creation process allows you to systematically analyze response times across all HTTP traffic in any capture file.
π§ Quick Revision Questions
- Which type of Wireshark packet contains the
http.timefield? - What is the packet number and status code of the first HTTP response packet in
tr-http-pcaprnet101.pcapng? - What specific line in the Packet Details pane do you right-click to create the HTTP response time column?
- How do you move the newly created column to a better position in the Wireshark interface?
- What does the value 0.026416000 seconds represent in the context of this lab?
π Lecture 132 β Wireshark Lab 39
π Overview: This lecture teaches how to analyze and visualize HTTP response times using Wireshark. It covers creating a custom column to calculate HTTP delays and saving a filtering button for quick detection of high response times, enabling efficient network problem identification.
ποΈ Topics Covered
The lecture covers creating a custom HTTP Delta column to measure response delays, sorting packets by delay to find the slowest responses, and building a persistent filter button to instantly isolate HTTP responses exceeding a defined threshold (e.g., 1 second).
π Lecture Summary
Step 5: Renaming the New Column
Right-click on the column heading and select Edit Column Details. Rename this new column to HTTP Delta. Click OK. This custom column will display the calculated delta time (delay) between the HTTP request and the corresponding response.
π Definition β HTTP Delta: The calculated time difference (in seconds) between an HTTP request and its matching response, indicating the server response delay.
Step 6: Sorting and Observing High Delays
Sort HTTP responses from high to low by clicking your new HTTP Delta column heading twice. Packets with the largest delays will appear at the top of the list. We can observe that HTTP response time from the HTTP server (209.133.32.69) is over 1.7 seconds twice in this trace file. Those packets are bearing numbers 432 and 20.
π Example: Sorting by the HTTP Delta column reveals that packets #432 and #20 from server 209.133.32.69 have response delays exceeding 1.7 seconds. This identifies the worst-performing HTTP transactions.
Step 1: Open the Trace File
Open tr-http-pcaprnet101.pcapng.
Step 2: Create a Button for High Response Times
Type http.time > 1 in the display filter area and then, click Save. This creates a persistent button that you can click anytime to instantly filter and display only HTTP responses with a delay greater than 1 second. This is one of the most powerful features to improve your efficiency in locating network problems.
π‘ Why this matters: Creating filter buttons transforms complex filter expressions into one-click actions, drastically speeding up repetitive network troubleshooting tasks.
β Key Takeaways
You must remember how to create a custom HTTP Delta column to measure request-response delays in Wireshark. Sorting this column identifies the slowest HTTP responses. The most powerful efficiency tool is saving a filter expression (like http.time > 1) as a clickable button for instant access. Packet numbers 432 and 20 in this trace had delays over 1.7 seconds, illustrating real-world server latency.
π§ Quick Revision Questions
- What is the purpose of creating an HTTP Delta column in Wireshark?
- After creating the HTTP Delta column, how do you sort packets to see the largest delays first?
- How many packets in the trace file had an HTTP response time over 1.7 seconds, and what were their packet numbers?
- What filter expression is used to create a button that detects high HTTP response times?
- Why is the ability to save filter expressions as buttons considered a powerful feature in Wireshark?
π Lecture 133 β Wireshark Lab 40
π Overview: This lecture focuses on using Wireshark to graphically visualize and analyze HTTP response times. It explains how to configure custom graphs and filters, and demonstrates the process of identifying packets with the highest delays. This matters because it enables network analysts to quickly spot performance bottlenecks in HTTP communications.
ποΈ Topics Covered
This lecture covers the step-by-step configuration of Wireshark's IO Graph feature to plot HTTP response times (http.time). It details the Graph configuration options (Graph 1-5, Color, Filter, Style), X Axis settings (Tick interval, Pixels per tick, View as time of day), and Y Axis Unit & Scale settings. The practical lab demonstrates creating a custom graph to identify packets with the highest HTTP response delays, specifically packets 20 and 432 showing delays over 1.7 seconds.
π Lecture Summary
Step 3: When you click save, Wireshark prompts to name the button. Name it HTTP Delay and then click OK.
Always remember to clear your display filter when you are done reviewing the results.
Step 4: As you click your new HTTP Delay button, you will find two packets of this trace file matching the filterβPacket 20 and Packet 432.
Topic 133: Wireshark Lab 40
In this topic, we plot HTTP response times in Wireshark. Wireshark allows a user to define up to five differently colored graphs. We can make the following configurations:
Graphs
- Graph 1-5: enable the specific graph 1-5 (only graph 1 is enabled by default).
- Color: (cannot be changed)
- Filter: a display filter for this graph
- Style: (Line/Impulse/FBar/Dot)
X Axis
- Tick interval: an interval in x direction lasts (10/1 mins or 10/1/0.1/0.01/0.001s)
- Pixels per tick: use 10/5/2/1 pixels per tick interval
- View as time of day: instead of sec or mins, view x as time of day
Y Axis
- Unit: the unit for y direction (Packets/Tick, Bytes/Tick, Bits/Tick, Advanced...)
- Scale: the scale for the y unit (Logarithmic, Auto, 10, 20, 50, 100, 200, 500, ...)
Letβs Graph HTTP Response Times.
Step 1: Open tr-http-pcaprnet101.pcapng.
Step 2: Select Statistics | IO Graph.
Step 3: In the Y Axis Unit area, select Advanced...
Step 4: Select the MAX(*) Graph 1 Calc option and then, enter http.time in the Calc area.
Step 5: To plot your results, click the Graph 1 button.
If you click the highest points in the graph, Wireshark will take you to those packets which have encountered highest delays. Packet 20 and Packet 432 show that the HTTP response time from the HTTP server (209.133.32.69) was over 1.7 seconds.
π‘ Why this matters: This technique allows you to visually identify the slowest HTTP transactions in a capture, which is critical for troubleshooting web application performance issues.
β Key Takeaways
You must remember that Wireshark's IO Graph can plot up to five graphs simultaneously. To plot HTTP response times, you select the Advanced Y Axis Unit, choose the MAX(*) calculation, enter http.time as the calculation field, and enable Graph 1. The highest points in the resulting graph correspond to packets with the largest response delays; clicking them navigates to those packets. In the lab example, packets 20 and 432 (from HTTP server 209.133.32.69) had delays exceeding 1.7 seconds. Always clear the display filter after reviewing results.
π§ Quick Revision Questions
- How many differently colored graphs can you define in Wireshark's IO Graph?
- What menu path do you follow to access the IO Graph feature?
- Which calculation option (e.g., MAX, MIN, AVG) is used to plot http.time in the lab?
- In the lab, which two packets had the highest HTTP response delays, and what was the approximate delay value?
- What is the IP address of the HTTP server identified in packets 20 and 432?
π Lecture 134 β Wireshark Lab 41
π Overview: This lecture demonstrates how to create a Server Message Block (SMB) response time column in Wireshark to analyze file-sharing protocol delays. Understanding SMB timing is critical for troubleshooting slow network file transfers on Windows-based networks.
ποΈ Topics Covered
Introduction to Server Message Block (SMB) as a request/response protocol for Windows file sharing, explanation of the smb.time field in SMB response packets, and a step-by-step walkthrough for creating, positioning, and sorting an SMB Delta column in Wireshark using the provided packet capture file.
π Lecture Summary
Introduction to Server Message Block (SMB)
Server Message Block (SMB) is a file sharing protocol used by Microsoft on Windows-based networks. The two common versions are SMB and SMB version 2. It operates as a request/response protocol, where a client sends a request and the server sends back a response with a specific response code. Response codes are documented on Microsoft's Open Specification site at www.microsoft.com/openspecifications/.
π‘ Why this matters: SMB delays can significantly impact file transfer performance. The smb.time field, found only in SMB response packets, provides a direct measurement of how long the server took to respond.
Step 1: Open the Packet Capture File
Open the file tr-smb-slow.pcapng in Wireshark.
Step 2: Locate the First SMB Response Packet
The first SMB response packet in the capture is Packet 5 (Negotiate Protocol Response). The smb.time field exists only in SMB response packets.
π Definition β smb.time: A Wireshark field that records the time elapsed from when the SMB request was sent to when the SMB response was received, measured in seconds.
π To examine: Expand the SMB section and the SMB Header section of Packet 5 in the Packet Details pane.
Step 3: Create a Column from smb.time
Right-click on the line that reads [Time from request: 0.000766000 seconds] and select Apply as Column.
π Example: This value (0.000766000 seconds) represents a delay of approximately 0.77 milliseconds for the Negotiate Protocol Response.
Step 4: Reposition the New Column
The newly created column appears to the left of the Info column. Click and drag the column to a suitable location where visibility is improved.
Step 5: Rename the Column
Wireshark automatically assigns the new column the label Time from request. To rename it:
- Right-click on the column heading.
- Select Edit Column Details.
- Change the title to SMB Delta.
- Click OK.
Step 6: Sort by Largest Delay
To examine SMB response packets with the largest delays, click the SMB Delta column heading twice. This sorts the packets from high to low (descending order), placing the slowest responses at the top.
π Example: After sorting, the packet with the highest smb.time value will appear first, indicating the greatest server delay.
β Key Takeaways
SMB is a request/response file sharing protocol on Windows networks, and its response delays can be measured using the smb.time field in Wireshark. Only SMB response packets contain the smb.time field β request packets do not. The step-by-step process involves opening the capture file, expanding Packet 5βs SMB header, right-clicking the Time from request value to apply it as a column, then renaming the column to SMB Delta for clarity. Sorting by this column in descending order helps identify the slowest SMB responses, which is essential for performance troubleshooting. The example value of 0.000766 seconds illustrates millisecond-level delays that are typical in network captures.
π§ Quick Revision Questions
- What does SMB stand for, and what type of protocol is it?
- In which type of SMB packets does the smb.time field exist?
- What was the smb.time value in Packet 5 of the provided capture?
- What are the two steps required to rename the smb.time column from "Time from request" to "SMB Delta"?
- How do you sort packets to show the largest SMB delays at the top of the packet list?
π Lecture 135 β Wireshark Lab 42
π Overview: This lecture demonstrates how to use Wireshark to analyze Server Message Block (SMB) protocol performance by creating and interpreting Service Response Time (SRT) statistics. Understanding SMB response times is critical for diagnosing file sharing and network storage performance issues in Windows environments.
ποΈ Topics Covered
Examining SMB and SMB2 response time statistics in Wireshark, opening a sample pcap file, navigating to the SRT statistics window, creating the SMB statistic, and interpreting the minimum, maximum, and average Service Response Time values displayed.
π Lecture Summary
Step 1: Open tr-smb-slow.pcapng
The lecture begins by instructing users to open the provided trace file named tr-smb-slow.pcapng. This file contains captured network traffic that includes SMB protocol exchanges, specifically selected to demonstrate slow SMB response times.
π‘ Why this matters: Using a pre-captured trace file allows consistent analysis without needing a live SMB environment.
Step 2: Select Statistics | Service Response Time | SMB
Navigate to Statistics in the Wireshark menu bar, then select Service Response Time, and finally choose SMB. When prompted by Wireshark, click Create Stat to generate the SMB Service Response Time statistics window.
This window displays three key metrics for the SMB protocol:
- Minimum Service Response Time
- Maximum Service Response Time
- Average Service Response Time
π Example: For the tr-smb-slow.pcapng trace, the SMB Service Response Time statistics window will show specific values for minimum, maximum, and average response times that reflect the performance characteristics of the captured SMB traffic.
β Key Takeaways
The lecture's core lesson is that Wireshark can automatically create and display SMB Service Response Time statistics from captured network traffic. Users must first open a pcap file containing SMB traffic, then navigate through Statistics | Service Response Time | SMB, and click "Create Stat" when prompted. The resulting window shows three critical performance metrics: minimum, maximum, and average SRT. These statistics are available for both SMB and SMB2 protocols. This analysis capability is essential for diagnosing slow file sharing performance in Windows networks.
π§ Quick Revision Questions
- What menu path in Wireshark leads to SMB Service Response Time statistics?
- What three SRT values are displayed in the SMB Service Response Time statistics window?
- What is the name of the sample pcap file used in this lab?
- What must the user click when prompted by Wireshark to generate the SMB statistic?
- Which two SMB protocol versions does Wireshark track for response times?
π Lecture 136 β Wireshark Lab 43
π Overview: This lecture explains how to create a custom button in Wireshark to detect Server Message Block (SMB) and SMB2 response times that exceed 1 second. It teaches the practical skill of using display filters with time-based fields to quickly identify network performance issues related to file sharing protocols.
ποΈ Topics Covered
The lecture covers the process of creating a button in Wireshark to detect SMB and SMB2 response times larger than 1 second. It demonstrates the use of the smb.time and smb2.time filter fields, saving the filter as a button, and testing the button against the tr-smb-slow.pcapng packet capture file.
π Lecture Summary
Step 1: Open tr-smb-slow.pcapng
First, open the provided packet capture file named tr-smb-slow.pcapng in Wireshark. This file contains network traffic with SMB and SMB2 requests and responses.
Step 2: Create the Display Filter
In the display filter area, type the following filter expression: smb.time > 1 || smb2.time > 1. This filter matches packets where either smb.time (for SMB) or smb2.time (for SMB2) is greater than 1 second.
π Definition β smb.time: The time delta (in seconds) between an SMB request and its corresponding response.
π Formula: smb.time > 1 || smb2.time > 1 β Matches packets where the SMB or SMB2 response time exceeds 1 second.
π Example: In the capture file, Packet 132 is the only packet that matches the filter smb.time > 1 || smb2.time > 1.
Step 3: Save the Filter as a Button
After typing the filter, click the Save button (the small disk icon) in the filter toolbar. A dialog box will appear. Name your button SMB/SMB2 Delay and then click OK. This creates a clickable button in the filter toolbar.
Step 4: Test the Button
Click your newly created SMB Delay button. Wireshark will automatically apply the saved filter. In the tr-smb-slow.pcapng capture, Packet 132 is the only packet that matched your filter, indicating it had an SMB response time exceeding 1 second.
π‘ Why this matters: This technique allows network administrators to quickly identify slow SMB responses that can cause file access delays in Windows environments.
β Key Takeaways
The most critical points from this lecture are: (1) Wireshark provides smb.time and smb2.time fields to measure response times for SMB and SMB2 protocols. (2) You can create custom buttons by typing a filter expression, clicking Save, and naming the button. (3) The filter smb.time > 1 || smb2.time > 1 detects any SMB or SMB2 request that took more than 1 second to receive a response. (4) Only Packet 132 matched this filter in the tr-smb-slow.pcapng file. (5) This technique helps identify performance bottlenecks in file sharing traffic.
π§ Quick Revision Questions
- What two Wireshark filter fields are used to measure SMB and SMB2 response times?
- What is the exact filter string used to detect SMB response times greater than 1 second?
- Which packet in the tr-smb-slow.pcapng file matched the filter for delayed SMB responses?
- How do you save a display filter as a button in Wireshark?
- What is the purpose of creating a button for this type of filter?
π Lecture 137 β Wireshark Lab 44
π Overview: This lecture demonstrates how to plot Server Message Block (SMB) response times using Wiresharkβs IO Graph feature. It explains the step-by-step process to visualize SMB performance, which is crucial for diagnosing network latency issues in file-sharing environments.
ποΈ Topics Covered
The lecture covers the complete procedure for plotting SMB response times in Wireshark, including opening the appropriate packet capture file, configuring the IO Graph with advanced Y-axis settings, selecting the correct calculation field (smb.time), and addressing the need for separate graphs for SMB and SMB2 protocols due to different delta time fields.
π Lecture Summary
Plotting SMB Response Times in Wireshark
To begin analyzing SMB performance, open the provided packet capture file tr-smb-slow.pcapng. Navigate to the Statistics menu and select IO Graph. In the Y Axis Unit area, choose Advanced... to access more graphing options. Set Graph 1 Calc to MAX(*) and enter smb.time in the Calc area. Click the Graph 1 button to plot the SMB response times on the graph.
π Example: If a sequence of SMB requests shows response times increasing from 2 ms to 150 ms over 10 seconds, the MAX(*) calculation will plot the single highest response time per interval, highlighting the slowest transactions.
Handling SMB and SMB2 Time Fields
Because SMB and SMB2 use different delta time fields, a single graph cannot capture both. You must create two separate graphs: one for SMB (using smb.time) and another for SMB2 (using its respective time field, such as smb2.time). This ensures each protocolβs response time is accurately plotted.
π Definition β delta time: The time difference between a request and its corresponding response in a protocol exchange. π‘ Why this matters: Incorrectly graphing both protocols on one axis would mix incompatible time measurements, producing misleading results.
β Key Takeaways
SMB response time plotting in Wireshark requires careful configuration using the IO Graph with the MAX(*) calculation on the smb.time field. Because SMB and SMB2 protocols use different delta time fields, you must create separate graphs for each to accurately visualize performance. This technique is essential for identifying slow file transfers and network bottlenecks in Windows-based file sharing environments.
π§ Quick Revision Questions
- What packet capture file is used to plot SMB response times?
- Which Wireshark menu contains the IO Graph feature?
- What calculation option should be selected for Graph 1 Calc?
- Why must separate graphs be created for SMB and SMB2?
- What field name is entered in the Calc area for plotting SMB response times?
π Lecture 138 β Wireshark's Expert Infos System
π Overview: This lecture covers Wireshark's Expert Infos System, a tool that automatically generates alerts about network concerns and packet comments in trace files. It helps both novice and expert users quickly identify probable network problems without manually scanning the packet list.
ποΈ Topics Covered
The lecture introduces the Expert Infos button and the three columns in Wireshark's Status Bar, the six categories of information classified by the Expert system (Errors, Warnings, Notes, Chats, Details, and Packet Comments), and how to open and use the Expert Infos window by clicking the button in the bottom left corner of the Status Bar.
π Lecture Summary
Topic 138: Wireshark's Expert Infos System
This topic provides an overview of Wiresharkβs Expert Infos System. There are two buttons and three columns in Wiresharkβs Status Bar. The first button is named the Expert Infos button. Wireshark generates alerts for you to numerous network concerns seen in the trace file as well as packet comments in the Expert Infos window. Expert infos are only a hint and help both novice and expert users to find probable network problems a lot faster, compared to scanning the packet list βmanuallyβ. The Expert classifies information into 6 categories:
- Errors: red
- Warnings: yellow
- Notes: cyan
- Chats: blue
- Details: grey
- Packet Comments: green
When you click the Expert Infos button in the bottom left corner of the Status Bar, the Expert Infos window will open.
π Definition β Expert Infos System: Wireshark's automatic alert generation system that classifies network concerns and packet comments into six color-coded categories (Errors, Warnings, Notes, Chats, Details, Packet Comments) to help users quickly identify probable network problems.
π‘ Why this matters: The color coding allows users to instantly prioritize issues β red Errors are critical, yellow Warnings need attention, while blue Chats and grey Details are informational and can be ignored in most troubleshooting scenarios.
β Key Takeaways
The Expert Infos System automatically generates alerts for network concerns and packet comments, classifying them into six color-coded categories: Errors (red), Warnings (yellow), Notes (cyan), Chats (blue), Details (grey), and Packet Comments (green). The Expert Infos button is located in the bottom left corner of the Status Bar, and clicking it opens the Expert Infos window. These infos serve as hints to help all users find probable network problems much faster than manual scanning. The system is designed to assist both novice and expert users in troubleshooting.
π§ Quick Revision Questions
- Where is the Expert Infos button located in Wiresharkβs interface?
- What are the six categories of information classified by the Expert Infos System, and what color is associated with each?
- What is the primary purpose of the Expert Infos System?
- What happens when you click the Expert Infos button?
- How does the Expert Infos System help both novice and expert users compared to manual scanning?
π Lecture 139 β Wireshark's Packet Loss Detection
π Overview: This lecture explains how Wireshark detects packet loss by analyzing TCP sequence numbers. Understanding packet loss causes and detection methods is critical for network troubleshooting and performance analysis.
ποΈ Topics Covered
The lecture covers three main areas: what causes packet loss in networks, how Wireshark uses TCP sequencing to detect lost packets, and the different categories of Expert information (chats, notes, warnings) that help identify network issues. It also explains how to enable or disable packet loss detection in Wireshark's preferences.
π Lecture Summary
Causes of Errors, Warnings, and Notes
Understanding the causes of errors, warnings, and notes helps determine what is affecting network performance. The lecture provides examples of commonly occurring Expert information:
- Chats: information about usual workflow, e.g., a TCP packet with the SYN flag set
- Notes: notable things, e.g., an application returned an "usual" error code like HTTP 404
- Warnings: e.g., an application returned an "unusual" error code like a connection problem
π‘ Why this matters: These categories help network analysts prioritize issues β chats are normal, notes are notable but expected, while warnings indicate real problems.
What Causes Packet Loss
Most of the time packets are dropped by interconnecting devices such as a switch, a router, a firewall β i.e., anything that makes forwarding decisions. The common reasons for packet loss include:
- A switch or router is overloaded
- The device is unable to keep up with the required packet forwarding rate
- The device is simply faulty
π Definition β Packet loss: the failure of one or more transmitted packets to arrive at their destination, typically caused by network congestion or faulty hardware
π Example: A switch handling 10,000 packets per second but receiving 15,000 packets per second will drop 5,000 packets per second due to overload.
How Wireshark Detects Packet Loss
The TCP sequencing process is used by Wireshark to detect lost packets. Wireshark analyzes the sequence numbers in TCP packets to identify gaps where packets should have arrived but did not.
π Definition β TCP sequence numbers: numbers that TCP assigns to each byte of data to ensure reliable delivery and proper ordering of packets
π Formula: Packet loss detection β Wireshark compares expected sequence numbers with received sequence numbers; gaps indicate potential packet loss
You can also turn off this feature by disabling the Analyze TCP Sequence Numbers TCP Preference setting. To do this:
- Click the Preferences button
- Expand Protocols
- Choose TCP
- Disable the "Analyze TCP Sequence Numbers" option
π‘ Why this matters: Disabling this feature may be useful in certain scenarios, such as when analyzing non-standard TCP implementations or reducing processing overhead.
β Key Takeaways
The most critical points to remember are that packet loss is primarily caused by overloaded or faulty network devices like switches and routers, not by the end hosts. Wireshark detects packet loss using TCP sequence numbers by looking for gaps in the expected data stream. Network experts categorize issues into chats (normal), notes (notable but expected), and warnings (unusual problems). The packet loss detection feature can be toggled in Wireshark's TCP preferences. Understanding these concepts is essential for accurate network troubleshooting.
π§ Quick Revision Questions
- What are the three categories of Expert information in Wireshark, and what does each represent?
- What are the three common causes of packet loss mentioned in the lecture?
- How does Wireshark detect lost packets at the TCP level?
- Where in Wireshark's settings can you disable the packet loss detection feature?
- Give an example of a "Notes" level event that Wireshark might report.