Team_4_Lab_1
docx
keyboard_arrow_up
School
Liberty University *
*We aren’t endorsed by this school
Course
355
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
7
Uploaded by DeanBookPartridge8
Course #
Team 4
Intro to Cypherpath SDI
CSIS 355
9/23/2021
Week 4, Lab 1
Team Members:
Isaac Hanna
Jacob Lohman
Blake Bonheim
Ryan O’Connor
Noah Wiggins
Tyler Dix
Michael Ccreeden
Title
The goals of the lab-Familiarize ourselves with
o
Cypherpath
o
VM usage in the environment
o
Kali Linux Commands
Abstract
In this lab, we are tasked to create a network and two workstation virtual
machines that are on the created network using the Cypherpath SDI. This is done by first
creating the network, dropping it into the group SDI, and configuring the network
properties as the instructions told us to. Then, we created two Kali Linux workstation
virtual machines and dropped them on top of the network that was already in our group
SDI. After successfully connecting the two workstations to the network, we powered up
and logged into the workstations using the given credentials. We then pinged each other’s
workstations using the respective IP addresses to test the connection and looked through
the ICMP traffic by using tcpdump.
Introduction
The purpose of this lab is to configure, use, test, and analyze a static IP with a
Kali Linux workstation. To do this, a network will be setup within the Cypherpath SDI
with two workstations on the network. One workstation will the used to “ping” the other
through the network. When setup properly, will the interaction between the two
workstations be visible in the ICMP traffic shown by the tcpdump of the second
workstation?
Method
Log in to cypherpath
Click on the VM template tab
Create a virtual machine (VM) template in Cypherpath
Fill in the required fields
Use the Kali image in the disk drive to give the VM a system to run on
Save the VM
Enter your team’s cloud
Ensure the cloud is activated by pressing the start button
Add a network from the toolbox bar by dragging and dropping the icon
Set up an IPv4 DHCP scope for the network by selecting a starting and end range
as well as a lease time
Add the Kali workstation directly on top of the network to establish a direct
connection
Do this again with a second Kali workstation
Once the connections are established, turn on both systems
Once they have booted up, connect to the first workstation
Once connected open the Terminal and ping the opposing workstation’s IP
address using command “ping xxx.xxx.xxx.xxx”
Then connect to the alternate workstation
Use command “sudo tcpdump” to collect the information being sent from the first
workstation’s ping
Look over the ICMP traffic coming from the initial kali workstation
Shut down both workstations and the network
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Results
Upon completing the lab, we were able to successfully set up the environment and ping
the two workstations that were connected to the switch. Figures 1-3 below demonstrate these
findings. The first of these displays our SDI configured with the net-switch and several Kali
workstations connected.
Figure 1:
SDI Setup
After that, the next two figures display the first workstation pinging the second workstation, and
then the tcpdump on the second one respectively. The tcpdump shows that the workstation is
being continually pinged by a specific ip address, which can easily be determined is the other
workstation by checking its stats in the SDI page.
Figure 2:
Workstation 1 after pinging Workstation 2
Figure 3:
Workstation 2’s tcpdump after being continually pinged by Workstation 1
Discussion
When using the “sudo tcpdump” within the linux terminal, our results are, at first glance, a lot to
take in. However, after doing some research, we discovered that the results were all the traffic
flowing to and from eth0 or ethernet. Within our VM, tcpdump was capturing and outputting all
the packets that were being captured within ethernet, specifying protocol, source ip and port,
destination ip and port, data length, etc
....
Since we did research on what exactly the output was
so we could have a better understanding of what we were looking at, we did not have any
questions or issues arise at this current moment, but if any to occur, we certainly we address
them as a team and with the professor.
Future Plans
Our team does not yet have specifically assigned roles. As the labs become more complex
and we identify the strengths and weaknesses of each team member, more specialization will
become practical. At this point, we work together on the labs, allowing each team member to
gain an understanding of what we are doing. We then divide the lab report and complete the
assignments in a collaborative manner but without intentional specializations.
Conclusion
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
This first lab provided an introduction to Cypherpath as well as to the basics of networking. We
learned to engage with the Cypherpath environment as we configured and deployed virtual
machines, learned about switches as we connected the virtual machines via a switch, configured
the dhcp server, and noted the assigned ip addresses, and learned about basic network
communication as we pinged one virtual machine with the other. These understandings will be
very helpful as we move tackle future labs.