Run the command ifconfig to get the local IP address. So, we need some clues and be able to use the Wireshark filter capabilities to find the relevant IP Addresses. Since I got 196 packets captured, it’s not that simple to identify the packets that we want to analyze versus the other noise.

Save the pcap file so that we have a backup in case we screw up the traffic capture. So, we’ll have to dig into the capture to find the relevant IP Addresses. go back to Chrome and hit enter to submit the HTTP GET requestĤ) Looking at the wireshark capture window, I captured 196 frames and most of them are specific to my home network traffic and not related to the AWS S3 website.That’s it, nothing else.ģ) Do these steps in order and as quick as possible. I’m using wireless so the capture filter on my MacBook Air is en0. Local network traffic is very noisy so I’ll hit enter just after I start Wireshark.Ģ) Load up Wireshark and setup the capture filter. Packet Captureġ) Paste in the website location into my browser, using Chrome, but don’t hit enter yet. In case you haven’t captured traffic before, it’s a pretty easy process that I outline below, otherwise you can skip to the analysis. I wanted to see what a packet flow looks like to a website hosted on AWS so I uploaded a simple HelloWorld website to AWS S3, an object store that is great for hosting simple, static websites, and captured packets working from my home “office”.

How to use wireshark to get ip 2020