Skip to content

About

I created a Campus Area Network (CAN) for a hypothetical company (called HawkNode Security), where I implemented typical industry practices while designing and configuring the network.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

32 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

HawkNodeSecurity Network

Overview • Upcoming Features • Documentation Menu

Overview

I created a Campus Area Network (CAN) for a hypothetical company (HawkNode Security), where I implemented typical industry practices while designing and configuring the network.

I wanted to do this project to demonstrate my ability to practically set up and configure enterprise networks that I have previously learned while studying for my CCNA.

NOTE: Due to the Activity Wizard, it may be harder to load the .pka file on some devices. For better performance, you can run the unlocked .pkt version.

Upcoming Features (as of 8/18/2026)

Here's what's coming in the future (Phase 3 -- Winter 2026/ Spring 2027, exact date TBD):

  • Advanced Access Control Lists
  • ASA Firewall Devices + DMZ Network Design
  • Access List Controls for certain services
  • Port Security (for switches)
  • Email network
  • and more!!

Phase 2 Upgrades for Summer/Fall 2026 (Currently In Progress)

  • Improving network addressing by using /31 subnets for transit links and /16 for campus sites.
  • Removed the Salt Lake City, LA, Minneapolis, and NYC campuses and created the San Francisco, Denver, Chicago, and Boston campuses
  • Implementation of HSRP (Hot Standby Router Protocol) and collapsed core design to increase network redundancy.
  • Implemented BGP and EIGRP across sites to make the implementation of routing protocols more realistic with industry standards.
  • Implemented NAT (Network Address Translation) between sites to improve realism.
  • Implemented interface descriptions between routers, helping to make future configuration easier.
  • Removed office images and replaced them with zones in order to make the topology more understandable.
  • Removed the console passwords in favor of keeping the enable mode password only in order to balance network security with easier accessibility.
  • Rewrote documentation as needed.

Documentation Menu

Network Design/Topology • Router IP Addresses • Host Device IP Addressing • Routing Protocol Information • WiFi Networks • VLAN Information • Etherchannel Information • Passwords & Security

Network Design/Topology

HawkNode Security Network Toplogy

The network is set up in a partial mesh configuration, with 2-4 connected campuses per site (via Fiber) and 2 internal connections (via copper cabling).

Router IP Addresses

Device Name Interface IP Address OSPF Info (Process, Area) Router ID
WashDC-RT G0/0 1.1.1.1/24 (1,0) 1.1.1.1
DC-RT G0/1 2.2.2.2/24 (1,0)
DC-RT G0/2 See Network Map (1,1)
ATL-RT G0/0 1.1.1.2/24 (1,0) 3.3.3.1
ATL-RT G0/1 3.3.3.1/24 (1,0)
ATL-RT G0/2 See Network Map (1,1)
AUS-RT G0/0 4.4.4.1/24 (1,0) 4.4.4.1
AUS-RT G0/1 3.3.3.2/24 (1,0)
AUS-RT G0/2 See Network Map (1,1)
LA-RT G0/0 4.4.4.2/24 (1,0) 5.5.5.1
LA-RT G0/1 5.5.5.1/24 (1,0)
LA-RT G0/2 See Network Map (1,1)
SLC-RT G0/0 7.7.7.1/24 (1,0) 7.7.7.1
SLC-RT G0/1 5.5.5.2/24 (1,0)
SLC-RT G0/2 See Network Map (1,1)
SEA-RT G0/0 7.7.7.2/24 (1,0) 8.8.8.1
SEA-RT G0/1 8.8.8.1/24 (1,0)
SEA-RT G0/2 See Network Map (1,1)
MIN-RT G0/0 See Network Map (1,1) 9.9.9.1
MIN-RT G0/1 8.8.8.2/24 (1,0)
MIN-RT G0/2 9.9.9.1/24 (1,0)
NYC-RT G0/0 See Network Map (1,1) 2.2.2.1
NYC-RT G0/1 2.2.2.1/24 (1,0)
NYC-RT G0/2 9.9.9.2/24 (1,0)

Host Device IP Addressing

As shown above on the map, the IP Addressing follows a scheme where each campus branch has its own IP Network (ex: Austin branch has a network of 10.20.0.0/16). From there, the third octet is assigned to the VLAN (ex: VLAN 70 in the Austin office would have a network of 10.20.70.0/24). From there the last IP octet is dedicated to the host.

