NET 150 - griffinsnest/tech-Jorunal-1 GitHub Wiki
Lab 1 Reflection
This week we tested some rudimentary network connectivity using common command-line prompts like ping, tracert, and nslookup. We learned what each command does, and what information each command gathers and shows us to allow us to record it. Basically, we were introduced to the concepts of IP addresses and hostnames and how to find and record the data surrounding them with these commands.
Lab 2.1 Reflection
In this lab we tested remotely connecting with the viewportal to a virtual machine running a Linux based OS. We also went over specific command used with the command prompt inside the VM to properly change a given user account's password, make an entirely new user, downloading applications through the command prompt, and being able to do all of these while using the root user's admin access to do so without needing to get permission to do those previous commands.
Lab 2.2 Reflection
In this lab we were introduced to the basic features and uses of Wireshark and how to use it along with commands when analyzing packet traffic. Specifically, we used them to monitor how ARP cache stores a list of IP addresses and MAC addresses your system goes through when traveling and Wireshark to see how MAC addresses are used in LAN communication.
- How to open and flush the ARP cache
- What does "-y" stand for in installation and how being added to a group works
- How to use Wireshark's display filter
Lab 3.1 Reflection
In this lab we tested how Address Resolution Protocol operations work and drew conclusions on how Layer 2 (MAC) and Layer 3 (IP) addresses interoperate. We did this through the use of the basic flow of ARP packets by pinging neighboring systems in the network. By understanding the role of broadcasts with ARP and how it is used between hosts on a LAN we will understand how the layers work together.
Lab 4.1 Reflection
In this lab we configured and observed a simple routed network within packet tracer. We set up a simple three-computer configuration that were all connected through a multilayered switch. After this, we simply have to set up the proper IP addresses and subnet masks for each computer, and then match each computer's IP address to the default gateway by setting it as well. Finally for set up just go and set up the matching IP addresses and mask for the ports on the Switch. After this it is simply using one of the computer's command prompt to ping one of the others you set up.
Lab 4.2 Reflection
In this lab, we used Packet Tracer to simulate a small network consisting of 4 computers and a switch. We focus on examining the address table of the switch and ARP tables of the computers. We do this by initiating some form of communication between the machines and then watching the transfer between the frames. Through this looking at the frame contents we will better understand how ARP and Ethernet connections work.
Lab 4.3 Reflection
In this lab, we used Packet Tracer to simulate a small network consisting of a computer, two switches, and a server. We focus on observing how this simple Network utilizes a router to connect the two separate networks of the computer and the server. We did this by learning how to properly set up the connections from a network to its switch, to the router then in reverse to the intended other networks.
Lab 5.2 Reflection
In this lab we continued with the example network we made in class, based on lecture 5.2 as well as the utility spreadsheet created that calculated the correct addresses for this network. We will use Packet Tracer to Model the creat /27 networks for the Skiff, Foster, and Joyce halls from scratch. We will introduce how to add a new module to your router as well as use both serial links and RIP to allow routers to communicate their routes with one another.
Lab 6.1 Reflection
In the previous lab, we implemented a small classful subnetting scheme consisting of five /27 networks to support our hypothetical network between buildings on campus. While it worked fine, it should have been noticed that though easy to calculate, there was a good deal of IP address/host space waste. So in this lab, you are going to reconfigure the existing network (routers and hosts) to use a Variable Length Subnet masking scheme (VLSM) to deal with this waste particularly with the two point to point serial links. In this case, since both of those networks in particular only use 2 hosts, so a /30 network fits the space needed much better.
Lab 6.2 Reflection
In the original Peter Packet Video that introduced us to networking with the application, Peter used Classful Subnetting with no regard to the number of hosts in each subnet, leading to inefficient IP allocation. So in this lab, the goal is to clean up the mess by appropriately allocating subnets using VLSM. Basically, this lab acts as a culmination of all that we have done so far in Packet Tracer. From finding the right CIDR for the number of hosts needed per subnet, to the setting up of routers for the network to properly connect.
Lab 9.2 Reflection
In this lab, we continue to work with static routing using an example pulled directory from CISCO's CCNA track. More specifically, in the lab we observe and reflect on the implications of internetworking when connecting multiple routers. The main goals were to be able to understand the limitations of routers, how to connect networks that are not directly connected using the CISCO cli to configure simple static routes to allow packets to cross multiple routers to a remote network.
*Configuring and displaying static routes
*Why not use static routes on every newtwork
Lab 10.1 Reflection
In this Packet Tracer lab, we try to gain a better understanding of how to configure and troubleshoot RIP version 2. More specifically, we will configure a basic lab topology, enable RIPv2 on the routers and configure them to advertise their networks. We do this by using the same starter Packet Tracer File as a previous lab, only now we will configure the network using only RIP. This means that the routers will learn about neighboring routers and their networks through RIP Broadcasts only.
*Configuring RIPv2 on Cisco & how to show the routes
Lab 10.2 Reflection
This lab acts as a culmination of all the previously learned parts of setting up a network and its subnets. First, we will need to build a classless routing table for a small network of 2 sites - East and West. This requires subnetting the organization's network space of 182.150.8.0/21 to accommodate the needed 5 networks of the company. The starting address and the last usable IP address in the last network are provided and it is up to us to figure out how to make them. Then it is our job to make the network in Packet Tracer, and connect the different subnets in order to make it possible for all of them to communicate with each other, preferably with RIPv2.
Lab 11.1 Reflection
This lab is an introduction to VLANS, aka Virtual LANs. A VLAN is a group of devices on one or more subnets that are configured to communicate as if they were attached to the same wire/LAN when they are in fact located on a number of different subnet segments. Because VLANs are based on logical instead of physical connections, they are extremely flexible and thus easier to connect and set up. To showcase this we use a starting Packet Tracer File that will be configured to utilize VLANs to have three separate devices on three separate subnets act like they are on one connected network.
*Creating and Configuring VLANs
Lab 12.1 Reflection
This lab focuses on investigating a layer 4 protocol called the Dynamic Host Configuration Protocol (DHCP), where in this case a host system such as our xubuntu Virtual Machine requests their own IP address as opposed to having it statically set by a systems administrator. Here we will simply use Linux commands to release and renew your dhcp address, and capture the interchange of data with Wireshark to see how it works.
Lab 12.2 Reflection
In this Lab, we configured an access point, allowing for remote access from PCs as well as wireless connectivity with WPA2 security. Along with that we manually configured PC wireless connectivity by entering the router SSID and password. To put it simply we manually set up a wireless router and configured PCs to connect to it and then a far-off connected Router.
Assignment 12 Reflection
In this assignment, we pick a wireless network of our choosing to connect to using our laptops or computers, and see the intricacies of how the connection is set up. These intricacies include the MAC address of the Wireless adapter, the SSID of the network you're connecting to, the 802.11 version that the device's wireless card is using, and other such aspects.
Lab 13.1 Reflection
In this lab, we pick a wireless web browser-based TCP connection from our Xubuntu client to a server of your choice. We do this by pinging a given web browser's SSID name and use a Wireshark capture to document the connection's back and forth of information sharing.
Lab 13.2 Reflection
In this lab, as a pair we worked to understand more about the connections between clients and a server. We must work in pairs because are two roles. One will host the client application, in the case of this lab a web browser, and the other will host the server application, a python http server. This to help us in understanding the finer points of source and destination layer 4 ports.