Web Browsing Analysis
Time to get after it and start looking at things! This is where the rubber meets the road.
Start recording packets in Wireshark! Make sure to choose the correct interface. Interfaces are tricky, but basically look for the one probably starting with en or wl with a bunch of traffic. At least in this case!
Depending on what you are trying to capture you have to change interfaces... "lo" or loopback, is your local interface for packets that never leave your box (which is important for local testing, but not the right place to look for traffic going externally.
With Wireshark fired up, you should see all sorts of traffic stacking up in there, probably with a ton of protocols you've never heard of.
For now, visit roppers.org and then end your session.
Assignment:
- What filter was required to only see Roppers.org traffic?
- What protocol was used?
- What port was used?
- Were you able to see any information in the browsing session?
- Why not?
- Was there anything else that interested you?
Damn HTTPs makes sniffing web traffic boring! At least it's secure these days!