PC1 wants to send a file to PC2
Both PC1 and PC2 are connected to the same switch. Both PCs are in same vlan.
Here is the process as I understand.
1. PC1 determines that PC2 is on same network.
2. PC1 sends arp for Mac Address of PC2.
3. Switch builds MAC Address table and adds PC1's Mac Address.
4. PC2 responds to the Arp Address with its MAc Address.
5. Switch builds MAC Address table and adds PC2's Mac Address.
6. PC1 now builds the FRAME with the destination MAC that it received from the arp request.
7. PC1 sends a unicast frame to PC2
Does PC1 send a frame with the packet encapsulated? meaning does it still contain IP Source and Destination?
Or is it a Frame with just the Data minus the IP Source and Dest?
I'm guessing that once it travels down the OSI model, it receives the IP info before the frame MAC's so it must keep it.
A minor change somewhere around #10:
When a layer 3 device receives a frame, it strips the frame (discards it) and passes the contents (the packet, complete with L3 addressing) up the stack.
Then the L3 destination (the "network address") is determined, the routing/forwarding decision is made and the packet is passed down the stack to the L2 process for re-encapsulation, the new frame will have a new SOURCE MAC address (the L3 device's egress interface) and a new DESTINATION MAC address (PC2 in this case).
In this case, PC2 is directly attached, so the L3 device must also ARP (if necessary) for the L3 host address/MAC. IF there was another intermediate hop, the L3 device doesn't even look at the host portion of the L3 address.
The L3 device won't mess with the L3 address, but it will do things like decrement the TTL, possibly change the QOS mapping ... mostly just flags.
Other than that, you have a pretty good handle on it.