Study guide

16.2 Network Hardware and Layered Network Models (OSI and TCP/IP)

Praxis Computer Science 5652

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Praxis 5652 Exam Overview and ETS Pseudocode

1.1 Praxis 5652 Test Facts, Scoring, and Registration 1.2 Official ETS Pseudocode Notation and Tracing Strategy

2 Chapter 2: Impacts of Computing: Innovation, Access, and Effects

2.1 Computing for Creativity, Problem Solving, Communication, and Innovation 2.2 Equal Access, the Digital Divide, and Accessibility 2.3 Beneficial and Harmful Effects of Computing Innovations

3 Chapter 3: Impacts of Computing: Intellectual Property, Ethics, Privacy, and Security

3.1 Intellectual Property: Copyright, Open Source, and Creative Commons 3.2 Ethical and Unethical Computing Practices and Their Implications 3.3 Privacy, Security, Data Collection, and Local vs. Cloud Storage

4 Chapter 4: Algorithms and Computational Thinking: Abstraction, Decomposition, Number Bases, and Representation

4.1 Abstraction and Abstraction Hierarchies 4.2 Decomposition, Pattern Recognition, and Developing Algorithms 4.3 Number Bases: Binary, Octal, Decimal, and Hexadecimal 4.4 Algorithm Formats: Natural Language, Flowcharts, Pseudocode, and Tracing

5 Chapter 5: Algorithms: Efficiency, Limits of Computing, and Randomization

5.1 Algorithm Efficiency: Linear, Quadratic, Exponential, and Logarithmic Growth 5.2 Limits of Computing: Unsolvable Problems, Intractability, and Heuristics 5.3 Randomization, Random vs. Pseudorandom Numbers, and Scaling to a Range

6 Chapter 6: Algorithms: Searching, Sorting, and Recursion

6.1 Searching Algorithms: Linear Search and Binary Search 6.2 Sorting Algorithms: Tracing, Comparisons, Correctness, and Efficiency 6.3 Recursion: Base Cases, Tracing, Errors, and Iterative Equivalents

7 Chapter 7: Programming: Variables, Data Types, Strings, and Expressions

7.1 Variables, Data Types, and Type Conversion 7.2 Strings and String Operations 7.3 Operators, Precedence, Expressions, and Formulas 7.4 Boolean Expressions, Truth Tables, and Boolean Algebra

8 Chapter 8: Programming: Selection, Iteration, and Writing Code

8.1 Sequence and Selection: if, else, Chained and Nested Conditions 8.2 Iteration: for, while, do … while, and repeat … until Loops 8.3 Reading, Completing, and Modifying Code

9 Chapter 9: Programming: Procedures, Arrays, and Data Structures

9.1 Procedures, Parameters, Return Values, Nested Calls, and Scope 9.2 Arrays, Lists, and Two-Dimensional Arrays 9.3 Stacks, Queues, and Dictionaries (Maps)

10 Chapter 10: Programming: Correctness, Errors, Testing, and Code Quality

10.1 Program Correctness: Preconditions, Postconditions, Invariants, and Testing vs. Proof 10.2 Error Types and Debugging Techniques 10.3 Choosing Useful Test Cases: Boundaries, Partitions, Coverage, and Regression 10.4 Extensibility, Modifiability, and Reusability: Constants and Parameterization 10.5 Documentation, Code Reviews, Peer Feedback, and End-User Feedback

11 Chapter 11: Programming: Events, Usability, Input Validation, and APIs

11.1 Event-Driven Programming, Asynchronous Events, and Concurrency 11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification 11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs

12 Chapter 12: Programming: Languages, Tools, Paradigms, and Object-Oriented Design

12.1 Low- and High-Level Languages, Compilers and Interpreters, and IDEs 12.2 Programming Paradigms: Procedural, Object-Oriented, and Others 12.3 Classes, Objects, Instance Variables, Methods, and Encapsulation 12.4 Inheritance, Polymorphism, and Overloading vs. Overriding

13 Chapter 13: Data: Bits, Encoding, Compression, and Encryption

