 we can see how does these different applications communicate like for a web page, how is a request from a browser sent to a website and the website server responds to the request by fragmenting the packets and then reassembling it. For the ease of looking at the packets or trying to look at the information that is available in the packets, what I will do here is I will add a filter here which will allow us to only see packets of websites. So now what we see here is our different packets that are responsible for a websites communication to happen. So further we will be learning about protocols like HTTP and TCP and how they enable these websites to exchange information. So while I am doing this what I will do is I will open up Google Chrome. So this is the dummy website. So as I click here what we see on via shark is a lot of other packets are being captured here. Now all these captures are relevant to the websites traffic that was just requested by us on the browser. So the HTTP is the hypertext transfer protocol which is responsible for the communication between a browser and a web server. So let's click on this. So what you see here are different layers of this communication or this piece of communication which we call packet. So you will come to know more about packets in the further course. Now what we see here is different layers of this communication. Now each packet is actually divided into different layers. So you have physical data link layer, then you have network layer and the transport layer. So here what we see is the different information that is relevant to each layer like you have IP addresses in this layer. And so we come to know about these in detail as we go ahead with the course. So what here I want to show is this hypertext transfer protocol request. So basically it says we had requested for this particular website via shark tells you that the response of this request was seen in the frame two to three. So here are the frame numbers and let's scroll down to the frame two to three. So what we expect to see there is there is another HTTP as we had seen earlier. Now this is the response to that request and there are a lot of frames that we see in between. So basically all these frames have been received to complete this entire communication. And so what does come in this communication here? Let's open this packet and see what data was there. So what you see here inside is actually the entire web page. So it's the code of the web page, the entire code of the web page that we had requested. So we could look at it by right clicking on the web page and viewing the web page source. So this is exactly what we had received from the server. So this is how the entire web page has been sent to our laptop. Now how did this happen? Now before this entire response was received, we see there are a lot of packets that were received. So all these were small small packets which were sent here, sent to the laptop and here they were reassembled using their TCP information something like a sequence number. We learn more about it in the further course. So this is how we can capture and look at live information on any of the laptops using Wireshark. Thank you.