Smart Campus Network Simulation

This project presents a detailed simulation of a Smart Campus Network, developed using Cisco Packet Tracer. The aim is to replicate the structure and functionality of a modern university network with enhanced interactivity. The simulation includes role-based access, integrated services, and advanced security mechanisms. This project demonstrates the application of networking principles in a practical, real-world scenario.

A computer network is a group of interconnected devices that communicate to share resources and data. Here's a breakdown of key network types:

Essential networking devices include:

Our architecture is designed for a modern campus, emphasizing security and role-based access. The design includes:

The devices used include:

Network Design Choices and Justification

The design of this Smart Campus Network incorporates several key choices to optimize performance, security, and manageability:

• VLAN Segmentation: VLANs are used to segment the network, enhancing security and performance.
• Router-on-a-Stick: This cost-effective method uses sub-interfaces for inter-VLAN routing.
• Role-Based Access Control: The network is designed to provide different levels of access to network resources based on the user's role.
• Dedicated Server VLAN: Servers are placed in a separate VLAN to isolate them from user traffic.
• Static IP Addressing: Static IP addresses are used for servers and network infrastructure devices.

The simulation involves configuring devices and services.

Below are the core commands used in Cisco Packet Tracer to configure the Smart Campus Network. These are real Cisco IOS commands applied to routers and switches.

1. VLAN Configuration (on Switches)

VLANs (Virtual Local Area Networks) were configured to logically separate different user groups on the campus network. Each VLAN was assigned a unique ID:

• VLAN 10 – Students
• VLAN 20 – Professors
• VLAN 30 – Admins
• VLAN 40 – Guests
• VLAN 99 – Servers

On each switch, we used the CLI to create these VLANs and assign ports to them. This ensures that devices in different groups don’t communicate by default, increasing security.

switch> enable
switch# configure terminal
switch(config)# vlan 10
switch(config-vlan)# name STUDENTS
switch(config)# interface range fa0/1 - 5
switch(config-if-range)# switchport mode access
switch(config-if-range)# switchport access vlan 10

Each VLAN separates devices into logical groups, improving security and efficiency.

2. Router Sub-interface Setup (Router-on-a-Stick)

Since each VLAN is a separate broadcast domain, inter-VLAN communication requires routing. We implemented a Router-on-a-Stick setup using sub-interfaces on a single physical interface (GigabitEthernet 0/0). Each sub-interface was configured with:

• An encapsulation ID matching the VLAN (dot1Q)
• An IP address for that VLAN (used as the default gateway)

router> enable
router# configure terminal
router(config)# interface g0/0.10
router(config-subif)# encapsulation dot1Q 10
router(config-subif)# ip address 192.168.10.1 255.255.255.0
router(config)# interface g0/0.20
router(config-subif)# encapsulation dot1Q 20
router(config-subif)# ip address 192.168.20.1 255.255.255.0
...etc

This allows devices from different VLANs to reach each other, depending on the access rules (ACLs).

Sub-interfaces allow routing between VLANs using one physical interface.

3. Access Control Lists (ACLs)

ACLs are used to control traffic and enforce policies. We applied an ACL on the interface connected to the Guest VLAN (40) to restrict their access:

• Block guests from accessing internal networks
• Only allow them to reach the web server
• Allow normal traffic for other users

router(config)# access-list 140 deny ip 192.168.40.0 0.0.0.255 any
router(config)# access-list 140 permit ip any any
router(config)# interface g0/0.40
router(config-if)# ip access-group 140 in

This ACL logic simulates a real university policy: guests can browse public pages but not access sensitive data.

4. Syslog Configuration

We added a Syslog server to monitor important events in the network — such as interface status changes or configuration updates. It helps administrators troubleshoot and secure the network.

On the router, we enabled logging to the Syslog server located at 192.168.99.30:

router(config)# logging 192.168.99.30

When we performed actions like shutting down interfaces, the Syslog server captured the event, proving that our monitoring was active.

5. Email Configuration (Server Side)

The Email Server was placed in VLAN 99 with the IP address 192.168.99.20. We enabled both SMTP (Simple Mail Transfer Protocol) on port 25 for sending emails, and POP3 (Post Office Protocol v3) on port 110 for receiving. In the server’s configuration (under the Services tab), the email domain was set to campus.com. Multiple user accounts were created for testing email functionality, such as:

• admin@campus.com — used by an admin PC
• student1@campus.com — used by a student PC
• guest@campus.com — used to verify access restrictions

Devices were then configured in the Desktop tab → Email tool, where we entered their email address, username, and the SMTP/POP3 server IP. We tested sending and receiving emails within the allowed roles (students, professors, admins), and verified that guests could not send or receive, as blocked by ACLs.

Visual documentation of our network simulation implementation:

VLAN Configuration

Network Topology

Test Email Succeed

Email Test Failed

ACL Configuration

ACL Confirmed Access

ACL Denied Access

Syslog Events

Router Configuration

This project demonstrates how networking principles can be applied to design and secure a functional campus network. It involved planning, segmentation, configuration, and testing of services such as VLANs, email communication, and ACL enforcement. The final setup accurately reflects a real-world scenario of controlled digital communication within an academic institution.

This project was created by:

• Koussay Nefzi

Faculty of Science, Monastir – 2025