Skip to content

About

Computer Networks — Course Kit (EN) · v13.05.00 · 13 lectures · 13 seminars · team projects · PlantUML · ASE-CSIE · ing. dr. Antonio Clim

Topics

Resources

Stars

43 stars

Watchers

0 watching

Forks

Latest commit

 

History

233 Commits

Folders and files

Repository files navigation

Computer Networks — Course Kit (EN)

Version Language Diagrams Labs

This repository is a complete teaching kit for an undergraduate computer networks module. It is organised as a sequence of lectures and evidence producing seminars, supported by projects, tooling and reproducible diagrams.

You should treat the kit as a laboratory manual, not only as a slide collection. The pedagogical intent is to move from declarative claims to defensible explanations supported by observable artefacts such as packet captures, logs and deterministic runs.

Language policy: the core materials are in English (British). Some files are intentionally bilingual (EN + RO) and Romanian instructor materials remain in Romanian.


Version status

This branch prepares v1.5.0. The preserved pre-remediation release is v1.4.0. Historical v13.05.00 references remain historical, and the MININET-SDN OVA retains its independent version 1.0.0 and Zenodo DOI. Candidate checks are documented in the remediation record; this branch is not a declaration of full VM or browser acceptance.

Start here

If you are a student

  1. Read current-outline.md to understand the weekly sequence.
  2. Use the MININET-SDN virtual workstation used in the ASE laboratories. The WSL2 setup is an alternative for the exercises that support it.
  3. Start with S01 and keep evidence as you work.

If you are teaching

  1. Use the week-by-week map below to plan the lecture–seminar pairing.
  2. Standardise the environment early. The ASE laboratory route is VirtualBox + MININET-SDN, with Docker Engine inside the guest. WSL2 + Ubuntu is a separate alternative for compatible exercises.
  3. Mark on evidence not on screenshots. Require submissions framed as claim → evidence → interpretation → limitation.

Contents


What is inside

Area What it contains What you use it for
00_APPENDIX/ Week 0 onboarding, optional bridge material, quizzes, troubleshooting notes reduce toolchain friction and standardise baseline skills
00_TOOLS/ PlantUML tooling, offline formatting, QA scripts keep the kit deterministic and maintainable
01_GUIDE_MININET-SDN/ Mininet-SDN setup guide (VM based) controlled topologies for SDN and routing demonstrations
02_PROJECTS/ project briefs, marking evidence expectations, diagrams and helper tools assessment by reproducible artefacts
03_LECTURES/ lecture Markdown with scenarios and diagrams conceptual model building plus short demonstrations
04_SEMINARS/ seminar explanations, tasks, scenarios, code and Docker configs practical work with evidence capture

Learning design

The kit uses a repeated loop:

  1. Model: you introduce a concept and the constraints under which it is valid.
  2. Observation: you run a controlled scenario and observe behaviour.
  3. Explanation: you justify observations with protocol level reasoning.
  4. Transfer: you reuse the same reasoning in a different context.

Diagram source (PlantUML)

@startuml
skinparam backgroundColor white
skinparam shadowing false
skinparam defaultFontName Arial
skinparam ArrowColor #1f2937
skinparam ComponentBorderColor #111827
skinparam ComponentBackgroundColor #f9fafb

title Teaching loop: model → evidence → explanation → transfer

actor "Instructor" as I
actor "Student" as S

component "Lecture (model)" as L
component "Seminar (evidence)" as E
component "Project (transfer)" as P
component "QA scripts" as Q

I --> L : deliver
S --> L : pre-read
L --> E : frame tasks
S --> E : run and observe
E --> P : integrate
Q --> L : consistency
Q --> E : consistency
@enduml

Tooling you will use

You do not need to install everything on day one. You should expand your toolchain as the seminars demand it.

Tool Why it matters Where you will use it
🧭 Git versioned distribution and updates cloning, updating and optional contributions
🐍 Python 3.10+ runnable scripts and protocol exercises seminars, scenarios and project tooling
🔎 Wireshark and tshark packet capture and protocol inspection S01 and most later labs
🐳 Docker Engine and Docker Compose isolated services and reproducible stacks many seminars and several lecture scenarios
🏁 COMPNET lab runner (optional) consistent start/stop commands for Compose scenarios selected lecture scenarios (Phase C pilot)
🎛️ Portainer CE (optional) visual inspection of containers and networks convenient debugging and classroom demos
☕ Java 8+ PlantUML rendering diagrams in lectures, seminars and projects
🧩 Node.js (optional) formatting checks (Prettier) if you edit Markdown or HTML
🌐 Mininet-SDN (optional) controlled virtual topologies SDN and routing related activities

The ASE laboratory route uses the MININET-SDN VirtualBox appliance. Students can use the same appliance on their own computers; WSL2 + Ubuntu + Docker Engine is a separate alternative for compatible exercises. The full installation is documented in 00_TOOLS/Prerequisites/Prerequisites.md.


Quick start pathways

