Sukhraj Singh
All projects

Networking · 2025

Campus Network

Connecting departments with a segmented network design.

Network simulationIndependent project

My contribution

I designed the two-site topology, segmentation, service paths and validation plan.

Evidence

Five topology views, configuration excerpts and packet-level validation guidance in the repository.

Scope & limitations

The Packet Tracer source is not published, and the four-VLAN summary does not yet match the ten-VLAN diagrams.

  • Cisco Packet Tracer
  • VLANs
  • Layer 3 Switching
  • WAN
  • DHCP
  • Routing

The research, briefly.

I documented a Cisco Packet Tracer design that connects a main campus, a branch campus and external services through explicit routing and switching boundaries. The repository topology shows eight main-campus VLANs, two branch VLANs, main and branch routers, multilayer switching, WAN point-to-point links and email, web and FTP services.

Sites
Main + branch campus
Segmentation
10 documented VLANs
Services
Email, web and FTP
Repository evidence
5 topology images
The problem & approach

The problem

I wanted to move beyond a flat departmental LAN and reason about a campus as a connected system. The design needed to separate users by role, preserve access to shared services and extend the same structure across a second site without making every failure look the same.

The approach

I documented a Cisco Packet Tracer design that connects a main campus, a branch campus and external services through explicit routing and switching boundaries. The repository topology shows eight main-campus VLANs, two branch VLANs, main and branch routers, multilayer switching, WAN point-to-point links and email, web and FTP services.

How it works
  1. 01Email service + cloud edge
  2. 02Main-campus router
  3. 03Main-campus multilayer core
  4. 04Eight building and service VLANs
  5. 05Web + FTP services
  6. 06Point-to-point WAN
  7. 07Branch router + multilayer switch
  8. 08Staff VLAN 90 + student VLAN 100
  • I separated the main campus into VLANs 10 through 80 for Admin, HR, Finance, Business, IT and Engineering, Arts, Student Lab and IT services.
  • I extended the design to a branch campus with VLAN 90 for staff and VLAN 100 for students behind a branch router and multilayer switch.
  • I connected the two campuses through a point-to-point WAN path and documented a separate cloud-facing email service path.
  • I placed web and FTP services on explicit main-campus network paths instead of treating every endpoint as an undifferentiated client.
  • I documented VLAN creation, access-port membership, 802.1Q trunking, inter-VLAN routing and DHCP configuration patterns.
  • I created a validation plan covering same-VLAN reachability, cross-VLAN paths, address assignment, end-to-end pings and simulation-mode packet tracking.
  • I added five topology views so the whole system, main campus, branch campus, buildings and cloud edge can be inspected separately.
Technical decisions & lessons

Hierarchical campus design

I used it to separate edge routing, campus distribution and end-device access responsibilities.

Ten VLANs

I used role-based segments to create intentional broadcast and troubleshooting boundaries across both sites.

Multilayer switching

I centralized the campus distribution path instead of sending every department directly to the WAN routers.

Point-to-point WAN links

I used explicit inter-site networks to make the main, branch and cloud paths visible.

DHCP and service networks

I separated client addressing from the web, FTP and email service paths the clients depend on.

Challenges

  • I had to keep VLAN membership, trunk carriage, gateway addressing, DHCP scopes and routed WAN networks consistent across far more than one department.
  • The repository's topology evidence is richer than its four-VLAN summary table, so I distinguish what the diagrams show from what the configuration excerpts document.
  • ACLs, STP tuning, EtherChannel, full OSPF and firewall policy remain future enhancements rather than completed claims.
  • The repository currently contains topology images and configuration excerpts but not the Packet Tracer source file, which is the clearest remaining reproducibility gap.

What I learned

  • I learned how a second site changes addressing, routing and failure-domain decisions that look simple inside one building.
  • I learned how hierarchical switching and role-based VLANs keep a larger topology understandable.
  • I learned to validate shared services and WAN paths separately from local switching behavior.
  • I learned why packet-level evidence and reproducible source files matter as much as a convincing topology image.

Branch segmentation · cisco

vlan 90
 name STAFF

vlan 100
 name STUDENTS

! branch networks: 192.168.9.0/24 + 192.168.10.0/24