LAB 3‐2 ‐ Exploring Broadcast Domains - rune-seregina/net-150-sp24 GitHub Wiki
In this lab, I explored the different routes that a ICMP packet would take depending on the network in which it is travelling (local or not). This helped build on my understanding of ARP and routing.
WireShark packets can be explored by layer from top to bottom!

Answer: What is the source MAC address? What is the destination MAC address? (Hint: Data Link Layer Header)
Source MAC address: d0:81:c5:23:bd:80 (default gateway)
Destination MAC address: 48:21:0b:33:5e:44 (my workstation)
Answer: Does the source MAC address look familiar from prior labs? Do you think it is the Google Server's MAC address?
It looks familiar because it is the default gateway's MAC address for the current network, it is not Google Server's MAC address.

Source MAC address: 48:21:0b:33:5e:4a (partner's work station) Destination MAC address: 48:21:0b:33:5e:44 (my workstation)
48:21:0b:33:5e:44
Deliverable 3: Does the MAC address match the address from your traffic capture in Deliverable 1? If not - what do you think happened?
No, the MAC address is different. Since the ping request was coming from inside the network, it did not need to go through the default gateway and instead went right to the intended workstation.
The ping request from my partner's workstation to my workstation had the source MAC address of 4a (their address) and a destination MAC address of 44 (my address).
The ping request from my workstation to my partner's workstation had the source MAC address of 44 (my address) and a destination address of 4a (their address).
While the workstations doing the communicating are the same, the communication is traveling in different directions depending on who sent the request and who is replying to the request.