Lab Report #3

IP on Ethernet

Abstract - The Lab Virtual Machines were used to create 4 pings that will transmit from the Windows machine to various networks, and analyze the packet data that was transmitted. The process will be performed using tightvnc and Wireshark.

Introduction – The study was performed using a monitor workstation to execute a ‘tcpdump’ and listen for incoming packets as they are transmitted from one machine on the network, to various networks. After the pings were created on the windows machine, the data was collected into a pcap container and analyzed with wireshark in order to discern the various bits of data that was transferred.

Materials and Methods

* School PC * Tight VNC * Wireshark * Lab Manual

* Use tightVNC to connect to cgs4285-a.cs.fiu.edu:5921-22-23 * On the linux machine, use the ‘ifconfig’ command to add the default gateway * On the Windows machine, go to the Connection settings and add the default gateway * In the Monitor, remove the default route * After removing the default route and set up the specified route in the manual * Run tcpdump on the monitor station to listen for traffic on both networks * Start ping 1 * Start ping 2 * Start ping 3 * Start ping 4 * After running all 4 pings, kill the tcpdump processes * Copy the two pcap files FIU account * Use Wireshark to analyze data

Results

See Q.A for results

Q.A.

What virtual system did you use (cgs4285-XX.cs.fiu.edu) Let me know the XX.

cgs4285-a.cs.fiu.edu

During ping1 what was the Ethernet destination for the ICMP echo request on network 10.100.1.0/24? What was the IP address of this Ethernet interface? Was the IP address of the interface with that Ethernet address the same as the IP destination address in the IP datagram itself? 


Destination - 52:54:00:E4:3A:BD
Destination - 10.100.1.254
Yes the IP