So have a look at what you see here, there are a lot of packets of Wireshark captures in seconds.
There are some requests and responses for them, broadcasts and their replies and et cetera, et cetera.
There is an easier way to follow a stream, although this is very entertaining.
The Stream is a collection of packets that form a network conversation from the beginning to the end,
just like your favorite story.
So I'm in college now and I captured the traffic just for a little bit, and while I was capturing,
I visited a Web site to create some HTP traffic.
And here are the results, DNS packets, DSP packets, H.T. packets, etc., so I'll select and HDP
packet and it's the get request.
Right, click, go to follow submenu, and here you see the TCP stream and the HTTP stream options are
both enabled, so that means we can follow either the DCP stream or the HTTP stream.
So let's click HTP stream.
Now, the client packets are red and the server packets are blue, they get request by COLLY 200, OK,
response by Oos VW.
Now this is a return page in HTML format, so you can scroll down and we'll see some of the other requests
and the responses and the same stream.
And perhaps you're beginning to see that when you click on a link and website or visit a website by
typing its URL, there might be several consecutive requests and responses that you don't even realize.
But in actuality, you don't need to know them as the end user.
But we're not your typical end users now, are we?
So let's keep going.
From the combo box at the left hand side of the bottom of the stream window, you can filter the conversation
from one side to another or vice versa.
So at the right hand side, right there is another combo box where you can select the output format.
Now, when you close the stream window and go back to the main window of Wireshark, you can see that
the stream filter is applied right here.
So I'll remove the filter by clicking this cross icon.
Now I see the entire captured traffic again.
That is why filters exist.