Do the source and destination addresses of the ping packets make sense?.Can you identify ping requests from server1?.Does it match the opcode for ARP as listed in Network Sorcery? (See ) Expand a specific ARP packet in the packet analysis pane and look for the hex Ethertype field.Look at the packets captured, and perform the following exercises: Generate some packets by pinging from Server1 to Server2 via your hub (and not another group's hub). Open 1 copy of Wireshark on your Netfpga machine and start listening on the private interface that connects to your hubīy default, Wireshark captures all packets it sees on the interface.Load your hub bitfile on your Netfpga machine.(For reference, similar steps were done in the Hardware Tutorial): Perform the following initial setup steps. The interface is relatively self explanatory, but feel free to ask questions.įor the second exercise, we will analyze packets captured from your Ethernet hub.

To answer these questions, you will need to explore wireshark's interface for displaying the values of the various packet header fields. Do all your printed fields match what Wireshark shows for the same packet?.exports/home/ / /logfile.dat, and click Open.Ĭompare the Wireshark packet analysis with the packet decoding that you implemented during the tutorial. Enter the path to your new data file, e.g. Go to File->Open, and click on the Notepad icon in the upper-left corner. Now open Wireshark (you don't need to use op because we're not capturing data from an interface, and thus don't need root access). Wait for a few packets to be received by your VNS toplogy, and then exit the program. This file is in the tcpdump/wireshark format and can be opened by either utility. The new -l flag will log all VNS packets received to the file logfile.dat. Remember to specify the VNS ID assigned to your group. Locate your VNS project from the first tutorial, and run the program again.

In this first exercise, we will analyze packets captured from VNS.

Wireshark captures for ping