A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
New PC plugged into office switch can't reach anyone. Link light is green. You check: PC has no IP, but switch already saw its MAC. Link works, IP missing. Frame vs packet matters — MAC got there, IP didn't. That's this lesson.
Think of an Ethernet frame as an office envelope. Outside: TO (destination MAC), FROM (source MAC), TYPE (what's inside: IPv4? IPv6?). Inside: your data. Back flap: checksum (FCS) so receiver knows envelope wasn't damaged. Switches only read the outside. They never open the letter.
| Part | Size | Job |
|---|---|---|
| Destination MAC | 6 bytes | Who should read it |
| Source MAC | 6 bytes | Who sent it, so switch can learn |
| Type | 2 bytes | 0x0800 = IPv4, 0x86DD = IPv6 inside |
| Data | 46-1500 bytes | Your packet (IP + TCP + app) |
| FCS | 4 bytes | Checksum, drop if damaged |
Max data 1500 bytes = MTU you will hear forever. Preamble/SFD before the frame are just clock sync, not counted. Tagged VLAN frames add 4 bytes — full detail in Module 6, just know tagged is slightly bigger.
link/ether is your MAC, 48 bits as 6 hex pairs. brd ff:ff:ff:ff:ff:ff is broadcast — 'everyone on my LAN'. First half of a real NIC is vendor OUI, second half unique. Addresses starting 02:... like above are locally assigned (VMs/containers) — normal in labs.
Deferred for later: 1522-byte tagged math, 802.1Q details (Module 6), STP BPDU MAC 01:80:C2... (Module 7), HSRP virtual MACs (Module 14). You don't need them to understand forwarding.
Know envelope parts, read your MAC, and unicast vs broadcast cold. Next: how the switch remembers every MAC it sees.
Optional: capture in Wireshark, filter eth.dst == ff:ff:ff:ff:ff:ff to see ARP broadcasts live. One capture teaches more than diagrams.
Finish the lesson once you have worked through the material. This awards ★ 40 XP.
Select each vulnerable line, then classify the finding.
Findings
Review target: 3 lines · 1 expected finding