Using a simple OSPF configuration, we are able to get full adjacency to the backbone network. This setup has the suitable network & wildcard mask.
ip routing
router ospf 1
network 10.0.2.0 0.0.0.63 area 1
My 2014 networking Bachelors project for MIT. Going towards my Bachelor in Electrical Engineering with a Computer Networking Specialization.
Tuesday, 27 May 2014
Monday, 26 May 2014
Beginning Wireless Configuration pt1
Starting my wireless configuration.
As the interface is modular, the name is: (service-module Integrated-Service-Engine 1/0)
Will continue learning to configure correctly tomorrow.
As the interface is modular, the name is: (service-module Integrated-Service-Engine 1/0)
Will continue learning to configure correctly tomorrow.
Thursday, 22 May 2014
My Components
Wireless:
Cloud Services/Servers:
Penetration Testing:
Additional:
- The wireless will be provided for guests & staff.
- The guest wireless is only for access to the internet
Cloud Services/Servers:
- Services
- File, mail & web servers.
- Video on demand (with prioritization)
- The location
- The physical connections in relation to other hardware
Penetration Testing:
- Breaking the network
- Exploits
- Software
- Documenting
Additional:
- Creating an interface for the cloud services.
Creating the baseline network pt1
The first part we needed to decide upon and create was the physical topology & accompanying addressing scheme.
With the hardware available to us in the network room, we decided to primarily utilize layer 3 switches for our backbone (core/distribution). This was due to the fact that these switches were both able to do routing (like a router) and the amount of fast Ethernet ports (24) in comparison to the typical (2) on a router. This is both cost effective and still provides good performance.
Using the 10.0.0.0/8 addressing block:
Students: 10.2.0.1 - 10.3.255.254 /15
Academic Staff + WLAN: 10.1.0.1 - 10.1.255.254 /16
Registry: 10.0.0.1 - 10.0.0.126 /25
Payroll: 10.0.0.129 - 10.0.0.254 /25
Management: 10.0.2.1 - 10.0.3.254 /23
Guest WLAN: 10.100.0.1 - 10.100.255.254 /16With the hardware available to us in the network room, we decided to primarily utilize layer 3 switches for our backbone (core/distribution). This was due to the fact that these switches were both able to do routing (like a router) and the amount of fast Ethernet ports (24) in comparison to the typical (2) on a router. This is both cost effective and still provides good performance.
![]() |
| BAS="Building 'A' Switch" CENS="Central Switch" BBS="Building 'B' Switch" |
For each of the two buildings in our network, there'll be two switches at the core. For redundancy, there are multiple connections between each switch. The central switches will then have connections to two routers, one as a backup connection.
Creating the baseline network pt3
Left to configure:
VLAN configuration:
VLAN configuration:
- CENS1 will be a VTP Server (running Version 3, as Primary Server, if possible) as well as CENS2 (also running Version 3, as secondary server.). All other switches will be configured as VTP Clients in order to propagate VLAN's across the network.
Spanning Tree:
- Setting up Rapid-PVST to quickly propagate information
Creating the baseline network pt2
To increase the speed of each connection between each device in our core network, we have utilized Etherchannel. This treats each group of multiple connections as one, therefore creating a faster connection.
Here's an example of the configuration that we can insert in to one of our central switches.
#CenS1
interface port-channel 1
no switchport
ip address 10.0.2.1 255.255.255.252
exit
interface range fastethernet0/1-2
no switchport
channel-group 1 mode active
exit
interface port-channel 2
no switchport
ip address 10.0.2.5 255.255.255.252
exit
interface range fastethernet0/3-4
no switchport
channel-group 2 mode active
exit
interface port-channel 3
no switchport
ip address 10.0.2.9 255.255.255.252
exit
interface range fastethernet0/5-6
no switchport
channel-group 3 mode active
exit
interface port-channel 4
no switchport
ip address 10.0.2.13 255.255.255.252
exit
interface range fastethernet0/7-8
no switchport
channel-group 4 mode active
exit
interface port-channel 5
no switchport
ip address 10.0.2.17 255.255.255.252
exit
interface range fastethernet0/9-10
no switchport
channel-group 5 mode active
exit
Here's an example of the configuration that we can insert in to one of our central switches.
#CenS1
interface port-channel 1
no switchport
ip address 10.0.2.1 255.255.255.252
exit
interface range fastethernet0/1-2
no switchport
channel-group 1 mode active
exit
interface port-channel 2
no switchport
ip address 10.0.2.5 255.255.255.252
exit
interface range fastethernet0/3-4
no switchport
channel-group 2 mode active
exit
interface port-channel 3
no switchport
ip address 10.0.2.9 255.255.255.252
exit
interface range fastethernet0/5-6
no switchport
channel-group 3 mode active
exit
interface port-channel 4
no switchport
ip address 10.0.2.13 255.255.255.252
exit
interface range fastethernet0/7-8
no switchport
channel-group 4 mode active
exit
interface port-channel 5
no switchport
ip address 10.0.2.17 255.255.255.252
exit
interface range fastethernet0/9-10
no switchport
channel-group 5 mode active
exit
The Baseline Network
Working together with Nathan, we'll be creating and sharing a baseline network.
The network we're creating is for 2 new buildings in an already existing school network. However, it is treated as it's own individual network.
The parts shared between the two of us are:
The network we're creating is for 2 new buildings in an already existing school network. However, it is treated as it's own individual network.
The parts shared between the two of us are:
- Designing the topology
- The addressing scheme
- Connectivity
- Choosing baseline protocols
- Building the model
My 2014 Project Focus
For my final year Bachelors project I decided on 3 main research topics.
They are:
Wireless networking
Cloud Computing/Servers
Penetration (Security) Testing
They are:
Wireless networking
Cloud Computing/Servers
Penetration (Security) Testing
Subscribe to:
Comments (Atom)


