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 etcetera, etcetera.
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 Cali now and I captured the traffic just for a little bit.
And while I was capturing, I visited a website to create some Http traffic.
And here are the results.
DNS Packets.
TCP packets.
Http packets.
Etcetera.
So I'll select an Http packet and it's the get request.
Right click go to follow on the submenu.
And here you see the TCP stream and the Http stream options are both enabled.
So that means we can follow either the TCP stream or the Http stream.
So let's click http stream.
Now the client packets are red and the server packets are blue.
The get request by Carly 200.
Okay.
Response by Owasp BWA.
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 in the same stream.
And perhaps you're beginning to see that when you click on a link in a 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.