Scribd
Upload
41 views6 pages

Wireshark: Weekly Practice Report (LAB6) LAB6: (PRACTICE #02)

The document is a weekly practice report from a student detailing their use of Wireshark. It includes: - The student's information and class details. - A summary of tasks completed using Wireshark including finding the IP and MAC addresses from an ARP reply, filtering HTTP requests by GET and POST methods, and explaining the details of packets captured for each. - For GET requests, the student explained details like accepted languages, user agent, connection type, accepted encodings, host, and request URI. - For POST requests, similar details were explained like user agent, connection type, accepted encodings, host, request URI, and content types.

Uploaded by

Nguyen Chi Hoang Minh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views6 pages

Wireshark: Weekly Practice Report (LAB6) LAB6: (PRACTICE #02)

The document is a weekly practice report from a student detailing their use of Wireshark. It includes: - The student's information and class details. - A summary of tasks completed using Wireshark including finding the IP and MAC addresses from an ARP reply, filtering HTTP requests by GET and POST methods, and explaining the details of packets captured for each. - For GET requests, the student explained details like accepted languages, user agent, connection type, accepted encodings, host, and request URI. - For POST requests, similar details were explained like user agent, connection type, accepted encodings, host, request URI, and content types.

Uploaded by

Nguyen Chi Hoang Minh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Weekly Practice Report (LAB6)

LAB6: WIRESHARK (PRACTICE #02)


Student ID B1809707
Name Nguyen Chi Hoang Minh
Email address [email protected]
Class Wed, Thu
Browser Edge
OS Window

Practice following topic as far as you can under environment (Snapshot and
explain)

1 Find IP address, MAC address of destination from ARP reply packet

IP address: 192.168.1.1
MAC address: a8:25:eb:57:99:68
2 Filter http.request.method == GET
3 Explain detail pane of GET method packet you searched from Wireshark screen

Accept-Language: en-US => Accepted language standard.

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36


(KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36 Edg/93.0.961.47 => Client
side browser type.

Connection: Keep-Alive => Connection controls whether the network connection


stays open after the current transaction finishes. Connection type is keep alive.

Accept-Encoding: gzip, deflate ==> Accepted encoding in client side.

Host: gaia.cs.umass.edu ==> This is the web server name where client is sending
HTTP GET request.

Request URI: http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file2.html =>


The client is asking for file wireshark-labs/HTTP-wireshark-file2.html present under
the web server name where client is sending HTTP GET request.

Accept: text/html,application/xhtml+xml,application/xml;
q=0.9,image/webp,image/apng,*/*; q=0.8,application/signed-exchange;v=b3; q=0.9
==> Tells server about the type of file it [client side browser] can accept.
4 Filter http.request.method == POST
5 Explain detail pane of POST method packet you searched from Wireshark screen

Cookie: contains the data that is being stored in cookies of your current browser.

Accept-Language: en-US => Accepted language standard.

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36


(KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36 Edg/93.0.961.47 => Client
side browser type.

Connection: Keep-Alive => Connection controls whether the network connection


stays open after the current transaction finishes. Connection type is keep alive.

Accept-Encoding: gzip, deflate ==> Accepted encoding in client side.

Host: mobile.quanlyxe.vn ==> This is the web server name where client is sending
HTTP POST request.

Request URI: http://mobile.quanlyxe.vn/tracking-apis/account/login => The client is


asking for file tracking-apis/account/login present under the web server name where
client is sending HTTP POST request.
Accept: application/json, text/plain, */*==> Tells server about the type of file it [client
side browser] can accept.

JavaScript Object Notation: also known as JSON, which is a format for sharing data.
As JSON is used for data interchange, Object and Member Keys will be
interchanged during login process between server and client.

You might also like