Skip to content
All systems
On GitHubMALULEKE-KS

Tshimo Agri Network

CMPG 325 individual network design project — Tshimo Agri Supplies (CMPG325-2026-042)

  • Cisco Packet Tracer
  • VLANs
  • HTML
View the source
Started
August 2026
Last push
3 days ago
Commits this year
10

Written by AI from the repository · updated 5 days agoAI

The brief

A computer-networks semester project (CMPG 325): design the network for a fictional agricultural supplier, simulate it in Cisco Packet Tracer and isolate an assigned fault. The design has to absorb two future changes without re-addressing — a branch office that may open within 18 months, and eight new staff joining one department.

The design

  • Topology — one edge router (router-on-a-stick, with NAT/PAT to the internet service provider), a core switch with 802.1Q trunking, and an access switch per department.
  • Addressing — the 10.23.0.0/16 block, split into four business VLANs plus a management VLAN. Every VLAN gets a uniform /26 regardless of current headcount, so growth never forces a re-address.

How the work is kept

The repository separates a living design record (docs/: requirements, physical and logical topology, the addressing plan, change requests) from frozen graded submissions, one folder per milestone — later edits never rewrite what was handed in. Device configurations, connectivity evidence and the fault-isolation write-up each have their own place.

Where it stands

Milestone 1, the client design review, is complete; the later milestones follow during the semester.

Activity

How it's moving.

26 weeks agothis week

10 commits in the last 26 weeks · 4 in the last 4

Latest commits

  1. Milestone 2 implementation, testing and fault-isolation evidence
  2. Add baseline Packet Tracer topology and physical build evidence
  3. Draft IOS configurations for switches, R1 and ISP, plus server setup
  4. Add Milestone 2 execution map and Packet Tracer build walkthrough
  5. Add signing date to Milestone 1 declaration page
  6. Ignore local session config file
  7. Rework design language, enlarge topology diagrams, tighten copy
  8. Restructure repo into docs/submissions layout, rebuild topology diagrams
Skills

What it proves.