Choose the pathway that matches your context. Socket and container exercises can use the supported alternatives below. Mininet remains required for the exercises that explicitly use its topologies; Portainer is optional.

Pathway A: read only (no installs)

  • Use GitHub to read the materials.
  • Start with current-outline.md then follow into 03_LECTURES/ and 04_SEMINARS/.

Pathway B: Python only (no Docker, no Mininet)

This supports early seminars and many lecture scenarios.

git clone https://github.com/antonioclim/COMPNET-EN.git
cd COMPNET-EN
python -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip

Where additional Python packages are needed, the relevant seminar directory will specify them.

Pathway C: Portainer (optional container interface)

Use the Portainer setup guide. For the MININET-SDN route, run the helper inside the VM:

bash 00_TOOLS/Portainer/INIT_GUIDE/portainer-init.sh

The local interface uses port 9050. Connect from Windows through the SSH tunnel in the setup guide. Port 9000 is reserved for the S10 tunnelling exercise.

Pathway D: MININET-SDN (ASE laboratory environment)

The MININET-SDN VirtualBox appliance is used in the ASE laboratories and can also be imported on students' compatible computers. Run Mininet, Open vSwitch and the guest Docker Engine inside that VM.


Clone the repository

Full clone

git clone https://github.com/antonioclim/COMPNET-EN.git
cd COMPNET-EN

Update an existing clone

git pull

Clone only what you need (sparse checkout)

Sparse checkout is useful when you want only a single lecture, a single seminar or a small subset for a given week. It reduces local clutter and supports a week-by-week workflow.

These commands require Git 2.25+.

Only lectures

git clone --depth 1 --sparse https://github.com/antonioclim/COMPNET-EN.git COMPNET-EN
cd COMPNET-EN
git sparse-checkout set 03_LECTURES 00_TOOLS

Only seminars

git clone --depth 1 --sparse https://github.com/antonioclim/COMPNET-EN.git COMPNET-EN
cd COMPNET-EN
git sparse-checkout set 04_SEMINARS 00_TOOLS

A single lecture (example: C08)

git clone --depth 1 --sparse https://github.com/antonioclim/COMPNET-EN.git COMPNET-EN
cd COMPNET-EN
git sparse-checkout set 03_LECTURES/C08 00_TOOLS

A single seminar (example: S12)

git clone --depth 1 --sparse https://github.com/antonioclim/COMPNET-EN.git COMPNET-EN
cd COMPNET-EN
git sparse-checkout set 04_SEMINARS/S12 00_TOOLS

A full week bundle (example: Lecture 05 and Seminar 05)

git clone --depth 1 --sparse https://github.com/antonioclim/COMPNET-EN.git COMPNET-EN
cd COMPNET-EN
git sparse-checkout set 03_LECTURES/C05 04_SEMINARS/S05 00_TOOLS

Move to the next week without recloning

If you already have a sparse checkout, you can switch what is present in your working tree.

# example: switch from Week 05 to Week 06

git sparse-checkout set 03_LECTURES/C06 04_SEMINARS/S06 00_TOOLS
Advanced: reduce download size (partial clone)

If your Git version and network support it, you can combine sparse checkout with a partial clone. This can reduce the initial download because file contents are fetched on demand.

git clone --depth 1 --filter=blob:none --sparse https://github.com/antonioclim/COMPNET-EN.git COMPNET-EN
cd COMPNET-EN
git sparse-checkout set 03_LECTURES/C01 04_SEMINARS/S01 00_TOOLS

Verify your lab environment

Before S01 you should validate that the baseline tools are working.

bash 00_TOOLS/Prerequisites/verify_lab_environment.sh

The script checks for core commands and expected versions. If it reports missing components, follow 00_TOOLS/Prerequisites/Prerequisites.md.


How to run a seminar

Seminar directories are written as a sequence of short parts. You should follow the order because later tasks assume earlier artefacts.

A pragmatic workflow is:

  1. Open the seminar README for the context and evidence expectations.
  2. Read each part file in order. Scenario files frame the experiment. Task files state what you must produce.
  3. Run commands from inside the seminar directory so relative paths work.
  4. Capture evidence as you go:
    • terminal outputs
    • .pcapng packet captures
    • Docker logs
  5. Clean up between attempts. For a Compose seminar, use its documented docker compose -f <file> down command. Add -v only when the exercise explicitly calls for deleting that project’s persisted data and you have saved the required evidence.

Week-by-week map

This is both a navigation tool and a dependency map.

