---
{
  "title": "Network devices",
  "summary": "Identify forwarding, wireless, translation, and security functions by configuration, then protect the infrastructure’s management and maintenance paths.",
  "topic": "networking",
  "level": "Beginner",
  "updated": "2026-10-12",
  "units": [
    1
  ],
  "aliases": [],
  "sources": [
    {
      "title": "Cisco: Networking basics",
      "url": "https://www.cisco.com/site/us/en/learn/topics/networking/what-is-computer-networking.html"
    }
  ],
  "published": "2026-10-02",
  "editorialVersion": 2
}
---
## The idea

Network infrastructure includes interfaces, access points, switches, routers, firewalls, modems, and other components. Hubs and repeaters have different forwarding behavior from switches. Modern devices may combine several functions, so names alone are insufficient. Examine configured forwarding, management, power, and security capabilities. Management access and supported maintenance are important regardless of the physical form of the device.

## In practice

A home gateway combines routing, wireless access, translation, and firewall functions, while an enterprise switch may also route between VLANs.

## A common misunderstanding

A “switch” is not necessarily limited to layer two, and a “router” does not automatically enforce the policy you need.

## Check your understanding

How should you evaluate a device’s role?

**Think it through:** From its actual configuration, supported behavior, placement, and management controls.

## One box can perform several jobs

Imagine a fictional academy replaces a home-style gateway with separate access points, switches, a router, and a firewall. The old gateway may have performed all of those functions in one enclosure. Comparing only product names would miss the actual change in responsibilities.

Start by listing behaviors: how clients connect, how frames move locally, how packets move between networks, where addresses are translated, and where traffic is restricted. A device can support a feature without that feature being enabled or correctly configured.

## Separate forwarding from administration

The path used by learner traffic differs from the path administrators use to configure equipment. Management interfaces can expose powerful operations, credentials, and diagnostic information. They need appropriate identity controls, restricted reachability, and records of significant changes.

Suppose a classroom switch forwards learner traffic correctly but lets any learner reach its administration page. The network is functional while an important control boundary is missing. Operational success does not establish secure administration.

## Maintenance affects the whole environment

A device inventory should include its role, owner, supported software, configuration backup, and recovery approach. Equipment that cannot receive appropriate maintenance can become a lasting risk even if its current forwarding behavior seems normal.

Replacing or updating infrastructure can also interrupt many services at once. Understand dependencies and recovery steps before changing a device on a shared path. A configuration backup is useful only if the team knows how to restore it on an available replacement.

For an exercise, draw a learner-to-application journey and annotate every device function it crosses. Then add the separate administrator journey to one device. Explain which credentials and network restrictions protect that management access. Finally, describe what happens if the device fails and who can recover it. This combines connectivity, control, and maintainability rather than treating infrastructure as anonymous icons.

## Keep exploring

- [[routing-and-switching]]
- [[wireless-security]]
- [[network-management]]