Network Devices Explained: A List of Each One and What It Does

Ask ten people to list network devices and you get ten different lists, because the category mixes layers, sizes, and eras. A home gateway does the work of a modem, router, switch, firewall, and wireless access point, while a data center separates all of those into distinct products that are documented for good reason.

This list groups the devices by the job they do, explains what each one is responsible for, and notes where the boundaries blur in practice. It is meant to be read as a map, not a spec sheet.

Devices That Connect Hosts

These devices exist to give endpoints a place to plug in and a way to reach each other on a local segment.

The switch is the workhorse. Early networks used hubs, which shared one collision domain and got congested fast, and the switch replaced them by giving each port its own segment and by learning which MAC address lives behind which port. A managed switch adds VLANs, spanning tree, link aggregation, and monitoring that surface through SNMP.

Devices That Connect Networks

These devices move traffic between networks, which means they work with IP addresses rather than MAC addresses.

The line between a router and a firewall has blurred, and so has the line between a router and a Layer 3 switch. The useful question is not what a device is called but what function it performs on your network: does it route, does it enforce policy, does it translate addresses, and does it terminate connections on behalf of others.

Devices That Reach the Outside World

Every network needs a path to the provider, and the device at that boundary goes by different names depending on the medium.

This is the side of the network where the carrier’s responsibility usually ends. Knowing where the demarcation point sits, and what the carrier owns versus what you own, is what turns a circuit outage into a one call fix instead of an argument.

Devices You Might Not Think Of

Some devices matter because they are the ones that cause the most confusion when they are missing from the records. A PoE injector adds power inline for one device. A KVM or console server gives out of band access when the network is down. A terminal server connects the console ports of many devices so they can be reached during an outage. A time server or NTP source keeps logs comparable across devices. A TFTP server delivers firmware and configurations. None of these route traffic, and every one of them can be the difference between a five minute fix and a site visit.

Why the Records Matter More Than the List

The device list itself is easy. What is hard is knowing which device is in which rack, which port connects to what, which address belongs to it, and who owns it. That is where a list stops being a checklist and becomes infrastructure documentation.

Recording every device, its interfaces, and its address against a site and a rack, as device inventory and IP address management in Obelinf do, keeps the map current enough to be useful. The network topology view then renders the same records as a diagram, so the list and the picture never drift apart.