Basic Network Troubleshooting using Wireshark — Session 2

Overview

This course segment introduces Wireshark as an essential network analysis tool for a broad range of technical roles, including network operations, security operations, DevOps, development, and support. The instructor emphasizes its universal relevance in troubleshooting and protocol analysis, particularly in modern cloud and continuous integration environments. The session transitions into a guided pre-lab exercise, where learners are instructed to examine a packet capture file related to a slow network issue, preparing for collaborative analysis.

Topic (Timeline)

1. Role Relevance of Wireshark [00:00:02.940 - 00:03:08.720]

• Wireshark is presented as a fundamental skill for all technical roles: network operations, help desk/support, security operations (SOC/Threat Hunting), DevOps, development, and testing.
• DevOps engineers are defined as those managing cloud-based CI/CD pipelines (e.g., Azure portal), handling build deployment, continuous integration, and configuration automation.
• The instructor shares personal experience as a developer, tester, and NDR product analyst to reinforce that protocol analysis via Wireshark is critical when applications operate over networks.
• Core message: Network troubleshooting and protocol understanding are not siloed skills—they are universally required across modern IT and security workflows.

2. Pre-Lab Introduction and Packet Analysis Task [00:03:10.860 - 00:04:51.020]

• Learners are directed to open a pre-lab packet capture file named “pre lab slow network picket file” (note: “picket” is likely a mispronunciation of “packet”).
• The file captures network traffic associated with a slow network performance issue.
• Students are instructed to spend ~5 minutes reviewing the packet data to form an initial understanding of the traffic patterns.
• The instructor mutes audio to allow independent analysis and invites two participants (Tanin and Ham) to share observations in the next phase.

Appendix

Key Principles

• Wireshark is not optional for technical roles—it is a core diagnostic tool for any role involving networked systems.
• Protocol-level visibility enables root-cause analysis in complex environments (e.g., cloud CI/CD, distributed applications).

Tools Used

• Wireshark (for packet capture and analysis)
• Azure Portal (as an example DevOps deployment environment)

Practice Suggestion

• Before moving to guided analysis, independently examine packet captures for anomalies: timing delays, retransmissions, unusual protocol behavior, or high-volume low-efficiency traffic.

Note on Terminology

• “Picket file” in transcript is likely a speech-to-text error for “packet file.” Correct term should be used in follow-up materials.