The Transport Layer PDU Is Called a Segment

The segment is the name given to a packet of data at the transport layer of your network. When your computer sends information across your home network or to the internet, that information gets broken into pieces at different layers. At the transport layer — the fourth layer in the standard network model — those pieces are called segments.

A segment contains the actual data you are sending (like a file or a web page request) plus transport layer information that tells the receiving computer how to reassemble and use that data. This includes port numbers, which direct the data to the right process on the receiving device, and sequence numbers, which help put the pieces back in the correct order if they arrive out of sequence.

Understanding what a segment is helps explain why your home network needs both a router and individual device settings to work properly. The segment is the level where your router decides which device on your network should receive each piece of data, and where your device's operating system decides which program should open it.

Key Takeaways

  • A segment is the unit of data at the transport layer, the fourth layer of network communication.
  • Segments contain both the actual data being sent and control information like port numbers and sequence numbers.
  • Port numbers in segments direct data to the correct process on the receiving device.
  • Sequence numbers help the receiving device reassemble segments that arrive out of order.
  • Understanding segments explains why routers and firewalls can control which programs on your devices can send and receive data.

How Segments Differ From Other Network Packets

Network data travels through multiple layers, and each layer wraps the data in its own container with its own name. At the process layer (the top), you have data. At the transport layer, that data becomes a segment. At the internet layer below it, the segment gets wrapped again and becomes a packet. At the link layer, the packet becomes a frame.

Each wrapper adds information the receiving computer needs at that layer. A segment adds port numbers and sequence numbers. A packet adds IP addresses so routers know which network device should receive it. A frame adds MAC addresses so devices on the same physical network can find each other. This layering is why your home network can have a router (which reads packets and IP addresses) separate from your device's firewall (which reads segments and port numbers).

The distinction matters when you are troubleshooting. If your device cannot reach a server at all, the problem is usually at the packet or frame level — a routing or connection issue. If your device connects to the network but a specific program cannot send data, the problem is usually at the segment level — a port or firewall rule.

Port Numbers: The Address Within a Device

Every segment includes a source port and a destination port. A port is a number between 0 and 65535 that identifies which program on a device should handle the data. When you open a web browser and visit a website, your browser uses a port number (usually a high number assigned automatically) to send the request. The web server responds to that same port number so your browser knows which request the response belongs to.

Some port numbers are reserved for specific services. Port 80 is used for unencrypted web traffic (HTTP), port 443 for encrypted web traffic (HTTPS), port 25 for email sending (SMTP), and port 22 for find remote access (SSH). Your home router's firewall can block or allow traffic based on port numbers, which is how you prevent unwanted programs from sending data out of your network.

When you set up port forwarding on your router — directing traffic on a specific port to a specific device on your network — you are working at the segment level. The router reads the port number in the segment and decides which device should receive it. This is why port forwarding requires you to know both the port number and the device's internal IP address.

Sequence Numbers and Data Reassembly

Large files cannot fit in a single segment. A 10 megabyte video file might be split into thousands of segments, each carrying a small piece of the video. These segments may travel different routes across the internet and arrive at the destination in a different order than they were sent. The receiving computer uses sequence numbers in each segment to put them back in the correct order.

Sequence numbers also help detect when a segment has been lost. If your computer receives segments numbered 1, 2, 3, 5, and 6, it knows segment 4 is missing and can ask the sending computer to resend it. This is why the transport layer is called "reliable" — it guarantees that data arrives complete and in order, even if the underlying network loses or reorders packets.

On a home network with a wired connection or a strong wireless signal, lost segments are rare. On a weak wireless connection or a congested network, retransmissions happen constantly in the background. Your device handles this automatically; you do not need to do anything. But understanding that segments have sequence numbers explains why a weak connection slows down your browsing — your device is spending time asking for retransmissions.

TCP and UDP: Two Ways to Send Segments

Two main protocols operate at the transport layer: TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). Both use segments, but they handle them differently. TCP guarantees that every segment arrives and arrives in order. UDP does not — it sends segments and does not care if some get lost.

TCP is used for anything where missing data matters: email, file downloads, web browsing, and remote access. If even one segment of your email is lost, the entire message is corrupted. UDP is used for things where speed matters more than perfection: video streaming, online gaming, and voice calls. If one segment of a video stream is lost, you might see a brief glitch, but the stream keeps playing.

Your router and firewall can distinguish between TCP and UDP traffic because that information is in the segment header. Some routers let you prioritize one type of traffic over another — for example, giving UDP video traffic priority over TCP file downloads. This is why understanding segments is useful even if you never configure your router: it explains what the settings actually control.

Why Firewalls Work at the Segment Level

A firewall is a program or device that reads segments and decides whether to let them through. It looks at the source port, destination port, and protocol (TCP or UDP) and compares them against a set of rules. If a rule says "block all incoming traffic on port 5900," the firewall will drop any segment trying to reach port 5900, no matter what device sent it.

This is why a firewall can stop malware from sending data out of your computer even if the malware has already infected your system. The malware might try to send a segment to a command-and-control server, but the firewall sees the destination port and blocks it. The malware cannot bypass the firewall because the firewall operates at the operating system level, below the process layer where the malware runs.

When you configure a firewall rule, you are always working with segment-level information: port numbers, protocols, and sometimes IP addresses. Understanding that segments carry this information helps you understand what a firewall rule actually does and why it works.

Frequently Asked Questions

Is a segment the same as a packet?

No. A segment is the unit of data at the transport layer. A packet is the unit of data at the internet layer, which wraps the segment in IP address information. A segment becomes a packet when it moves down to the internet layer.

Can I see segments on my network?

Yes, with a packet capture tool like Wireshark, which is free software that runs on Windows, Mac, and Linux. Wireshark shows you the segments being sent and received on your network, including port numbers, sequence numbers, and the data inside. It is useful for troubleshooting network problems, but the output can be overwhelming if you are not familiar with network protocols.

Why do some programs need specific ports?

Programs listen on specific ports so the operating system knows which program should receive incoming data. When a segment arrives on port 443, the operating system knows it should go to a web browser or web server, not to an email client. If two programs try to use the same port, one will fail to start.

What happens if a segment is corrupted?

TCP includes a checksum — a mathematical check — in each segment to detect corruption. If a segment is corrupted in transit, the checksum fails and the receiving computer discards the segment and asks for a retransmission. UDP does not include this check, so corrupted UDP segments are silently dropped.

Do I need to know about segments to use my home network?

No. Your devices and router handle segments automatically. But understanding segments helps you troubleshoot problems, configure firewall rules, and understand why your router has settings for port forwarding and traffic prioritization.