Most of the IPs are handed out via DHCP (Dynamic Host Configuration Protocol) either through the CORE1 router or a specific-site server, but there are a couple of static IPs (listed below) for critical services:

Server Name IP Address Subnet Mask Default Gateway
Web-Server 10.20.60.5 255.255.255.0 10.20.60.1
File-Server 10.20.60.6 255.255.255.0 10.20.60.1
Backup_Server_1 24.24.24.2 255.255.255.0 24.24.24.1
Backup_Server_2 24.24.24.2 255.255.255.0 24.24.24.1

Routing Protocol Information

BGP EIGRP HSRP

WiFi Networks

There will be two main WiFi Networks: HNS-Employees and HNS-Guest at each of the branches. The details are documented below:

Network Name Password 2.4 GHz Channel
HNS-Employees tiYLkcO0YnN07^ 1
HNS-Guest None 11

VLAN Information

VLAN Name VLAN ID
Wired/PC 10
WiFi 20
Office-Devices 30
Management 40
Voice-Traffice 50
Servers 60
Native 75
unusedPorts 200

Etherchannel Information

All etherchannels are configured in PAgP (Cisco proprietary EtherChannel protocol)

Interface Range Group Number
f0/1-3 1

Passwords & Security

Login Block (Router ONLY)
*All login blocks will be set for the following format:
login block-for [180 seconds] attempts [3] within [60 seconds]

Network Address Translation (Router ONLY)
Configuration items TBD

Access Control Lists (Router ONLY)
Configuration items TBD

Switchport Security (Switch ONLY)
Configuration items TBD

Console/Enable Mode Passwords are configured on network equipment and follow this format (in lowercast): [SITE][EDGE, CORE, or SWITCH][en] ex: auseden would be for Austin's edge switch
While this format isn't really secure, this is meant to be for demonstration purposes as well as make network configuration easier.

Console Mode Password Device Name Enable Mode Password
Con-NYCRTNYC-RTEnb-NYCRT
Con-NYCS1NYC-S1Enb-NYCS1
Con-NYCS2NYC-S1Enb-NYCS2
Con-NYCS3NYC-S3Enb-NYCS3
Con-NYCS4NYC-S4Enb-NYCS4
Con-DCRTDC-RTEnb-DCRT
Con-DCS1DC-S1Enb-DCS1
Con-DCS2DC-S2Enb-DCS2
Con-DCS3DC-S3Enb-DCS3
Con-DCS4DC-S4Enb-DCS4
Con-LARTLA-RTEnb-LART
Con-LAS1LA-S1Enb-LAS1
Con-LAS2LA-S2Enb-LAS2
Con-LAS3LA-S3Enb-LAS3
Con-LAS4LA-S4Enb-LAS4
Con-LAS5LA-S5Enb-LAS5
DEN-EDGEdeneden
DEN-CORE1denco1en
DEN-CORE2denco2en
DEN-SW1densw1en
DEN-SW2densw2en
AUS-EDGEauseden
AUS-CORE1ausco1en
AUS-CORE2ausco2en
AUS-SW1aussw1en
AUS-SW2aussw2en
Con-SLCRTSLC-RTEnb-SLCRT
Con-SLCS1SLC-S1Enb-SLCS1
Con-SLCS2SLC-S2Enb-SLCS2
Con-SLCS3SLC-S3Enb-SLCS3
Con-SLCS4SLC-S4Enb-SLCS4
Con-SEARTSEA-RTEnb-SEART
Con-SEAS1SEA-S1Enb-SEAS1
Con-SEAS2SEA-S2Enb-SEAS2
Con-SEAS3SEA-S3Enb-SEAS3
Con-SEAS4SEA-S4Enb-SEAS4
Con-MINRTMIN-RTEnb-MINRT
Con-MINS1MIN-S1Enb-MINS1
Con-MINS2MIN-S2Enb-MINS2
Con-MINS3MIN-S3Enb-MINS3
Con-MINS4MIN-S4Enb-MINS4

About

I created a Campus Area Network (CAN) for a hypothetical company (called HawkNode Security), where I implemented typical industry practices while designing and configuring the network.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors