Hosts, Clients, Servers and Network Interfaces

This lesson answers a different question from How Networks Communicate. The first lesson followed the data; this lesson identifies the devices on that path, the evidence each device uses, and the point where you would investigate when communication fails.

What is a host?

A host is an endpoint that originates, receives, or processes network data. A laptop, desktop, server, printer, phone, and IP camera can all be hosts. Applications run on hosts; switches and routers help their traffic reach other hosts.

The words client and server describe roles, not permanent device types. A laptop may be a client while requesting a web page and a server while sharing a file. The source and destination can also reverse when the reply travels back.

Before sending IPv4 traffic, a host makes one crucial decision:

1. Compare the destination IP address with its own address and subnet mask.
2. If the destination is local, send toward that host's MAC address.
3. If the destination is remote, send toward the default gateway's MAC address.

ARP can supply the required local-link MAC address. ARP is introduced here only as evidence of that decision; a later lesson will examine ARP and MAC learning in depth.

Devices that connect hosts

An intermediary device connects endpoints or network segments. It forwards, filters, or translates traffic; it is not normally the application endpoint for the user's conversation.

A home device may combine an access point, switch, router, firewall, and DHCP service in one box. The functions remain distinct even when the hardware is shared. This lesson introduces the firewall boundary briefly; policy design and Palo Alto behavior belong in the separate firewall module.

Explore the topology

Select any visible device in the topology. The animation pauses and opens a plain-language profile showing the device's purpose, addressing, observable evidence, and a common failure. Expand Technical details only when you want the deeper explanation.

Static topology guide

Local wired path: Wired PC → Layer 2 switch → local server.

Local wireless path: Wireless laptop → access point → Layer 2 switch → local server.

Remote extension: From the Layer 2 switch, traffic continues through the gateway and firewall to the remote server. Replies follow the return path toward the original host.

Wired PC

A wired PC is an endpoint that creates requests and accepts replies over an Ethernet connection.

Wireless laptop

A wireless laptop is an endpoint that reaches the LAN through radio and an associated access point.

Wireless access point

The access point connects an associated wireless host to the wired local network.

Layer 2 switch

A switch connects LAN devices and forwards Ethernet frames using destination MAC information.

Router and default gateway

The default gateway is the router interface a host uses to reach destinations outside its local network.

Firewall boundary

A firewall is a security checkpoint that can permit or deny traffic crossing a network boundary.

Local server

The local server is a destination host on the same IPv4 subnet as the clients.

Remote server

The remote server is the final destination host on a different IP network.

Choose a packet journey

Wired host to local serverThe PC reaches a server on the same LAN.Wireless host to local serverThe laptop crosses the access point and switched LAN.Wired host to remote serverThe PC uses its gateway and crosses a firewall boundary.Wireless host to remote serverThe laptop crosses wireless, switched, routed, and secured links.

Use the explorer as a diagnostic map: identify the source host, decide whether the destination is local or remote, find the expected next hop, and then follow both the outbound and return paths. A successful request does not guarantee a successful reply if the return route or a security policy is different.

Compare packet journeys

Change the journey above and watch which devices become relevant.

• Wired to local: host → switch → local server, then the reverse path.
• Wireless to local: laptop → access point → switch → local server, then back through the switch and access point.
• Wired to remote: host → switch → gateway → firewall → remote server, with a routed return.
• Wireless to remote: laptop → access point → switch → gateway → firewall → remote server, followed by the complete return journey.

The switch is still important in a remote journey, but it does not decide the end-to-end IP route. The access point does not become the laptop's IP gateway merely because it provides the wireless connection. At every routed hop, the link-layer frame can change while the source and destination IP addresses normally continue to identify the communicating hosts.