"

36 Build the Baseline Environment (Eagle Net)

Dante Rocca and Kyle Wheaton

This section is for building a baseline environment. e.g. Your target.  We’ll call it Eagle Network, The Eagle, or just Eagle for reference.  It will contain many of the devices of a real network, but it will be abbreviated to save on host machine resources.  You will need to create this enterprise network first before starting any of the attack labs.

Learning Objectives

  • Create a network to serve as a target for offensive cyber operations

Prerequisites

Deliverables

  • Four (4) Screenshots are required:
    • GNS3 lab environment
    • Kali box receiving an IP address
    • Metasploitable3-Win box receiving an IP address
    • Metasploitable3-Linux box receiving an IP address

Resources

  • N/A

Contributors and Testers

  • Mathew J. Heath Van Horn, PhD
  • Jacob M. Christensen, Cybersecurity Student, ERAU-Prescott
  • Kyle Wheaton, Cybersecurity Student, ERAU-Prescott

Phase I – Setting up the network

This lab provides students with a guide to creating a network containing vulnerabilities to exploit while conducting a cyber attack. Much of this lab is directly from the DHCP Relay chapter. We highly recommend that once the GNS3 environment is complete; you save a master copy for reuse in future activities.
  1.  The goal is to create a network like this:
    Picture of the final product
    Figure 1 – Expected final result
  2. Create the following virtual machines and add them to the GNS3 environment:

    NOTE: Not every VM is used in every lab. To save resources, substitute a Tiny Core Linux box for any unused machine. This device swap will still show live targets on scans, but it only uses 50 MB of memory instead of 2 GB!

    1. TinyCore Linux in Chapter 5 – Installing Tiny Core Linux
    2. Ubuntu Server VM with all add-ons in Chapter 7 – Create a Linux Server
    3. Ubuntu Desktop in Chapter 11 – Create a Ubuntu Desktop
    4. Kali VM in Chapter 12 – Create a Kali Linux VM
    5. Both Metasploitable 3 (Windows and Linux) VMs in Chapter 13 – Create a Vulnerable Desktop VM
  3. Configure the Ubuntu Server to service DHCP requests
    1. Modify the /etc/netplan/*.yaml on the DHCP machine
      Screenshot of the network configuration file (.yaml)
      Figure 2 – Ubuntu Server netplan configuration
    2. Modify the /etc/kea/kea-dhcp4.conf file on the DHCP machine
      Screenshot of the DHCP config using KEA
      Figure 3 – Ubuntu Server DHCP configuration
    3. Ensure sure the daemon is active and running

      NOTE: As a reminder to:

      1. Start the service:

      > sudo systemctl start kea-dhcp4-server.service

      2. Restart the service:

      > sudo systemctl restart kea-dhcp4-server.service

      3. Start the service on system boot:

      > sudo systemctl enable kea-dhcp4-server.service

      4. Check service status:

      > systemctl status isc-dhcp-server.service

      5. Check the configuration for errors

      > kea-dhcp4 -t /etc/kea/kea-dhcp4.conf

      6. Check the system log for additional error messages

      > journalctl -xeu kea-dhcp4-server.service

  4. Assign each interface on the router an IP address according to the IP addresses in the image
  5. Configure the router as a DHCP relay for the Red and Blue networks
  6. Check to make sure that everything is working properly
    1. The attacker’s machine should receive an address from the 100.100.100.0/24 pool
    2. The blue machines should receive addresses from the 200.200.200.0/24 pool
End of Lab

Deliverables

3 Screenshots are needed to earn credit for this exercise:

  • Screenshot of Lab Environment
  • Screenshot of Kali VM receiving an IP address
  • Screenshot of Metasploitable3 VM receiving an IP address

License

Icon for the Creative Commons Attribution-NonCommercial 4.0 International License

Mastering Enterprise Networks 2e Copyright © 2024 by Mathew J. Heath Van Horn is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License, except where otherwise noted.

Share This Book