liveBook · Manning

Port number

Also called network port, container port

A port number is a transport-layer identifier associated with a host address that directs network traffic to a service or application endpoint.

How 8 Manning books explain it

Acing the CCNA Exam: Volume 1 Fundamentals and Protocols

A port number is a transport-layer identifier ranging from 0 to 65535 that directs network data to a particular application process on a host.

How it is used
Uses transport-layer addressing to deliver messages to application processes and to filter traffic in extended ACLs.
How deep it goes
Explains the numeric range, encapsulation, request-reply reversal, common assignments, and extended-ACL matching.
Examples
Uses HTTPS on TCP 443, a client source port 50000, common protocol assignments, and Cisco extended-ACL entries.
What you can do after
Apply port matching in Cisco extended ACLs and interpret source and destination ports in client-server exchanges.

Read how Acing the CCNA Exam: Volume 1 Fundamentals and Protocols explains port number →

Kubernetes in Action, Second Edition

A container port is a network port on which an application in a container accepts connections.

How it is used
Identifies where a container application accepts connections and helps configure requests or Service forwarding.
How deep it goes
Distinguishes an informative pod port declaration from actual connectivity, then explains Service port and targetPort configuration.
Examples
Uses a pod manifest declaring `containerPort: 8080`, requests to a pod IP, and a Service manifest with `port` and `targetPort`.
What you can do after
Operate/configure it by recording a container port, finding a pod IP, and choosing a Service targetPort or local port-forward.

Read how Kubernetes in Action, Second Edition explains port number →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

A port number is a transport-layer identifier that distinguishes application endpoints and concurrent communication sessions on a host.

How it is used
Uses TCP/UDP port numbers to distinguish simultaneous sessions when dynamic PAT maps many inside hosts to shared public addresses.
How deep it goes
Explains port allocation, preservation, collisions, persistence, capacity, and ICMP’s Identifier alternative, then demonstrates Cisco configuration and output.
Examples
Uses shared-address translation tables, NAT pools, PAT overload commands, and ICMP Identifier handling as concrete examples.
What you can do after
Diagnose PAT translations by relating inside-local and inside-global addresses to translated TCP/UDP ports and session entries.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains port number →

Fundamentals of Cybersecurity

A port number is a numeric identifier that directs network traffic to a particular service or application on a host.

How it is used
Directs incoming network traffic from a host to the appropriate service or application.
How deep it goes
Explains port-number routing with an analogy, address format, and a worked example of services sharing an IP address.
Examples
Uses SMTP on port 25, MySQL on port 3306, and HTTPS on port 443.
What you can do after
Understand how an IP address and port number together direct a request to a service on a host.

Read how Fundamentals of Cybersecurity explains port number →

Learn Go with Pocket-Sized Projects

A network port is a numbered endpoint that identifies a service or connection on a host.

How it is used
Uses port numbers to expose Go HTTP and gRPC services for local development and network requests.
How deep it goes
Explains virtual endpoints, standard assignments, conflicts, development choices, and Go listener calls without covering deployment or containerization.
Examples
Demonstrates HTTP on localhost:8080, curl testing, gRPC on a chosen TCP port, and random allocation through port 0.
What you can do after
Operate/configure a Go HTTP or gRPC service by binding it to a chosen port and handling requests.

Read how Learn Go with Pocket-Sized Projects explains port number →

Road to Kubernetes

A port is a numbered network endpoint through which a host or container accepts or sends traffic for an application or service.

How it is used
Configures local web access and connects host traffic to applications running inside containers.
How deep it goes
Explains defaults, environment and command-line overrides, and host-to-container mappings without descending into networking internals.
Examples
Uses Express.js on ports 3000 and 3011, FastAPI on 8011, and Docker mappings from 8080 to NGINX port 80.
What you can do after
Operate local applications and containers by selecting reachable ports and applying host-to-container mappings.

Read how Road to Kubernetes explains port number →

.NET in Action, Second Edition

A network port is a numbered endpoint used by networked software to identify a service on a host or container.

How it is used
Configures access to a web service running inside a Docker container.
How deep it goes
Distinguishes port exposure from publication and demonstrates host-to-container mapping, but does not detail networking internals.
Examples
Uses an AsciiArtSvc Dockerfile exposing 5101 and a runtime mapping from host port 5000.
What you can do after
Operate/configure a Docker container so a host port reaches the service’s internal listening port.

Read how .NET in Action, Second Edition explains port number →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

A network port is a numbered logical endpoint that identifies a service or application protocol on a networked host.

How it is used
Controls which network services can reach or leave EC2 instances and related AWS resources.
How deep it goes
Explains port-based firewall rules through web, SSH, and EFS examples, but does not develop port internals or application security.
Examples
Uses ports 80, 443, 22, and 2049 in web-server, SSH, and EFS mount-target scenarios.
What you can do after
Operate/configure security-group rules that expose required services while restricting unnecessary inbound and outbound traffic.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains port number →

Also covered in

What to know first

Related concepts

Questions about port number

What is port number?

A port number is a transport-layer identifier associated with a host address that directs network traffic to a service or application endpoint.

Which Manning books explain port number?

Acing the CCNA Exam: Volume 1 Fundamentals and Protocols, Kubernetes in Action, Second Edition, Acing the CCNA Exam: Volume 2 Advanced Networking and Security, Fundamentals of Cybersecurity, Learn Go with Pocket-Sized Projects, Road to Kubernetes, .NET in Action, Second Edition and Amazon Web Services in Action, Third Edition: An in-depth guide to AWS.

What should I know before learning port number?

Manning books that teach port number usually introduce server, SSH, IP address and container first.

What is the difference between port number and host port?

A port number is a transport-layer identifier associated with a host address that directs network traffic to a service or application endpoint. A network port on the host machine that can be mapped to a container port.

What kinds of port number are there?

Kinds of port number include routed port.

What is port number part of?

Port number is part of socket address. A socket address is a network endpoint identifier consisting of a host address and a port number.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.