13.1 Bits and Bytes: Why Binary, Storage Calculations, and Signed Integers 13.2 Encoding Text, Images, and Sound 13.3 Lossless and Lossy Compression: Run-Length Encoding, Huffman Coding, and Media Formats 13.4 Encoding vs. Encryption, Symmetric and Public-Key Encryption, and Their Trade-offs

14 Chapter 14: Data: Analysis Tools, Simulation, Storage, and Collection

14.1 Analyzing Data with Spreadsheets: Cleaning, Transforming, and Visualizing 14.2 Simulation and Modeling 14.3 Files, Databases, and Storage Requirements: Scale, Redundancy, and Backup 14.4 Collecting, Aggregating, and Generating Data: Public Data Sets, Surveys, Sensors, and Crowdsourcing

15 Chapter 15: Computing Systems: Hardware, Operating Systems, and Computing Environments

15.1 Hardware Components and the Fetch–Decode–Execute Cycle 15.2 Operating Systems, Software Components, and Resource Issues 15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems 15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored

16 Chapter 16: Networks, the Internet, the Web, and Cybersecurity

16.1 Network Types and Wired and Wireless Communication 16.2 Network Hardware and Layered Network Models (OSI and TCP/IP) 16.3 Network Performance: Bandwidth, Latency, Load, and Estimating Needs 16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability 16.5 The Web: HTTP, HTML and Markup Languages, Browsers, Servers, and Clients 16.6 Cybersecurity: The Five Pillars, Strong Passwords, Security Strategies, and Trade-offs

16.2 Network Hardware and Layered Network Models (OSI and TCP/IP)

Key Takeaways Explain This Topic AI

A switch connects devices within a LAN and sends each frame only to the port of its destination MAC address; a hub, now obsolete, repeats every signal to all ports.

A router connects different networks and forwards packets toward their destination IP address using a routing table; a home router usually also provides Wi-Fi, NAT, and a firewall.

A modem converts between the digital signals of a home network and the signaling used on the provider's cable, DSL, or fiber line.

The TCP/IP model has four layers (application, transport, internet, link); the OSI model has seven (application, presentation, session, transport, network, data link, physical).

Sending data moves down the layers, each adding its own header (encapsulation): a message becomes a TCP segment, then an IP packet, then an Ethernet frame, then bits.

Last updated: September 2026

What this competency asks

ETS asks you to know components of networks :

Identify network hardware devices and their functions.

Describe possible abstraction models of networks.

Network hardware devices

Device Function Uses addresses at

Network interface card (NIC) Connects a device to a network (wired or wireless); has a MAC address Link (hardware)

Hub (obsolete) Repeats every incoming signal out of all ports; all devices share bandwidth and collisions None; it just repeats signals

Switch Connects devices within a LAN ; learns which MAC address is on which port and forwards frames only where they need to go MAC addresses

Wireless access point (WAP) Connects Wi-Fi devices to the wired LAN MAC addresses

Router Connects different networks (for example, a school LAN to the Internet) and forwards packets toward their destination using routing tables IP addresses

Modem Mo dulates and dem odulates: converts between the network's digital signals and the provider's line signaling (cable, DSL, fiber terminal) —

  • Firewall Filters traffic according to security rules (Section 16.6) IP addresses, ports, and sometimes content
  • Repeater / range extender Regenerates a signal to extend its distance —

A typical home router combines a router, a switch, a Wi-Fi access point, and a firewall, and it performs network address translation (NAT) so many devices share one public IP address (Section 16.4).

MAC vs. IP addresses: a MAC address (48 bits, written in hex, such as 00:1A:2B:3C:4D:5E ) identifies a network interface on the local link. An IP address identifies a device's location on the internetwork and is used to route across networks. Your laptop keeps its MAC address everywhere, but it receives a different IP address on each network it joins.

Why layered models?

Networking is complicated, so it is divided into layers . Each layer provides services to the layer above it and uses the services of the layer below. This is abstraction (Section 4.1). A web browser does not care whether data travel over Wi-Fi or fiber, and Wi-Fi does not care whether it is carrying a video or an email. Layers can be improved independently: moving from copper to fiber required no change to HTTP.

