Free Example 1 • Daily Lesson
IPv4 Configuration: The workstation has an address—but is it a usable address?
A classroom-ready 45–55 minute lesson showing the level of daily planning included across the year.
Learning target
Students will inspect IPv4 configuration evidence and identify which value should be investigated before changing anything.
A missed question can expose a vocabulary gap, an unsupported inference or a repair chosen too soon. Add the free Wrong Answer Detective to classroom review to make the reason behind each mistake visible.
Student evidence
Workstation: LAB-PC-07
IPv4: 10.20.8.44
Mask: 255.255.255.0
Gateway: 10.20.9.1
DNS: 10.20.8.53
Ping 10.20.8.22 → Reply
Ping 10.20.9.1 → Destination unreachable
45–55 minute teaching sequence
5 min — Bell ringer: Which values describe this host, and which value tells it where to send remote traffic?
10 min — Teach: Separate the jobs of address, mask/prefix, gateway, and DNS.
8 min — Worked example: Model how local success narrows the problem without proving the entire configuration is correct.
20 min — Student work: Teams diagnose six fictional workstation cards containing different configuration conditions.
5 min — Debrief: Compare two cases that produce similar symptoms for different reasons.
2 min — Exit ticket: What should you investigate when local communication works but remote communication fails?
Teacher guidance: Students often see a normal-looking IPv4 address and assume the host is configured correctly. Listen for students who use the successful local ping as evidence that the local interface and same-subnet communication are functioning, then identify the gateway as the next configuration value worth testing. Do not reward “restart everything” as an evidence-based first action.