Network Flows
100%

Network Monitoring · Lesson 2

Network Flows

Learn to interpret addresses, ports, timing, and byte counts in a flow summary.

A flow groups traffic that shares properties such as network addresses, ports, and protocol. Monitoring systems can count the bytes or packets in a flow without keeping the full contents.

Reading the Two Endpoints

In this simulated summary the collector records a direction from a source to a destination. Transport protocols such as TCP include port numbers, which can identify a listener on the receiving side.

start=09:21:00Z protocol=TCP src=192.0.2.10:51600 dst=192.0.2.20:443 bytes=1800
start=09:21:00Z protocol=TCP src=192.0.2.20:443 dst=192.0.2.10:51600 bytes=8200

The first line goes toward port 443. The second shows the reverse direction. Some collectors group both directions together, so check the format you are reading.

In the first row, which address and port receive the recorded traffic?

Comparing the Counts

The sample shows more bytes in the direction from port 443. A larger response may be normal for a web page. The count alone gives no page content, account, or reason for the volume.

What do 8,200 bytes in the second row describe?

Adding Context

Use known service information and time to decide which flows are relevant. If you need to know what the web server returned, compare with its access logs for the same time and connection where available.

You want the HTTP status for the web request. Which additional source would help?

Lesson complete

You finished Network Flows

You can now read the main fields of one flow summary.

  • Find endpoint addresses and ports.

  • Interpret byte counts in the reported direction.

  • Choose another source when application results matter.

Keep your learning progress

Create a free account to save this lesson and continue learning on any device.

Create a free account
Next Lesson
Back to Network Monitoring