How alihamz10/computer-networks-lab-comp-352l works
Project Type and Purpose
• This is an educational repository of four hands-on labs in computer networks.
• It contains:
• Lab manuals (PDFs) describing exercises
• Raw data (PCAP files) and code (Python scripts) for each lab
• Screenshots / test harness outputs
• Markdown lab reports summarizing findings
File Structure
• Top-level directories:
• Lab Manuals/ (PDF instructions)
• Lab 03/ (Wireshark PCAPs + Screenshots)
• Lab 04/, 05/, 06/ (Python socket programming modules)
• Lab Reports/ (Markdown write-ups)
• Key files:
• user_credentials.json (shared data for auth tasks in Labs 05/06)
• README.md (entry-point documentation, prerequisites, quick start)
README for Technical Stack & Workflow
• External tools: Wireshark (for PCAP inspection)
• Runtime: Python 3.10+
• Modules use standard libraries: socket, threading, json.
• Workflow per lab: follow manual → run scripts / inspect PCAP → capture output → document in report.
Defining Main Components
a. Resources Layer
• “Lab Manuals” (PDF) ← the source of requirements for each lab.
b. Experiment Modules (one per lab)
• Lab 03 Module
• Inputs: PCAP files in Lab 03/
• Processor: Wireshark GUI / CLI
• Outputs: Screenshots/analysis images
• Lab 04-06 Modules
• Inputs: Python scripts + user_credentials.json (for auth labs)
• Processor: Python interpreter
• Outputs: Screenshots/tests under each Lab XX/Screenshots
c. Documentation Layer
• Lab Reports (Markdown) consolidating screenshots and answers
• README.md orchestrates the overall workflow
d. External Services & Tools
• Wireshark
• Python 3.10+ runtime
• Git
Interactions & Data Flow
• Manuals → guide → Experiment Modules
• PCAPs + Scripts → fed into → Tools (Wireshark / Python)
• Tools → produce → Artifacts (Screenshots, test logs)
• Artifacts → referenced by → Lab Reports
• README → entry-point → links Manuals, Labs, Reports
Architectural Patterns & Design Principles
• Clear separation of concerns:
• Instruction layer (PDF manuals)
• Execution layer (PCAP analysis, socket code)
• Verification/output layer (screenshots/tests)
• Documentation layer (reports)
• Consistent folder layout per lab for uniformity
Essential Elements
• Clear, unique labels for: Lab 03, Lab 04, Lab 05, Lab 06, Lab Manuals, Lab Reports, README
• Callouts for key configuration files (e.g., user_credentials.json) and dependencies (Python, Wireshark)