Week Lecture Seminar Primary focus Typical stack
01 C01 Network fundamentals S01 Wireshark and netcat observation and tooling literacy Wireshark
02 C02 OSI and TCP/IP models S02 sockets (TCP and UDP) application level reasoning Python, Wireshark
03 C03 intro network programming S03 broadcast, multicast and tunnelling UDP patterns Python, Wireshark
04 C04 physical and data link S04 custom protocols framing, parsing and robustness Python
05 C05 addressing and subnetting S05 subnetting and simulation address planning as a design skill Python
06 C06 NAT, ARP, DHCP, NDP and ICMP S06 SDN and topologies controlled network behaviour Mininet-SDN (optional), Wireshark
07 C07 routing protocols S07 capture filters and scanning observation discipline and safety Python, Wireshark
08 C08 TCP, UDP and TLS S08 HTTP servers and proxies protocol evolution and trade-offs Python, Docker, Wireshark
09 C09 session and presentation S09 FTP patterns state and representation Python, Docker
10 C10 HTTP(S) S10 DNS, SSH and FTP in containers service composition Docker
11 C11 FTP, DNS and SSH S11 load balancing reverse proxies and failure modes Docker
12 C12 SMTP, POP3 and IMAP S12 JSON-RPC, Protobuf and gRPC structured APIs Python, Docker
13 C13 IoT and network security S13 scanning and vulnerability reasoning security literacy Docker, Wireshark
14 C14 revision and integration S14 recap and assessment integrate evidence, explain behaviour and prepare for assessment Python, Docker, Wireshark
Course coverage: lecture and seminar indices

Lecture index is maintained in 03_LECTURES/README.md. Seminar index is maintained in 04_SEMINARS/README.md.

  • Lectures: 03_LECTURES/C01/ … 03_LECTURES/C14/
  • Seminars: 04_SEMINARS/S01/ … 04_SEMINARS/S14/

Diagrams and rendering

Diagrams are authored in PlantUML so you can regenerate them and avoid diagram drift.

  1. Download plantuml.jar (kept out of Git)
bash 00_TOOLS/plantuml/get_plantuml_jar.sh
  1. Render diagrams for one lecture or one seminar
cd 03_LECTURES/C01/assets
bash render.sh
  1. Render all diagram sets (lectures, seminars and projects)
bash 00_TOOLS/plantuml/get_plantuml_jar.sh

find . -path "*/assets/render.sh" -print0 | while IFS= read -r -d '' f; do
  (cd "$(dirname "$f")" && bash ./render.sh)
done

With and without Portainer

Portainer is a management interface. Docker Engine is what actually runs the containers.

You can deliver and complete the course without Portainer. The value of Portainer is observability for beginners and rapid inspection during seminars.

Common action Portainer approach CLI equivalent
list containers Containers view docker ps
view logs container logs panel docker logs -f <container>
inspect networks Networks view docker network ls and docker network inspect <net>
bring up a stack Stacks feature (if enabled) docker compose up -d
stop and clean container stop and remove docker compose down (add -v only for an intended data reset)

With and without Mininet-SDN

Mininet-SDN is not a prerequisite for the whole module. It is a specialised environment for controlled topology work.

Capability Without Mininet-SDN With Mininet-SDN
service composition Docker networks virtual switches and hosts
routing demonstrations limited, container centric native routing style topologies
SDN flow experimentation not available available
required for most weeks selected tasks, mainly S06

If you do not have Mininet-SDN, you can still complete the majority of seminars. Where Mininet-SDN is expected, the seminar will state it explicitly and provide alternatives where feasible.


Quality checks and formatting

If you change the repository you should keep it deterministic. The following checks are safe to run locally from the repository root.

python3 -m venv .venv-qa
source .venv-qa/bin/activate
python -m pip install -r 00_TOOLS/qa/requirements.txt
python 00_TOOLS/qa/run_checks.py

If you edit Markdown or HTML, run formatting:

npm install
npm run format:check

# or check line endings and final newlines without installing npm packages
node format-offline.js --check
# Use --write only when you intend to apply those limited formatting changes.

Safety and scope

Several seminars include scanning and security related activities. You must restrict all scanning and testing to controlled laboratory networks and approved targets. Do not point these exercises at public infrastructure.


Licence and permitted use

The author approved Option A for the v1.5.0 candidate on 17 November 2026. LICENCE.md defines Category A educational content under CC BY-NC-SA 4.0, Category B source code and configuration under GPL-3.0-or-later and the reserved Category C paths in LICENCE_CATEGORY_C.txt. Component-specific third-party terms and permissions already granted take precedence. The applicable licence governs attribution and reuse; the policy adds no commercial restriction, research-citation condition or automatic co-authorship obligation to GPL-covered material. See the author decision and application record.

Suggested academic citation

Clim, A. (2025). Computer Networks — Course Kit (EN). Bucharest University of Economic Studies (ASE), Faculty of Economic Cybernetics, Statistics and Informatics (CSIE). https://github.com/antonioclim/COMPNET-EN

Repository structure

.
├── 00_APPENDIX
├── 00_TOOLS
├── 01_GUIDE_MININET-SDN
├── 02_PROJECTS
├── 03_LECTURES
├── 04_SEMINARS
├── CHANGELOG.md
├── LICENCE.md
├── current-outline.md
└── requirements-optional.txt

About

Computer Networks — Course Kit (EN) · v13.05.00 · 13 lectures · 13 seminars · team projects · PlantUML · ASE-CSIE · ing. dr. Antonio Clim

Topics

Resources

Stars

43 stars

Watchers

0 watching

Forks

Contributors

Languages