Network foundationsUnit 3 of 5
Beginner20 minIn reviewTranslation in review

Packets, clients, servers and ports

Follow application data between two process roles and identify the endpoint information used by transport protocols.

What you will learn
  • Explain client and server as roles played by processes.
  • Describe how an IP address, transport protocol and port identify a service endpoint.
Know this first
  • Network foundations
  • Network interface
  • Process
  • Packet
Start this unit
Last verifiedReview every 365 days
On this page

Processes communicate

A client process initiates an exchange to request a service. A server process waits for and responds to requests. These are roles: a powerful machine is not automatically a server, and one computer can run both client and server processes.

Application data is divided and carried through protocol layers. At the IP layer, a packet includes source and destination addressing information. A complete conversation normally involves multiple packets in both directions.

Address, protocol and port

An IP address gets the packet to an interface in an IP network context. A transport protocol such as TCP or UDP identifies its own delivery rules. A port number helps that transport protocol direct data to the intended application endpoint.

destination IP       192.0.2.80
transport protocol   TCP
destination port     443

Together, those values describe a TCP endpoint in this documentation example. Port 443 is registered for HTTPS, but seeing that number alone does not prove that the traffic is encrypted, trustworthy or even HTTPS. Evidence from the actual protocol exchange is still required.

TCP and UDP at beginner level

  • TCP provides a reliable, ordered byte stream between endpoints and establishes connection state.
  • UDP carries individual datagrams without TCP's connection and reliability mechanisms.

Applications choose a transport based on their protocol needs. “UDP is faster” is not a sufficient design explanation; application behaviour, loss handling, latency and network conditions matter.

Mini challenge

A browser process connects to 192.0.2.80 using TCP destination port 443.

  1. Which process is acting as the client?
  2. What identifies the remote interface?
  3. What identifies the transport endpoint?
  4. Which additional evidence would you need before claiming the exchange is valid HTTPS?
Next stepIP addresses and local networks

Now examine the address and prefix that let a host decide whether a destination is local.