Ethernet

Preamble: A sequence of alternating bits ($101010...$) that allows the receiving device to synchronize its clock with the incoming bitstream.

MAC Addresses: The frame includes both the destination and source MAC addresses ($48$ bits each) to ensure the data reaches the correct hardware interface.

EtherType / Length: This field indicates either the protocol of the encapsulated data (e.g., IPv4) or the total length of the payload.

Payload: The actual data being transported, which must typically be between $46$ and $1500$ bytes in size.

FCS (Frame Check Sequence): A mathematical checksum (CRC) used by the receiver to verify that the data was not corrupted during transmission.

Sequence of Events: Always be prepared to describe the CSMA/CD process in order: Listen $\rightarrow$ Transmit $\rightarrow$ Detect Collision $\rightarrow$ Jamming Signal $\rightarrow$ Random Wait $\rightarrow$ Retry.

MAC vs. IP: Remember that Ethernet operates using MAC addresses; IP addresses are part of the payload and are handled by the Network Layer, not the Ethernet protocol itself.

Error Detection: If a question asks how Ethernet ensures data integrity, focus on the FCS field and the use of Cyclic Redundancy Checks (CRC).

Collision Logic: Understand that collisions are a natural part of shared-media Ethernet; the protocol is designed to manage them, not necessarily prevent them entirely in older bus topologies.

Misconception: Students often think a collision means the data is lost forever. In reality, Ethernet is designed to retransmit the data automatically after a random delay.

The 'Random' Wait: A common mistake is forgetting why the wait time must be random; if two devices waited the exact same amount of time, they would collide again immediately upon retrying.

Hardware vs. Software: Ethernet is often confused with the Internet. Ethernet is the local 'plumbing' (hardware/link layer), while the Internet is the global network of networks (network layer).