The TCP/IP model (four layers)

  • Layer Job Examples
  • Application Network services for programs HTTP, HTTPS, DNS, SMTP, FTP
  • Transport End-to-end delivery between programs, using port numbers; reliability (TCP) or speed (UDP) TCP, UDP
  • Internet Addressing and routing packets across networks IP (IPv4, IPv6)
  • Link (network access) Moving frames across one physical network Ethernet, Wi-Fi
  • The OSI model (seven layers)
  • # Layer Role Corresponds to TCP/IP
  • 7 Application Services used by applications Application
  • 6 Presentation Data formats, encryption, compression Application
  • 5 Session Managing sessions between applications Application
  • 4 Transport End-to-end reliability, ports, segmentation Transport
  • 3 Network Logical addressing and routing (routers) Internet
  • 2 Data link Frames, MAC addresses (switches) Link
  • 1 Physical Bits as signals on cable or radio Link

The OSI model is a teaching and reference model. TCP/IP is what the Internet actually runs.

Where each device works

  • Device OSI layer TCP/IP layer
  • Hub, repeater, cable 1 Physical Link
  • Switch, wireless access point, NIC 2 Data link Link
  • Router 3 Network Internet
  • Firewall 3 and 4; some also inspect application data Internet and transport, sometimes application

A common mnemonic lists the OSI layers from 1 up to 7: P lease D o N ot T hrow S ausage P izza A way (physical, data link, network, transport, session, presentation, application).

Using the layers to troubleshoot

Technicians work up the layers, because a failure at a lower layer breaks everything above it.

  • Symptom Likely layer What to check
  • No link light, or Wi-Fi shows no connection Physical and link Cable, port, wireless radio, access point

Connected, but the computer has only a self-assigned 169.254.x.x address Internet (addressing) The DHCP server that hands out IP addresses

  • Sites load by numeric IP address but not by name Application (DNS) DNS server settings (Section 16.4)
  • One website fails while others work Application or the remote server The site itself, not the local network
  • Encapsulation

When data are sent, each layer adds its own header (and the link layer adds a trailer): Application: [ message, e.g. an HTTP request ]

  • Transport: [ TCP header | message ] → segment
  • Internet: [ IP header | TCP header | message ] → packet
  • Link: [ Ethernet header | IP packet | FCS trailer ] → frame
  • Physical: 1 0 1 1 0 0 1 … → bits

The TCP header holds source and destination ports , sequence numbers for reordering, and acknowledgment information.

The IP header holds source and destination IP addresses and a time-to-live counter that stops packets from circling forever.

The Ethernet frame holds MAC addresses in its header and a frame check sequence (CRC) in its trailer for detecting transmission errors.

At the receiver, each layer removes its own header ( decapsulation ) and passes the rest up.

Following one request through the devices

A student's laptop on school Wi-Fi requests a web page from a server on another network:

The laptop sees that the server is not on its local network, so its NIC sends the packet in a Wi-Fi frame addressed to the MAC address of the default gateway , the school's router. In IPv4, the Address Resolution Protocol (ARP) finds the MAC address that goes with the router's IP address.

The access point passes the frame onto the wired LAN, and the switch forwards it only out of the router's port.

The router removes the frame, reads the destination IP address, checks its routing table, and decrements the time-to-live. At the school's edge, the router (or a firewall beside it) also applies security rules and uses NAT to replace the laptop's private source address with the school's public address. Then the packet goes into a new frame for the next link.

The school's connection carries the packet to its Internet provider. Every router along the path repeats the forwarding part of step 3: it reads the destination IP address, decrements the time-to-live, and sends the packet on inside a new frame, with the IP addresses unchanged.

The server's NIC accepts the final frame, and each layer removes its header until the request reaches the web server program.

The rule to remember: MAC addresses change at every hop, while the source and destination IP addresses stay the same from end to end , except where NAT rewrites a private address at the network's edge. A basic switch forwards by MAC address only. A router forwards by IP address.

Packet switching

The Internet uses packet switching . Data are split into packets that travel independently, possibly by different routes, and are reassembled at the destination. Links are shared efficiently, and traffic can route around failures. The traditional telephone network used circuit switching , which reserves a dedicated path for the whole call. That path is steady, but capacity is wasted during silences, and the call drops if the path breaks.