Endpoints & Network Adapters
Hosts, NICs, MAC addresses, interface states, speed/duplex and the endpoint side of a packet path.
Open PlaybookA component-first learning module for L2 and L3 engineers. Learn what each network component does, where it sits in the architecture, what state it maintains, how it forwards traffic and how to troubleshoot it in production.
Do not learn network devices as isolated product names. Learn their responsibility, state, interfaces and place in the packet journey. Open a playbook whenever you need a focused revision before moving forward.
Hosts, NICs, MAC addresses, interface states, speed/duplex and the endpoint side of a packet path.
Open PlaybookCopper, fiber, optics, SFP/SFP+, media types, distance, polarity and physical-layer failure symptoms.
Open PlaybookUnderstand why hubs repeat bits while switches learn MAC addresses and make forwarding decisions.
Open PlaybookAccess ports, trunks, CAM tables, VLANs, STP, EtherChannel and the switching data plane.
Open PlaybookSVIs, routed ports, hardware forwarding and where campus switching becomes routing.
Open PlaybookInterfaces, routing tables, next hops, control plane vs data plane and inter-network forwarding.
Open PlaybookStateful inspection, zones, security policy, NAT and how firewall decisions affect packet flow.
Open PlaybookSSID, radio, channel, client association, VLAN mapping and the wired path behind an AP.
Open PlaybookCentralized policy, AP management, roaming, tunnels and enterprise WLAN architecture.
Open PlaybookVirtual services, health checks, VIPs, persistence and the difference between network and application forwarding.
Open PlaybookONT/modem, edge router, provider handoff, BGP and the operational boundary between enterprise and carrier.
Open PlaybookIDS/IPS, visibility points, telemetry and how security controls become part of the packet path.
Open PlaybookIdentify the component, interface type, operating layer and primary responsibility.
Place it correctly in the topology and identify its neighboring devices.
Determine whether it uses MAC, VLAN, ARP, routing, session or policy state.
Explain the decision that moves traffic to the next interface or hop.
Predict the observable symptoms before touching the configuration.
Choose counters, status commands, logs or packet captures that provide evidence.
Each exercise connects component knowledge to evidence collection and packet-flow reasoning.
Given an enterprise topology, identify every component a packet crosses from endpoint to application.
Determine whether a forwarding problem belongs to VLAN/MAC logic or IP/routing logic.
Start with a link-down symptom and isolate cable, optic, interface, VLAN and gateway causes.
Trace a permitted and denied flow through zones, NAT and security policy.
Explain the path from campus access through distribution, edge routing, provider handoff and Internet.