Skip to content
Computer Science · Class 12

Active learning ideas

TCP/IP Model: Network Access and Internet Layers

Students often find abstract networking ideas hard to grasp without hands-on work. Active learning lets them see how data moves physically and logically through layers, making the TCP/IP model real rather than just theoretical. Stations, role plays, and tool-based activities turn packet framing, addressing, and routing from confusing terms into clear, memorable steps.

CBSE Learning OutcomesCBSE: Computer Networks - Network Protocols - Class 12
30–50 minPairs → Whole Class4 activities

Activity 01

Simulation Game45 min · Small Groups

Simulation Game: Packet Encapsulation Stations

Prepare stations for Network Access (add MAC headers to paper packets) and Internet layer (assign IP addresses and route via mock tables). Groups assemble, route, and disassemble packets, noting changes at each layer. Conclude with class share-out of challenges faced.

Explain the primary responsibilities of the Network Access layer in TCP/IP.

Facilitation TipBefore running the simulation, distribute printed frame headers so students can physically arrange fields and see encapsulation in action.

What to look forPresent students with a scenario: 'A computer on your home Wi-Fi network needs to send data to a server in another country.' Ask them to identify which layer handles the physical transmission (Network Access) and which layer handles the global addressing and path selection (Internet). Then, ask them to state whether an IP address or MAC address is primarily used for each task.

ApplyAnalyzeEvaluateCreateSocial AwarenessDecision-Making
Generate Complete Lesson

Activity 02

Jigsaw30 min · Pairs

Hunt: MAC vs IP Address Discovery

Students use command prompts on school computers to find their device's MAC and IP addresses. In pairs, they compare across devices, discuss why MAC stays fixed while IP changes, and map to TCP/IP layers. Record findings in a shared class table.

Differentiate between IP addresses and MAC addresses.

Facilitation TipUse coloured sticky notes for MAC and IP addresses during the hunt so students visually separate the two address spaces.

What to look forPose the question: 'Why is it necessary to have both IP addresses and MAC addresses?' Facilitate a discussion where students explain the scope of each address type and how they work together for end-to-end communication. Prompt them to consider what would happen if only one type of address existed.

UnderstandAnalyzeEvaluateRelationship SkillsSelf-Management
Generate Complete Lesson

Activity 03

Jigsaw40 min · Small Groups

Role-Play: Dynamic Routing Game

Assign students roles as routers with printed routing tables. 'Packets' (cards) travel based on destination IP; update tables for link failures. Groups debrief on hop-by-hop decisions and convergence.

Analyze how data packets are routed across different networks at the Internet layer.

Facilitation TipIn the role-play, assign students to small autonomous systems and give each a simplified routing table to keep the simulation manageable.

What to look forAsk students to write down two key differences between IP addresses and MAC addresses on a slip of paper. Additionally, have them briefly describe the main role of a router in the context of the Internet layer.

UnderstandAnalyzeEvaluateRelationship SkillsSelf-Management
Generate Complete Lesson

Activity 04

Jigsaw50 min · Pairs

Capture: Wireshark Layer Analysis

Capture local pings with Wireshark, filter for Ethernet and IP frames. Individually annotate screenshots showing MAC/IP headers and routing info. Pairs present one anomaly found.

Explain the primary responsibilities of the Network Access layer in TCP/IP.

Facilitation TipIn Wireshark, freeze the capture window after each filter so students can annotate packets step-by-step without losing context.

What to look forPresent students with a scenario: 'A computer on your home Wi-Fi network needs to send data to a server in another country.' Ask them to identify which layer handles the physical transmission (Network Access) and which layer handles the global addressing and path selection (Internet). Then, ask them to state whether an IP address or MAC address is primarily used for each task.

UnderstandAnalyzeEvaluateRelationship SkillsSelf-Management
Generate Complete Lesson

A few notes on teaching this unit

Start with the physical aspects—cables, signals, frames—so students feel the Network Access layer first. Then move upward to the logical world of IP addresses and routing, linking each concept to real devices in the lab. Avoid rushing into protocol names; anchor understanding in the problem each layer solves. Research shows that building mental models through layered simulations and peer explanations solidifies comprehension more than lectures alone.

By the end of these activities, students should confidently explain how the Network Access layer builds frames with MAC addresses and how the Internet layer uses IP addresses to route packets across networks. They will also articulate why both types of addresses are necessary and show how routing decisions happen dynamically.


Watch Out for These Misconceptions

  • During the Packet Encapsulation Stations activity, watch for students who treat the Network Access layer as only cables and wires.

    Have them complete the frame construction station where they add source and destination MAC addresses, checksums, and error detection fields. Point out that this layer also handles framing and reliability, not just physical transmission.

  • During the MAC vs IP Address Discovery hunt, watch for students who believe IP addresses are permanently tied to hardware like MAC addresses.

    During the hunt, pair students to compare a live DHCP lease table with interface MAC addresses. Ask them to note how IP addresses change while MAC addresses remain fixed, reinforcing the logical versus physical nature of each.

  • During the Dynamic Routing Game role-play, watch for students who assume packets always take the shortest path.

    After each hop, have them update their routing tables based on simulated link failures. Ask them to explain why the new path was chosen instead of the shortest one, linking this to real-world routing protocols.


Methods used in this brief