21 Static Networking Part 1
Mathew J. Heath Van Horn, PhD and Jacob Christensen
Up to this point, we have only used one router in our working environments. However, you will rarely work on a network with only a single because the whole point of an enterprise network is to connect multiple LANs into a unified cohesive network.
In this lab, we will create and connect three LANs via routers. We introduce you to static routing solutions so you can become familiar with routing procedures. Static routing is impractical mainly because it is very manpower intensive to maintain and prone to human error.
Estimated time for completion: 70 minutes
Learning objectives
- Successfully create two functional LANs:
- Red (DHCP + 2 PCs)
- Blue (DHCP + 2 PCs)
- Configure two routers to use static routing so all devices can communicate
Prerequisites
Deliverables
- Screenshot of GNS3 workspace with labels
- Screenshot of Wireshark IMCP packets showing a Red device successfully pinging a Blue device
Resources
Contributors and Testers
- Dante Rocca, Cybersecurity Student, ERAU-Prescott
- Sawyer Hansen, Cybersecurity Student, ERAU-Prescott
Overview
You are now going to combine your subnet, DHCP, and router configuration skills to create two networks, each with their own gateway routers. Your final product should look similar to the following.
Phase I -Build the Network Topology
The following steps are to create the baseline for completing the lab. It makes assumptions about learner knowledge from completing previous labs. Going forward, we will be using Ubuntu Servers for all network servicing needs. For those who have limited computational resources, consider using TinyCore as an alternative.
- Start GNS3
- Create a new project: LAB_07
- Build the Red subnet with the following specifications:
- IP address space – <IP_ADDRESS>/24
- Two client machines – VPCS
- One switch – Ethernet switch
- One DHCP server – Ubuntu Server VM (isc-dhcp-server)
- One router – MikroTik CHR
- Connect the server and PCs to their associated switch
- Connect the switch to the router’s ether1 interface
- IP address space – <IP_ADDRESS>/24
- Configure the MikroTik router to act as Red’s gateway
NOTE: Refer to Chapter 16, Phase II, Step 4 for more information.
- Set a new hostname to reflect its new purpose
> system identity set name=RED-ROUTER
- Set ether1 with the IP address <IP_ADDRESS> for the Red network
> ip address add address=<IP_ADDRESS>/24 interface=ether1
- Verify that it was taken
> ip address print
MikroTik Configuration Preface
By default, MikroTik routers will have a DHCP client enabled on interface ether1, which will automatically request an IP address once the network’s DHCP server is online. To avoid unnecessary packet traffic (and troubleshooting headaches), disable this client as part of the router’s setup routine. You can identify interfaces with DHCP clients enabled via the “dynamic” (D) flag that appears next to its identification number.
List all DHCP clients currently enab