What Is a Computer Network? Connected Devices Plus Shared Rules

Two devices do not form a useful network merely because a cable joins them or both can transmit radio waves. They also need agreed rules for identifying one another, packaging information, sharing the link, detecting problems, and interpreting what arrives.

A computer network is a group of connected devices that exchange data using shared communication rules called protocols.

A network can contain two nearby machines, thousands of office devices, or many independent networks joined across the planet.

Why networks exist

Networks let devices share:

Messages and files
Internet access
Printers and storage
Applications and databases
Audio and video
Sensors and control signals
Computing capacity

Without a network, moving information might require physically carrying storage between devices.

Networks make communication fast and automatic, but introduce questions about addressing, congestion, reliability, compatibility, and security.

Nodes and links

A connected device is often called a node or host. Examples include:

Laptop
Phone
Server
Printer
Camera
Smart television
Router
Sensor

A link carries signals between nodes.

Links can use:

Copper cable
Fiber-optic cable
Wi-Fi radio
Cellular radio
Satellite radio

The medium carries physical signals. Networking protocols decide what those signals mean.

Data needs packaging

Imagine two people speaking continuously over one shared radio channel with no pauses, names, or message boundaries. The listener would struggle to determine who is speaking and where one message ends.

Networks divide communication into structured units. Depending on the layer, these units may be called frames, packets, segments, or messages.

They include control information such as:

Source and destination
Length or boundaries
Protocol type
Ordering information
Error-detection values

The useful content is commonly called the payload.

Protocols are agreements

A protocol defines rules for communication.

It may specify:

Message layout
Valid values
Who may send and when
How devices identify one another
How errors are detected
Whether missing data is retried
How a conversation begins and ends

Ethernet, Wi-Fi, IP, TCP, DNS, and HTTP are examples operating at different layers.

Devices can be built by different manufacturers and still communicate because they implement shared standards.

Network interfaces

A device connects through a network interface.

It may have several:

Ethernet
Wi-Fi
Cellular
Virtual private network
Loopback interface for internal communication

Each interface has hardware or software state and may have its own addresses.

When a laptop switches from home Wi-Fi to a phone hotspot, it joins a different network through a different connection. Its internet-facing addressing and route may change even though it remains the same physical laptop.

Switches connect devices locally

An Ethernet switch joins devices within a local network.

It learns which device addresses are reachable through which physical ports and forwards local frames accordingly.

Instead of sending every frame to every device, the switch usually directs it toward the appropriate port. Broadcast and unknown traffic may still reach multiple ports.

A home router often contains a small Ethernet switch internally, which is why several LAN sockets are available on one box.

Routers connect networks

A router moves packets between different IP networks.

Your home router commonly connects:

The private home network
The internet provider's network

It examines destination IP information and chooses a next route.

Switching and routing solve related but different scopes:

A switch primarily connects devices within a local network.
A router connects separate networks.

Real enterprise devices can perform both roles.

Clients and servers

Networked software often follows a client-server pattern.

A client initiates a request. A server listens for requests and provides a service.

When visiting a website:

The browser acts as a client.
It connects to a web server.
It requests a resource.
The server sends a response.

The same machine can be a client in one conversation and a server in another.

Peer-to-peer systems distribute responsibilities more evenly, allowing participants to serve one another directly.

A concrete example: printing over a home network

Suppose a laptop prints to a Wi-Fi printer:

Both devices join the same local network.
The laptop discovers or knows the printer's address.
Printing software creates a print job.
Network protocols divide it into transferable data.
Wi-Fi or Ethernet carries frames through the access point or switch.
The printer receives and reconstructs the job.
It interprets page commands and prints.

The internet provider does not need to participate. The home network can continue supporting local printing even if the internet connection is down.

This proves that Wi-Fi, a local network, and the internet are not the same thing.

Layered communication

Networks are easier to design when responsibilities are separated.

A simplified stack is:

Application: web, email, chat
Transport: application-to-application delivery
Internet: routing across networks
Link: delivery across one local link
Physical: electrical, optical, or radio signal

Each layer uses the layer below and offers a service to the layer above.

When sending a web request, HTTP data is wrapped in transport information, then IP information, then local-link information. The receiver unwraps these layers.

Layering lets Wi-Fi replace Ethernet without redesigning HTTP.

Reliability can live at different layers

Not every network link or protocol guarantees delivery.

A layer may:

Detect damaged data
Retry locally
Number messages
Request retransmission
Ignore loss

Wi-Fi can retry a damaged local frame. TCP can recover missing transport data end to end. An application may add its own confirmation.

Multiple reliability mechanisms are not necessarily redundant because they cover different scopes and timing.

Network security

Connecting devices creates paths that attackers or defective software may misuse.

Security measures include:

Authentication
Encryption
Firewalls
Network segmentation
Software updates
Least-privilege services
Monitoring

A private local address is not a complete security control. Malware already inside a network can attack nearby devices.

Services should expose only necessary interfaces and require appropriate authentication.

Common misunderstandings

"Wi-Fi is the internet"

Wi-Fi is a local radio-link technology. It can connect to local devices even without internet access.

"Every network needs a central server"

Devices can communicate peer to peer. Central servers are an architectural choice.

"A faster cable fixes every network problem"

Performance may be limited by server capacity, routing, latency, Wi-Fi interference, software, or the internet connection.

"Connected means permitted"

A physical path does not imply authorization. Security rules still decide what communication is allowed.

Knowledge check

1. What two broad ingredients make a network?

Connected devices and shared protocols for exchanging information.

2. What is the difference between a switch and router?

A switch primarily forwards local-link traffic within a network; a router forwards packets between networks.

3. Can a home printer work when the internet is unavailable?

Yes, if the printer and sending device can still communicate through the local network.

4. Why are networking layers useful?

They separate responsibilities, allowing one technology to change without redesigning every layer above it.

The one idea to remember

A network is connected devices plus agreed communication rules.

Links carry signals, protocols organize data, switches connect local devices, routers connect networks, and layered software turns those mechanisms into useful services.

Next, we will distinguish local and wide-area networks and see why the internet is best understood as a network of networks.